Currently the getErrors method returns error messages constituted as follows:
Error: :=>
Can the separator between the XPATH and Error Message also be made "==>" so
that the different constituents of the error message can be parsed
consistently as required by the consuming application?
The problem with ":" as a separator is that it is also used in XML world as
namespaceprefix:elementname
If there is a known way/pattern of parsing the error message, please do let me
know.
Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I created / renamed SysErrErrorHandler and ElementErrorHandler to
B2BErrErrorHandler and B2BErrorHandler, made necessary changes to the error
message formats
Specified the new errorhandler via. setErrHandler
I am able to successfully run it in standalone environment. However when I run
it in WebSphere, I get following error:
java.lang.ClassCastException: net.sf.saxon.tinytree.TinyElementImpl
incompatible with net.sf.saxon.tree.ElementImpl
at uk.org.jcam.sdom.Element.setAttribute(Element.java:172)
Martin,
I am stuck! I am not able to use the Warning feature as the error messages are
in different format difficult / not able to parse XPATH, element and error
message.
The error handler is also not working and I have been troubleshooting all day
as I could not figure out what might have gone wrong.
Requesting you to make the error / warning messages appear consistent as
suggested earlier such that they can be segregated easily using simple string
functions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am sorry you seemed to have been struggling through things.
This is a saxon error that should be fixed in RC6. I am wondering if you have
an earlier version running in websphere, hence the fact that it is running OK
in you dev environment and not in WebSphere.
I now have googletalk set up so you can chat when you are in.
Martin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Currently the getErrors method returns error messages constituted as follows:
Error: :=>
Can the separator between the XPATH and Error Message also be made "==>" so
that the different constituents of the error message can be parsed
consistently as required by the consuming application?
The problem with ":" as a separator is that it is also used in XML world as
namespaceprefix:elementname
If there is a known way/pattern of parsing the error message, please do let me
know.
Regards
Also for the Warning the getWarnings method returns warnings in the format
Warning: =>:
Can it be made consistent please.
Please raise this as a bug fix request - consistent format of CAMV error and
warning messages using ==> delimiter.
To overcome this formatting 'error' you simply have to implement your own
ErrorHandler. This formatting is all done in the ElementErrorHandler.
I do not regard this as a bug.
Well sure it can be done but it is about maintaining consistency say among
warnings and error messages.
If you send me some pointers about how to create a custom ErrorHandler, I am
happy to do that.
I created / renamed SysErrErrorHandler and ElementErrorHandler to
B2BErrErrorHandler and B2BErrorHandler, made necessary changes to the error
message formats
Specified the new errorhandler via. setErrHandler
I am able to successfully run it in standalone environment. However when I run
it in WebSphere, I get following error:
java.lang.ClassCastException: net.sf.saxon.tinytree.TinyElementImpl
incompatible with net.sf.saxon.tree.ElementImpl
at uk.org.jcam.sdom.Element.setAttribute(Element.java:172)
Martin,
I am stuck! I am not able to use the Warning feature as the error messages are
in different format difficult / not able to parse XPATH, element and error
message.
The error handler is also not working and I have been troubleshooting all day
as I could not figure out what might have gone wrong.
Requesting you to make the error / warning messages appear consistent as
suggested earlier such that they can be segregated easily using simple string
functions.
Hi,
I am sorry you seemed to have been struggling through things.
This is a saxon error that should be fixed in RC6. I am wondering if you have
an earlier version running in websphere, hence the fact that it is running OK
in you dev environment and not in WebSphere.
I now have googletalk set up so you can chat when you are in.
Martin