1. Miller Rhodes
  2. PowerServer Web
  3. Sunday, 10 February 2019

We have an application that is loaded with NVOs of type 'exception' and I wondered what others had done to deal with the face that this object is unsupported.

Miller Rhodes Accepted Answer Pending Moderation
0
Votes
Undo

Hi Marco,

 

So we could literally do nothing and we would be fine since the deployment process will comment out this code ?

Comment
Literally.

Your code will keep working in client server, but will be automatically skipped when deployed as a Web application.

One source for both environments, with no need to comment/uncomment lines out.

As a matter of fact, just to alleviate your concerns on Exceptions handling, keep in mind that - unlike a PB executable - the Web application will not "crash" when exceptions occur.

Of course you'll receive "user-unfriendly" messages, but the Web app will keep running.

Best,

.m



  1. Marco Meoni
  2. Tuesday, 12 February 2019
There are no comments made yet.
  1. Tuesday, 12 February 2019
  2. PowerServer Web
  3. # 1
Chris Pollach Accepted Answer Pending Moderation
-1
Votes
Undo

Hi Miller;

  FYI: Ticket #2111 was opened on 2019-01-09 as an enhancement request to support the TRY..CATCH in PowerServer. Ticket #2036 is related to this as well.

Regards ... Chris

Comment
There are no comments made yet.
  1. Monday, 11 February 2019
  2. PowerServer Web
  3. # 2
Miller Rhodes Accepted Answer Pending Moderation
0
Votes
Undo

.

Comment
There are no comments made yet.
  1. Monday, 11 February 2019
  2. PowerServer Web
  3. # 3
Marco Meoni Accepted Answer Pending Moderation
1
Votes
Undo

Hello Miller,
it mostly depends on what type of external objects are used in your application, and what kind of operations (logging? user-friendly message handling?) you need to trap via TRY ... CATCH.
PowerServer toolkit will automatically comment out your NVOs because PowerServer offers its own built-in exception handling mechanism to avoid client side exception.
This is typically just fine for most of the cases.
However, if you need to call external DLLs or COM objects on the client machine you may argue that the lack of support for Exception is not gonna let you handling properly runtime errors.

In short, you have no means for reusing whatever custom function or event is implemented into your NVOs.
This is not gonna affect migration of your application, no matter how big it is and how loaded it is of Exception-derived NVOs.
But it does affect its execution if exceptions thrown by external components are meant to change the application execution flow.
Best,
.m

Comment
0

Votes

Hi Marco,







Thanks for the response. We have a number of local external functions in an NVO that call several functions in a DLL. It looks like our customer is trying to provide user friendly error messaging.



I was just wondering if there was an Appeon sanctioned way to replace this functionality.
  1. Miller Rhodes
  2. Monday, 11 February 2019
There are no comments made yet.
  1. Monday, 11 February 2019
  2. PowerServer Web
  3. # 4
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.