You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Lance Waterman <la...@gmail.com> on 2006/07/07 07:58:40 UTC
Deployment API
I have taken feedback from Paul Brown and posted the deployment API
specification here - http://wiki.apache.org/ode/Architecture. I have also
checked the "dapi" into the ode scratch area. Note: I fully anticipate the
API and document will need more work.
Lance
Re: Deployment API
Posted by Lance Waterman <la...@gmail.com>.
Hi Matthieu,
Thanks for taking a look. I am currently out of the office for a couple of
weeks and my connectivity will be spotty. I will take a look at the DD as
soon as I get back.
Lance
On 7/11/06, Matthieu Riou <ma...@gmail.com> wrote:
>
> Lance,
>
> I've finished reading the deployment specification and it's really nice!
> Thanks a lot for all the work and Paul's review. Personally I'm pretty
> happy
> with the APIs and interactions you described, I'm only concerned about one
> thing that could be missing: a deploment descriptor.
>
> I'd agree that, following your document, the deployment descriptor would
> probably be useful only for what you described as the "deploy tooling".
> However whatever the tooling is, it will need a descriptor to accomplish a
> few tasks, mostly finding the EPRs. We have to associate a given partner
> link with a service and a port (an EPR). That's the only way give an EPR
> to
> the engine and also to route incoming messages to the engine efficiently.
> So
> I blieve a DD is necessary for this. Also having some user-specific
> properties associated with a process in there too could be useful as well.
>
> So as I mentioned, even this could be a bit out of scope for the
> deployment
> spec, I think the deployment descriptor should also be described there as
> it
> should be bundled in the deployment package. If you like, Assaf has made a
> spec for the content of a deployment descriptor. We could share this. You
> can also have a look at the schema at the deployment descriptor schema
> reflecting this spec:
>
>
> http://svn.apache.org/repos/asf/incubator/ode/scratch/pxe-iapi/bpel-dd/src/main/xsd/dd.xsd
>
> What do you think?
>
> Matthieu
>
> On 7/6/06, Lance Waterman <la...@gmail.com> wrote:
> >
> > I have taken feedback from Paul Brown and posted the deployment API
> > specification here - http://wiki.apache.org/ode/Architecture. I have
> also
> > checked the "dapi" into the ode scratch area. Note: I fully anticipate
> the
> >
> > API and document will need more work.
> >
> > Lance
> >
> >
>
>
Re: Deployment API
Posted by Lance Waterman <la...@gmail.com>.
Hi Matthieu,
I have been looking over the DD and am a bit confused as to what is being
used and where. In the DD project there are two implementations ( dd.xsd and
bpeldd.xsd ). It appears that both are used by
org.apache.ode.bpel.engine.BpelServerImpl. The overloaded method "deploy()"
has two implementations. It looks like one method deploys a compiled BPEL
process and uses the dd.xsd ( ProcessDDInitializer ) and the other deploys
an un-compiled BPEL process and uses the bpeldd.xsd ( ProcessInitializer ).
Is this interpretation correct and is this the intent? They appear to be
similar in function to me but I would like to verify.
Thanks,
Lance
On 7/11/06, Matthieu Riou <ma...@gmail.com> wrote:
>
> Lance,
>
> I've finished reading the deployment specification and it's really nice!
> Thanks a lot for all the work and Paul's review. Personally I'm pretty
> happy
> with the APIs and interactions you described, I'm only concerned about one
> thing that could be missing: a deploment descriptor.
>
> I'd agree that, following your document, the deployment descriptor would
> probably be useful only for what you described as the "deploy tooling".
> However whatever the tooling is, it will need a descriptor to accomplish a
> few tasks, mostly finding the EPRs. We have to associate a given partner
> link with a service and a port (an EPR). That's the only way give an EPR
> to
> the engine and also to route incoming messages to the engine efficiently.
> So
> I blieve a DD is necessary for this. Also having some user-specific
> properties associated with a process in there too could be useful as well.
>
> So as I mentioned, even this could be a bit out of scope for the
> deployment
> spec, I think the deployment descriptor should also be described there as
> it
> should be bundled in the deployment package. If you like, Assaf has made a
> spec for the content of a deployment descriptor. We could share this. You
> can also have a look at the schema at the deployment descriptor schema
> reflecting this spec:
>
>
> http://svn.apache.org/repos/asf/incubator/ode/scratch/pxe-iapi/bpel-dd/src/main/xsd/dd.xsd
>
> What do you think?
>
> Matthieu
>
> On 7/6/06, Lance Waterman <la...@gmail.com> wrote:
> >
> > I have taken feedback from Paul Brown and posted the deployment API
> > specification here - http://wiki.apache.org/ode/Architecture. I have
> also
> > checked the "dapi" into the ode scratch area. Note: I fully anticipate
> the
> >
> > API and document will need more work.
> >
> > Lance
> >
> >
>
>
Re: Deployment API
Posted by Matthieu Riou <ma...@gmail.com>.
Lance,
I've finished reading the deployment specification and it's really nice!
Thanks a lot for all the work and Paul's review. Personally I'm pretty happy
with the APIs and interactions you described, I'm only concerned about one
thing that could be missing: a deploment descriptor.
I'd agree that, following your document, the deployment descriptor would
probably be useful only for what you described as the "deploy tooling".
However whatever the tooling is, it will need a descriptor to accomplish a
few tasks, mostly finding the EPRs. We have to associate a given partner
link with a service and a port (an EPR). That's the only way give an EPR to
the engine and also to route incoming messages to the engine efficiently. So
I blieve a DD is necessary for this. Also having some user-specific
properties associated with a process in there too could be useful as well.
So as I mentioned, even this could be a bit out of scope for the deployment
spec, I think the deployment descriptor should also be described there as it
should be bundled in the deployment package. If you like, Assaf has made a
spec for the content of a deployment descriptor. We could share this. You
can also have a look at the schema at the deployment descriptor schema
reflecting this spec:
http://svn.apache.org/repos/asf/incubator/ode/scratch/pxe-iapi/bpel-dd/src/main/xsd/dd.xsd
What do you think?
Matthieu
On 7/6/06, Lance Waterman <la...@gmail.com> wrote:
>
> I have taken feedback from Paul Brown and posted the deployment API
> specification here - http://wiki.apache.org/ode/Architecture. I have also
> checked the "dapi" into the ode scratch area. Note: I fully anticipate the
>
> API and document will need more work.
>
> Lance
>
>