Hi Raymond, Sorry for the late reply, your e-mail passed through my filters :) The approach described in the document sounds good to me, it's similar to what we're doing for import resolution within an ODE deployment package. So that should work. The only part I'm not so clear about though is when the resolution occurs, is it when the contribution is loaded?
And thanks for the congrats! Matthieu On 7/31/07, Raymond Feng <[EMAIL PROTECTED]> wrote: > > Hi, Matthieu. > > Congratulations on the ODE graduation! > > We have made some processes in Tuscany regarding to the artifact > resolving. > Please see more details at > > http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Resolving+WSDL+and+XSD+artifacts > . > > I think the strategy will apply to BPEL as well. Would you please take a > look? Hopefully, we can get the implementation.bpel working soon. > > Thanks, > Raymond > > ----- Original Message ----- > From: "Matthieu Riou" <[EMAIL PROTECTED]> > To: "Luciano Resende" <[EMAIL PROTECTED]> > Cc: <[email protected]> > Sent: Thursday, July 05, 2007 5:08 PM > Subject: Re: BPEL implementation: WSDL and BPEL resolving > > > > Sure, no problem. And thanks :-) > > > > On 7/5/07, Luciano Resende <[EMAIL PROTECTED]> wrote: > >> > >> Thanks Matthieu > >> > >> I'm little overbooked these days, but let me see if I could try to > >> look into the resolution thing over the weekend. Is that OK ? > >> > >> On 7/5/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: > >> > Hi guys, > >> > > >> > I've done a few additional stuff on the BPEL implementation allowing > a > >> BPEL > >> > file to be compiled by ODE upon deployment. The implementation is > >> therefore > >> > created and initialized with most of what would be needed by the > >> runtime. > >> > However there's still a couple of problems with resolution and > finding > >> my > >> > way inside Tuscany code isn't that easy. > >> > > >> > To resolve the WSDL implemented by the process I've been trying to go > >> > through the resolution mechanism and declare the implementation I > >> > return > >> in > >> > the read() method of the processor as unresolved. However the > resolve() > >> > method is never called afterward and this results in a > >> NullPointerException > >> > in Tuscany as the InterfaceContract is never set. From what I could > >> > make > >> out > >> > of the code, it seems that the resolution mechanism happens for > >> Interface > >> > processors but not of implementations, but I could be wrong. > >> > > >> > I've created a patch that adds the BPEL compilation and demonstrates > >> > the > >> > problem using the test case. Please have a look at > >> > BPELImplementationProcessor, you'll see how the implementation is > >> > built. > >> > You'll also see that the BPEL file from now is directly loaded using > an > >> > additional "file" attribute. Ideally that should go as well to use > the > >> same > >> > type of resolving as for the WSDL (when it will work). > >> > > >> > Some help regarding this would be definitely welcome... > >> > > >> > Thanks, > >> > Matthieu > >> > > >> > >> > >> -- > >> Luciano Resende > >> Apache Tuscany Committer > >> http://people.apache.org/~lresende > >> http://lresende.blogspot.com/ > >> > > > >
