Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved 'Exception' unsupported in Powerserver Web

  1. Issue
1
Votes
Undo
  1. Miller Rhodes
    Miller Rhodes
  2. PowerServer 2020 or older (Obsolete)
  3. Sunday, 10 February 2019 22:52 PM UTC

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.

WSAStartup external function not working in Powers...
Richtextedit and mobile/web
Responses (4)
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Monday, 11 February 2019 07:23 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

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
Miller Rhodes
  1. Miller Rhodes
  2. Monday, 11 February 2019 12:31 PM UTC
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. Helpful 1
There are no comments made yet.
Miller Rhodes
Miller Rhodes Accepted Answer Pending Moderation
  1. Monday, 11 February 2019 12:31 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

.

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 11 February 2019 15:23 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

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.
Miller Rhodes
Miller Rhodes Accepted Answer Pending Moderation
  1. Tuesday, 12 February 2019 01:05 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Hi Marco,

 

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

Comment
Marco Meoni
  1. Marco Meoni
  2. Tuesday, 12 February 2019 07:57 AM UTC
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. Helpful 1
There are no comments made yet.
  • Page :
  • 1


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