Yes, but I noticed when I deploy the PingPong example I see a WSDL
initialized
message get spit out in debug. I dont see that when I deploy
my service assembly containing the Service Unit with my bpel, wsdl, xsd, and
deploy.xml.
However, I do see the service unit go through the BPEL compiler and
say it is starting. Then looking at the picture through JMX I see the
endpoint for that
BPEL. OR, at least JMX thinkks its therer??? COuld that be wrong?
Alex Boisvert wrote:
>
> If you mean they use a different namespace prefix (bp:, ws:) for the same
> namespace uri ("http://mydomain/MYservice";), that shouldn't be a problem.
>
> alex
>
>
> On 7/13/07, jbi joe <[EMAIL PROTECTED]> wrote:
>>
>>
>> Yes, currently Im using a PoJO with lw-container, but may have
>> loads of others in the future.
>> I turned on DEBUG. I think its soemthing to do
>> with the deploy.xml file and how Im specifing URL to WSDL.
>> The namespace that I have used for my BPEL and WSDL
>> are the same, but with differnt xsd.
>> I used netbeans to construct them and the example
>> had them named the same.
>> MYservice.bpel
>> MYservice.wsdl
>>
>> Namesace
>> bp=http://mydomain/MYservice
>> ws=http://mydomain/MYservice
>>
>> IS THAT OK?
>>
>>
>>
>> Alex Boisvert wrote:
>> >
>> > On 7/13/07, jbi joe <[EMAIL PROTECTED]> wrote:
>> >>
>> >>
>> >> I suspected that the message is misleading. I will try changing the
>> >> debuf
>> >> level.
>> >> I am using the JMX console and see the endpoint listed for the BPEL.
>> >> QUESTION: Where if anyplace does the WSDL have to be specified.
>> >> Does it need to be specified inside of the Normalized Message?
>> >
>> >
>> >
>> > The WSDLs are only required for the BPEL process and are not directly
>> > referenced in the normalized message. The service name + endpoint are
>> > part
>> > of the message exchange metadata.
>> >
>> > BTW, which service engine are you using for your Java components? Are
>> you
>> > using servicemix-lwcontainer? servicemix-jsr181? servicemix-cxf-se?
>> > I'll
>> > get started on an example, most likely with servicemix-lwcontainer.
>> >
>> > alex
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Could-not-find-a-mapper-for-request-message-tf4067593.html#a11585559
>> Sent from the Apache Ode User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Could-not-find-a-mapper-for-request-message-tf4067593.html#a11593026
Sent from the Apache Ode User mailing list archive at Nabble.com.
