nk4um

Seems like I wasn''t as up-to-date as I thought!

I went to check for updates before I posted, but ended up only half did it!!

Sorry!

Cheers,

Chris

Hi Chris, It appears that 4.0.2 doesn''t have the exceptionProcess enhancement in the standard module jar. But the update on the repository does.

Please look at the System Information tool and confirm that you have this jar installed:
urn:com:ten60:core:module:standard (v1.8.29)

I''ve just downloaded a clean instance and patched it from apposite and the correct pluggable overlay instance is there.

Cheers, Tony

HI Guys,

This doesn''t seem to be working in 4.0.2, or am I being mad!?

I get the following exception on commission:

<ex>   <ex>     <id>Unhandled exception parsing standard module</id>     <message>[DeltaXML Web Space] Construction of endpoint failed</message>     <location>urn:com:deltaxml:netkernel:web: /module/rootspace/pluggable-overlay</location>   </ex>   <ex>     <id>Unhandled exception initialising parameter on endpoint</id>     <message>Use of undeclared [exceptionProcess] parameter</message>   </ex> </ex>

My exceptionProcess looks like:

<exceptionProcess>   <identifier>active:groovy</identifier>   <argumentname="operator">res:/com/deltaxml/netkernel/testException.gy</argument>   <argumentname="request">arg:request</argument>   <argumentname="exception">arg:exception</argument> </exceptionProcess>

Removing this from my module (leaving my preProcess and postProcess) configuration and my module commissions fine.

Any ideas?

Cheers,

Chris

Hi Chris, yes it would be useful to be able to do this. Then it would unify the exception handler overlay functionality. Currently exceptions don''t get postProcessed as you suggest. Let me think about this. I suspect it would be bad for exceptions to enter the postProcess but it might be good to have an exceptionProcess parameter. Thoughts?

Tony

Is there any way of catching exceptions thrown when creating the response in a pluggable overlay (i.e. the bit after the pre-process and after the post-process)?

What might be useful would be an exceptionProcess to compliment postProcess (either postProcess or exceptionProcess would be triggered, never both and never neither). While I could use an exceptionHandler overlay, it feels natural for my exception handling code to be on the same level as the postProcess.

Cheers,

Chris