Re: BPEL execution problem

This looks like a http BC bug. It seems to generate the tag
<getEmergencyItineraryResponse xmlns="">

instead of

<getEmergencyItineraryResponse xmlns=" http://j2ee.netbeans.org/wsdl/EmergencyService">

If you already filed a bug, please associate it with http BC component.

I am posting this on dev@... alias too. Please note that for issues on the runtime, you have better chance of responses if you post on dev@....

- Kiran.

Chris wrote:

I'm joining to this mail a simple example of a BPEL process that is building. But xmlns is empty and the client is failing.

Can someone please have a look. I'm not sure if this is a bug or if I'm simply doing something wrong. I really need to get my project working (it is more complex than the one I'm joining but same error).

Best regards,
Chris.

On Nov 16, 2007 9:29 AM, Chris <dchris@...> wrote:

I'm joining the corresponding BPEL and WSDL files generated with
netbeans 6 (in Open ESB 2.0 Latest (Build 20071112)).

On Nov 15, 2007 12:59 PM, Chris <dchris@...> wrote:
> Ok. And can you see the reason why it didn't understand it? the SOAP
> message was in my mail too and it contrains the result I expect in
> <itinerary></itinerary>. Something must be wrong in the message
> though..
>
> Regards,
> Chris.
>
>
> On Nov 15, 2007 12:17 PM, Honorez Dylan <Dylan.Honorez@...> wrote:
> > Chris,
> >
> > The error message simply states that the server received a soap-message that it didn't understand.
> >
> > Unexpected response element getEmergencyItineraryResponse
> > expected: { http://j2ee.netbeans.org/wsdl/EmergencyService}getEmergencyItineraryResponse
> >
> > So yes, xmlns='' is a problem. Your message should look like this:
> > <?xml version="1.0" encoding="UTF-8"?>
> > <SOAP-ENV:Envelope
> > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/ "
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/
> > http://schemas.xmlsoap.org/soap/envelope/">
> >   <SOAP-ENV:Body>
> >     <getEmergencyItineraryResponse xmlns=" http://j2ee.netbeans.org/wsdl/EmergencyService">
> >       <itinerary>0,0,0|9,6,7|9,8,0|9,6,1|4,4,6|8,7,8|50,50,50</itinerary>
> >     </getEmergencyItineraryResponse>
> >   </SOAP-ENV:Body>
> > </SOAP-ENV:Envelope>
> >
> > Kind regards,
> > Dylan Honorez
> > kZen Consultant
> > 4C Technologies nv
> > Veldkant 33A
> > B-2550 Kontich
> > +32 (0)3 451 36 60tel
> > +32 (0)3 451 36 69 fax
> > +32 (0)485 69 28 12 mob.
> >
> >
> >
> > -----Original Message-----
> > From: Chris [mailto: dchris@...]
> > Sent: donderdag 15 november 2007 11:26
> > To: nbentpack@...
> > Subject: [entpack] BPEL execution problem
> >
> > Hi,
> >
> > I finally got my BPEL project to work, at least I thought so. I get
> > this output when executing a test :
> > <?xml version="1.0" encoding="UTF-8"?>
> > <SOAP-ENV:Envelope
> > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd=" http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation=" http://schemas.xmlsoap.org/soap/envelope/
> > http://schemas.xmlsoap.org/soap/envelope/ ">
> >   <SOAP-ENV:Body>
> >     <getEmergencyItineraryResponse xmlns="">
> >       <itinerary>0,0,0|9,6,7|9,8,0|9,6,1|4,4,6|8,7,8|50,50,50</itinerary>
> >     </getEmergencyItineraryResponse>
> >   </SOAP-ENV:Body>
> > </SOAP-ENV:Envelope>
> >
> > Output looks good, is xmlns="" a problem?
> >
> >
> > However, I get the following error when executing a client:
> > javax.xml.ws.WebServiceException: Unexpected response element
> > getEmergencyItineraryResponse expected:
> > { http://j2ee.netbeans.org/wsdl/EmergencyService}getEmergencyItineraryResponse
> >         at com.sun.xml.ws.client.sei.ResponseBuilder$RpcLit.readResponse (ResponseBuilder.java:604)
> >         at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:256)
> >         at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java :224)
> >         at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:117)
> >         at $Proxy92.getEmergencyItinerary(Unknown Source)
> >         at org.apache.jsp.callServices_jsp._jspService (callServices_jsp.java
> > from :90)
> >         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)
> >         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
> >         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
> >         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
> >         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
> >         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
> >         at org.apache.catalina.core.ApplicationFilterChain.servletService (ApplicationFilterChain.java:411)
> >         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:317)
> >         at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:198)
> >         at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)
> >         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:230)
> >         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198)
> >         at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:288)
> >         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
> >         at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:202)
> >         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
> >         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java :577)
> >         at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
> >         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
> >         at org.apache.catalina.core.StandardPipeline.doInvoke (StandardPipeline.java:632)
> >         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
> >         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java :571)
> >         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
> >         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
> >         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
> >         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
> >         at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:571)
> >         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
> >         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:270)
> >         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
> >         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess (DefaultProcessorTask.java:568)
> >         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
> >         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask (DefaultReadTask.java:341)
> >         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
> >         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask (DefaultReadTask.java:214)
> >         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
> >         at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java :106)
> >
> > Could you please tell me what the error message mean exactly and if
> > you have any idea where the problem could come from?
> >
>

-- 
Kiran Bhumana
Open ESB Community (http://open-esb.org)