Hi everyone,
I am experimenting with adding XSLT as an implementation type (with a
WSDL interface for now). I have looked at the javascript container and
found it very helpful, but I have two questions about the use of
ComponentContext and proxy factories.
Among other things, I have created :
public class XSLTComponentContext extends AbstractContext implements
AtomicContext
In XSLT the components are stateless: you just run the whole stylesheet
and return the result tree.
I am confused about what getInstance should return if one is dealing
with a non-Java implementation type. The Java container returns the
actual class that implements the component's Java interface and the
javascript container returns a proxy from a proxy factory...
One option is to return what getTargetInstance returns (the XSLTInvoker)
but that avoids the proxy chains so doesn't feel right... On the other
hand, if i do something similar to what the javascript implementation
does, then the result from locateService is something of class $Proxy37
that has JDKInvocationHandler .. Not sure what one would do with that
(?). Am I supposed to create my own proxy factory and plug it in somehow ?
Any insight appreciated into the right way to set up the proxies and the
getInstance method so that a non-java implementation type that is
stateless fits properly.
thanks!
Rania
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
