You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by atp <pa...@cudl-lille.fr> on 2008/08/25 15:02:58 UTC
Re: Error deployment BPEL- UndeclaredPartnerLink
Hi,
I've read this thread, but, unfortunately, it does'nt answer to my problem
which is very similar to which of tmf.
I've got this message from ODE for a week, and I can't find the explanation:
Caused by: org.apache.ode.bpel.compiler.api.CompilationException: error:
[CompilationErrors] Compilation completed with 3 error(s):
file:/opt/apache-tomcat-6.0.14/webapps/ode/WEB-INF/processes/ValidationProcess/ValidationProcess.bpel:18:
error: [UndeclaredPartnerLinkType] Attempt to reference undeclared partner
link type "{http://bpel.lmcu.fr/Notification/}NotificationPLT".
null:55: error: [UndeclaredPartnerLink] Attempt to reference undeclared
partner link "Notification".
file:/opt/apache-tomcat-6.0.14/webapps/ode/WEB-INF/processes/ValidationProcess/ValidationProcess.bpel:61:
error: [UndeclaredPartnerLink] Attempt to reference undeclared partner link
"Notification".
at org.apache.ode.bpel.compiler.BpelCompiler.compile(BpelCompiler.java:741)
at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:260)
at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:330)
at
org.apache.ode.store.DeploymentUnitDir.compile(DeploymentUnitDir.java:162)
at
org.apache.ode.store.DeploymentUnitDir.compile(DeploymentUnitDir.java:126)
at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:165)
... 3 more
I'm trying to setup a very simple asynchronous process:
- it is invoked by a client which pass a message;
- it sends the message to a user, by invoking a WS which sends the message
by mail;
- it waits for the response
- it sends back the response to the client.
Notification.wsdl defines the WS in charge to send the message by mail, and
to send back the response to the BPEL process.
ValidationProcess.wsdl is the WSDL associated with the BPEL process.
I've declared the partner link type NotificationPLT in Notification.wsdl as
well as in ValidationProcess.wsdl, and I always get the same error.
I think that I've conscienciously checked the namespaces :-/
I've tested the files attached by thomas, and they seem to work, after
having applied your fix (until an error due to an encode use not supported).
If you have time to have a look, here are my files:
the process files:
http://adullact.net/docman/view.php/384/2183/ValidationProcess.bpel
http://adullact.net/docman/view.php/384/2181/ValidationProcess.wsdl
the invoked WS:
http://adullact.net/docman/view.php/384/2180/Notification.wsdl
http://adullact.net/docman/view.php/384/2182/Notification.xsd
In thix version, all partner link type are declared in
ValidationProcess.wsdl, but itsan option that I prefer not to keep.
My configuration:
- ReadHat Enterprise
- Apache tomacat 6.0.14
- Apache ODE 1.2
The project was generated by Eclipse and the BPEL plugin.
Thanks in advance for any help,
Ph.
PS: I'm trying to make this process work for learning BPEL. I would be very
pleased il somebody could give some link towards others simple example of
asynchronous BPEL process. Thanks again :-)
--
--
View this message in context: http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19143471.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Error deployment BPEL- UndeclaredPartnerLink
Posted by Matthieu Riou <ma...@offthelip.org>.
On Mon, Aug 25, 2008 at 6:55 AM, atp <pa...@cudl-lille.fr> wrote:
>
>
>
> atp wrote:
> >
> > Hi,
> >
> > I've read this thread, but, unfortunately, it does'nt answer to my
> problem
> > which is very similar to which of tmf.
> >
> > [ ... ]
> >
> >
>
> I've just now partially solve the problem.
> It appears that the WSDL editor and the BPEL wizzard don't ude the same
> namespace for partner link types.
>
> The wsdl editor uses http://schemas.xmlsoap.org/ws/2004/03/partner-link/,
> while the BPEL wizzard use http://docs.oasis-open.org/wsbpel/2.0/plnktype
>
> So, the ValidationProcess.wsdl file contained a mix of both, and the ODE
> compiler seems have a preference for the first one.
>
> For now, the problem is over, and I'll have to deal with a lot of new ones
> :-)
>
On thing I noticed: your NotificationPLT doesn't seem to be using any role
whose portType is implemented by the process.
Matthieu
>
> Regards,
>
> Ph.
>
> --
> --
> View this message in context:
> http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19144293.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>
Re: Error deployment BPEL- UndeclaredPartnerLink
Posted by Druid <de...@gmail.com>.
Hi
There is still another problem，I think I have defined the service but it
is not find
I find it difficult to solve the problem by myself,and the reference
material is not enough for me,is there any suggestion?
2008/9/23 Matthieu Riou <ma...@offthelip.org>
> On Tue, Sep 23, 2008 at 3:30 AM, Druid <de...@gmail.com> wrote:
>
> >
> > with your help,I have solved the problem,but I met a new one.
> > I konw there is something wrong with the confirmationData,but I don't
> know
> > what is the reason.
> > http://www.nabble.com/file/p19624961/HelloWorld2-RPC-sa.zip
> > HelloWorld2-RPC-sa.zip
> > http://www.nabble.com/file/p19624961/error.txt error.txt
> >
>
> In HelloWorldAsynchronism.bpel you have the following assignment:
>
> <assign>
> <copy>
> <from>
> <confirmationData xmlns="urn:/HelloWorldAsynchronism.wsdl">
> <ha:HelloName>1111</ha:HelloName>
> </confirmationData>
> </from>
> <to variable="HelloResponseAA" part="confirmationData" />
> </copy>
> </assign>
>
> In BPEL when you want to assign a literal XML snippet you have to surround
> it with a <literal> element:
>
> <assign>
> <copy>
> <from>
> <literal>
> <confirmationData xmlns="urn:/HelloWorldAsynchronism.wsdl">
> <ha:HelloName>1111</ha:HelloName>
> </confirmationData>
> </literal>
> </from>
> <to variable="HelloResponseAA" part="confirmationData" />
> </copy>
> </assign>
>
> Matthieu
>
>
> >
> >
> > Matthieu Riou-5 wrote:
> > >
> > > On Sun, Sep 21, 2008 at 10:58 PM, Druid <de...@gmail.com> wrote:
> > >
> > >>
> > >> I have met the same problem ,and I changed the namingspace as you
> > >> said,but
> > >> it
> > >> doesn't work.
> > >> what else should I have to change?
> > >
> > >
> > > In BPEL 2.0 the portType reference in a partner link type is an
> > attribute,
> > > not a sub-element. So your partner link type should look like:
> > >
> > > <plnk:partnerLinkType name="HelloLT">
> > > <plnk:role name="helloService" portType="tns:HelloAvailabilityPT"/>
> > > <plnk:role name="helloCustomer" portType="tns:HelloCallbackPT"/>
> > > </plnk:partnerLinkType>
> > >
> > > Matthieu
> > >
> > >
> > >> http://www.nabble.com/file/p19602295/HelloWorld2-RPC-sa.zip
> > >> HelloWorld2-RPC-sa.zip
> > >> http://www.nabble.com/file/p19602295/error.txt error.txt
> > >>
> > >>
> > >> atp wrote:
> > >> >
> > >> >
> > >> >
> > >> > atp wrote:
> > >> >>
> > >> >> Hi,
> > >> >>
> > >> >> I've read this thread, but, unfortunately, it does'nt answer to my
> > >> >> problem which is very similar to which of tmf.
> > >> >>
> > >> >> [ ... ]
> > >> >>
> > >> >>
> > >> >
> > >> > I've just now partially solve the problem.
> > >> > It appears that the WSDL editor and the BPEL wizzard don't ude the
> > same
> > >> > namespace for partner link types.
> > >> >
> > >> > The wsdl editor uses
> > >> http://schemas.xmlsoap.org/ws/2004/03/partner-link/
> > >> ,
> > >> > while the BPEL wizzard use
> > >> http://docs.oasis-open.org/wsbpel/2.0/plnktype
> > >> >
> > >> > So, the ValidationProcess.wsdl file contained a mix of both, and the
> > >> ODE
> > >> > compiler seems have a preference for the first one.
> > >> >
> > >> > For now, the problem is over, and I'll have to deal with a lot of
> new
> > >> ones
> > >> > :-)
> > >> >
> > >> > Regards,
> > >> >
> > >> > Ph.
> > >> >
> > >> > --
> > >> >
> > >>
> > >> --
> > >> View this message in context:
> > >>
> >
> http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19602295.html
> > >> Sent from the Apache Ode User mailing list archive at Nabble.com.
> > >>
> > >>
> > >
> > >
> >
> > --
> > View this message in context:
> >
> http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19624961.html
> > Sent from the Apache Ode User mailing list archive at Nabble.com.
> >
> >
>
Re: Error deployment BPEL- UndeclaredPartnerLink
Posted by Matthieu Riou <ma...@offthelip.org>.
On Tue, Sep 23, 2008 at 3:30 AM, Druid <de...@gmail.com> wrote:
>
> with your help,I have solved the problem,but I met a new one.
> I konw there is something wrong with the confirmationData,but I don't know
> what is the reason.
> http://www.nabble.com/file/p19624961/HelloWorld2-RPC-sa.zip
> HelloWorld2-RPC-sa.zip
> http://www.nabble.com/file/p19624961/error.txt error.txt
>
In HelloWorldAsynchronism.bpel you have the following assignment:
<assign>
<copy>
<from>
<confirmationData xmlns="urn:/HelloWorldAsynchronism.wsdl">
<ha:HelloName>1111</ha:HelloName>
</confirmationData>
</from>
<to variable="HelloResponseAA" part="confirmationData" />
</copy>
</assign>
In BPEL when you want to assign a literal XML snippet you have to surround
it with a <literal> element:
<assign>
<copy>
<from>
<literal>
<confirmationData xmlns="urn:/HelloWorldAsynchronism.wsdl">
<ha:HelloName>1111</ha:HelloName>
</confirmationData>
</literal>
</from>
<to variable="HelloResponseAA" part="confirmationData" />
</copy>
</assign>
Matthieu
>
>
> Matthieu Riou-5 wrote:
> >
> > On Sun, Sep 21, 2008 at 10:58 PM, Druid <de...@gmail.com> wrote:
> >
> >>
> >> I have met the same problem ,and I changed the namingspace as you
> >> said,but
> >> it
> >> doesn't work.
> >> what else should I have to change?
> >
> >
> > In BPEL 2.0 the portType reference in a partner link type is an
> attribute,
> > not a sub-element. So your partner link type should look like:
> >
> > <plnk:partnerLinkType name="HelloLT">
> > <plnk:role name="helloService" portType="tns:HelloAvailabilityPT"/>
> > <plnk:role name="helloCustomer" portType="tns:HelloCallbackPT"/>
> > </plnk:partnerLinkType>
> >
> > Matthieu
> >
> >
> >> http://www.nabble.com/file/p19602295/HelloWorld2-RPC-sa.zip
> >> HelloWorld2-RPC-sa.zip
> >> http://www.nabble.com/file/p19602295/error.txt error.txt
> >>
> >>
> >> atp wrote:
> >> >
> >> >
> >> >
> >> > atp wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> I've read this thread, but, unfortunately, it does'nt answer to my
> >> >> problem which is very similar to which of tmf.
> >> >>
> >> >> [ ... ]
> >> >>
> >> >>
> >> >
> >> > I've just now partially solve the problem.
> >> > It appears that the WSDL editor and the BPEL wizzard don't ude the
> same
> >> > namespace for partner link types.
> >> >
> >> > The wsdl editor uses
> >> http://schemas.xmlsoap.org/ws/2004/03/partner-link/
> >> ,
> >> > while the BPEL wizzard use
> >> http://docs.oasis-open.org/wsbpel/2.0/plnktype
> >> >
> >> > So, the ValidationProcess.wsdl file contained a mix of both, and the
> >> ODE
> >> > compiler seems have a preference for the first one.
> >> >
> >> > For now, the problem is over, and I'll have to deal with a lot of new
> >> ones
> >> > :-)
> >> >
> >> > Regards,
> >> >
> >> > Ph.
> >> >
> >> > --
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19602295.html
> >> Sent from the Apache Ode User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19624961.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>
Re: Error deployment BPEL- UndeclaredPartnerLink
Posted by Druid <de...@gmail.com>.
with your help,I have solved the problem,but I met a new one.
I konw there is something wrong with the confirmationData,but I don't know
what is the reason.
http://www.nabble.com/file/p19624961/HelloWorld2-RPC-sa.zip
HelloWorld2-RPC-sa.zip
http://www.nabble.com/file/p19624961/error.txt error.txt
Matthieu Riou-5 wrote:
>
> On Sun, Sep 21, 2008 at 10:58 PM, Druid <de...@gmail.com> wrote:
>
>>
>> I have met the same problem ,and I changed the namingspace as you
>> said,but
>> it
>> doesn't work.
>> what else should I have to change?
>
>
> In BPEL 2.0 the portType reference in a partner link type is an attribute,
> not a sub-element. So your partner link type should look like:
>
> <plnk:partnerLinkType name="HelloLT">
> <plnk:role name="helloService" portType="tns:HelloAvailabilityPT"/>
> <plnk:role name="helloCustomer" portType="tns:HelloCallbackPT"/>
> </plnk:partnerLinkType>
>
> Matthieu
>
>
>> http://www.nabble.com/file/p19602295/HelloWorld2-RPC-sa.zip
>> HelloWorld2-RPC-sa.zip
>> http://www.nabble.com/file/p19602295/error.txt error.txt
>>
>>
>> atp wrote:
>> >
>> >
>> >
>> > atp wrote:
>> >>
>> >> Hi,
>> >>
>> >> I've read this thread, but, unfortunately, it does'nt answer to my
>> >> problem which is very similar to which of tmf.
>> >>
>> >> [ ... ]
>> >>
>> >>
>> >
>> > I've just now partially solve the problem.
>> > It appears that the WSDL editor and the BPEL wizzard don't ude the same
>> > namespace for partner link types.
>> >
>> > The wsdl editor uses
>> http://schemas.xmlsoap.org/ws/2004/03/partner-link/
>> ,
>> > while the BPEL wizzard use
>> http://docs.oasis-open.org/wsbpel/2.0/plnktype
>> >
>> > So, the ValidationProcess.wsdl file contained a mix of both, and the
>> ODE
>> > compiler seems have a preference for the first one.
>> >
>> > For now, the problem is over, and I'll have to deal with a lot of new
>> ones
>> > :-)
>> >
>> > Regards,
>> >
>> > Ph.
>> >
>> > --
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19602295.html
>> Sent from the Apache Ode User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19624961.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Error deployment BPEL- UndeclaredPartnerLink
Posted by Matthieu Riou <ma...@offthelip.org>.
On Sun, Sep 21, 2008 at 10:58 PM, Druid <de...@gmail.com> wrote:
>
> I have met the same problem ,and I changed the namingspace as you said,but
> it
> doesn't work.
> what else should I have to change?
In BPEL 2.0 the portType reference in a partner link type is an attribute,
not a sub-element. So your partner link type should look like:
<plnk:partnerLinkType name="HelloLT">
<plnk:role name="helloService" portType="tns:HelloAvailabilityPT"/>
<plnk:role name="helloCustomer" portType="tns:HelloCallbackPT"/>
</plnk:partnerLinkType>
Matthieu
> http://www.nabble.com/file/p19602295/HelloWorld2-RPC-sa.zip
> HelloWorld2-RPC-sa.zip
> http://www.nabble.com/file/p19602295/error.txt error.txt
>
>
> atp wrote:
> >
> >
> >
> > atp wrote:
> >>
> >> Hi,
> >>
> >> I've read this thread, but, unfortunately, it does'nt answer to my
> >> problem which is very similar to which of tmf.
> >>
> >> [ ... ]
> >>
> >>
> >
> > I've just now partially solve the problem.
> > It appears that the WSDL editor and the BPEL wizzard don't ude the same
> > namespace for partner link types.
> >
> > The wsdl editor uses http://schemas.xmlsoap.org/ws/2004/03/partner-link/
> ,
> > while the BPEL wizzard use
> http://docs.oasis-open.org/wsbpel/2.0/plnktype
> >
> > So, the ValidationProcess.wsdl file contained a mix of both, and the ODE
> > compiler seems have a preference for the first one.
> >
> > For now, the problem is over, and I'll have to deal with a lot of new
> ones
> > :-)
> >
> > Regards,
> >
> > Ph.
> >
> > --
> >
>
> --
> View this message in context:
> http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19602295.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>
Re: Error deployment BPEL- UndeclaredPartnerLink
Posted by Druid <de...@gmail.com>.
I have met the same problem ,and I changed the namingspace as you said,but it
doesn't work.
what else should I have to change?
http://www.nabble.com/file/p19602295/HelloWorld2-RPC-sa.zip
HelloWorld2-RPC-sa.zip
http://www.nabble.com/file/p19602295/error.txt error.txt
atp wrote:
>
>
>
> atp wrote:
>>
>> Hi,
>>
>> I've read this thread, but, unfortunately, it does'nt answer to my
>> problem which is very similar to which of tmf.
>>
>> [ ... ]
>>
>>
>
> I've just now partially solve the problem.
> It appears that the WSDL editor and the BPEL wizzard don't ude the same
> namespace for partner link types.
>
> The wsdl editor uses http://schemas.xmlsoap.org/ws/2004/03/partner-link/,
> while the BPEL wizzard use http://docs.oasis-open.org/wsbpel/2.0/plnktype
>
> So, the ValidationProcess.wsdl file contained a mix of both, and the ODE
> compiler seems have a preference for the first one.
>
> For now, the problem is over, and I'll have to deal with a lot of new ones
> :-)
>
> Regards,
>
> Ph.
>
> --
>
--
View this message in context: http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19602295.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Error deployment BPEL- UndeclaredPartnerLink
Posted by atp <pa...@cudl-lille.fr>.
atp wrote:
>
> Hi,
>
> I've read this thread, but, unfortunately, it does'nt answer to my problem
> which is very similar to which of tmf.
>
> [ ... ]
>
>
I've just now partially solve the problem.
It appears that the WSDL editor and the BPEL wizzard don't ude the same
namespace for partner link types.
The wsdl editor uses http://schemas.xmlsoap.org/ws/2004/03/partner-link/,
while the BPEL wizzard use http://docs.oasis-open.org/wsbpel/2.0/plnktype
So, the ValidationProcess.wsdl file contained a mix of both, and the ODE
compiler seems have a preference for the first one.
For now, the problem is over, and I'll have to deal with a lot of new ones
:-)
Regards,
Ph.
--
--
View this message in context: http://www.nabble.com/Error-deployment-BPEL--UndeclaredPartnerLink-tp15884549p19144293.html
Sent from the Apache Ode User mailing list archive at Nabble.com.