[ http://jira.codehaus.org/browse/XFIRE-812?page=comments#action_83174 ] Mark Alan West commented on XFIRE-812: --------------------------------------
To expand on the above comment, deployed EJBs don't have a orion-web.xml file. They have a orion-application.xml file. And this doesn't not allow configuration of the class loader. I guess this is what Oracle is working on? > Problem to connect to the webservice from the OC4J Container > ------------------------------------------------------------ > > Key: XFIRE-812 > URL: http://jira.codehaus.org/browse/XFIRE-812 > Project: XFire > Issue Type: Bug > Affects Versions: 1.2.3 > Reporter: Victor Dieu > Assigned To: Tomasz Sztelak > Attachments: full.txt, The Error Message.txt > > > I want to access an external webservice. I've generated a webservice proxy by > using XFire. Every thing works fine when I run my client as a standalone > client. The problem occurs when I deployed my application to the OC4J > application server. The deployment works fine, but when a module tried to > access the proxy via a stateful session bean (EJB 3.0), it fails. > I've tried many different ways to make it works without success. Please help > me !!! > The error message is attached to this message. > Please send me an email if any one have fixed it... > I'm standing helpless rite now... > Waiting desperately for your respons, > Best regards, > Victor Dieu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
