Re: [pxe-user] Apache Axis Integration

[Paul B. <pau...@gm...>]

Hi, Sanjay --

> In the PXE faq it is stated that
>  1) PXE integration with apache axis is possible.
>  2) PXE's BPEL compiler can be customized to support non-standard BPEL
> syntax and semantics.

These are both true.

>  Do we have any form of documentation on how above things can be
> accomplished?

For #1, you have two cases; if PXE fills the role of the client, then
it's straightforward to integrate the AXIS version of SAAJ.  If PXE
fills, the role of the server, then you'd need to implement a
"provider" that interfaces with PXE's internal messaging bus along the
lines of the native service provider example.  (This is for AXIS v1;
for AXIS v2 or XFire, you'll want to think differently...)

What's the use case that you have in mind?  (SOAP headers?)

For #2, you can implement a custom activity on a variety of levels.=20
On one level, you can provide a scripting endpoint like the XSLT
service provider.  On another level, you can extend the behavior of
existing BPEL constructs (like the support for section 14.3 in BPEL4WS
1.1).  On an even deeper level, you can extend the object model,
compiler, and runtime for completely different constructs -- the PXE
"virtual machine" could be used for a completely different language if
you were feeling really ambitious.

What's the use case that you have in mind here?  (Annotations to
populate SOAP headers?)

-- Paul