Thanks Paul - I'll give it a try.
In light of a previous thread on the ODE API, I may be jumping forward a bit
but I would like to get a better understanding of the PXE architecture.
1) Is it possible to invoke PXE such that a BPEL process executes within the
client's context or is a PXE RMI server always required?
2) I found the following FAQ on the PXE Wiki and would like to know if the
core process engine ( i.e. jacob, bpel-runtime ) can be abstracted away from
the task/threading framework ( i.e. sfwk-core, sfwk-impl )?
*Q.* *Can PXE be deployed within an application server or web container?*
*A.* Yes, PXE can be deployed into most common application servers. However,
it is important to note that PXE is not an *enterprise application* in the
J2EE sense: PXE manages its own transactions and threads. Consequently, if
PXE is deployed using a WAR or EAR file, it will be in violation of a number
of J2EE contracts.
3) Is it possible to synchronously invoke a PXE BPEL process? I saw this bit
of code in the BpelUnitTest ( line 160 ) so I thought I'd ask.
// We invoke here, but we get responses asynchronously, through our
// callback methods!
listener.invokeBPEL(
_callback, svc, i == 0 ? "initial" : ("#" +i),
msg.operation, patternSubstitution(sw.toString()));
Thanks for the help.
Lance
On 4/7/06, Paul R Brown <[EMAIL PROTECTED]> wrote:
>
>
> Hi, Lance --
>
> > Could someone from the PXE team point me to any documentation/
> > threads that
> > discuss debugging the PXE engine. I would like to run the
> > spexcercizer unit
> > tests and step through the engine. Thanks for any help ( btw - I am
> > using
> > the Eclipse JDT ).
>
> All of the interesting parts of the spexerciser run in the PXE server
> container, and IIRC, there is a flag that you can pass when starting
> the server executable that enables a JPDA connection...
>
> Look in $PXE_ROOT/PXE/src/bin/jlo-run.sh.template at around line 111;
> if you put --jdb on the commandline, then it will set up a connection
> for a JPDA debugger on port 5005 for your favorite debugger, be that
> in Eclipse or NetBeans. :)
>
> -- Paul
>
