Re: [ebxmlms-general] Error when running loopback or monitor.

[Patrick Y. <kc...@ce...>]

Mark,

I guess the problem occurs when the jwsdp tries to locate the default 
SOAP message factory. This may be due to duplicated saaj*.jar and 
jaxm*.jar. And the classloader of jwsdp may be confused if there are 
multiple copies of the same library. You can try to delete those files 
in either directory and see the effect in a trial-and-error way.. :-) I 
am sorry we are not so familiar with jwsdp, and so we cannot give you a 
direct answer. Thanks.

Regards, -Patrick


MTM Zenhorst wrote:

>Hello,
>
>The Hermes messaging seems to run ok, starts polling and no errors in
>the log files.
>
>The client does give an error when running either the loopback or the
>monitor. Both with the same error...
>
>The error is:
>cannot create request objects.
>hk.hku.cecid.phoenix.message.handler.RequestException: Cannot initialize
>request object: Default message factory cannot be instantiated.
>at hk.hku.cecid.phoenix.message.handler.Request.<init> (Unknown Source)
>at hk.hku.cecid.phoenix.message.handler.Request.<init> (Unknown Source)
>at Loopback.run(Loopback.java:29)
>at Loopback.main(Loopback.java:11)
>
>I cant find the thing that is wrong. versions of the jar files are all
>the same as in the jwsdp.
>
>used software:
>Windows 2k
>jwsdp1.2
>apache 2
>
>I hope somebody can help me with this.
>
>Regards,
>
>Mark Zenhorst
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IBM Linux Tutorials.
>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>_______________________________________________
>ebxmlms-general mailing list
>ebx...@li...
>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>  
>