I have a serializable class that I want to pass between the JSP container
and a session EJB container. Within the EJB container it uses a
specialized storage library, and within the JSP it should use a stub
library with NOPs in place of the storage library. Both the real and stub
libraries are .jar files.
Unfortunately I don't see how to persuade Orion to invoke the real library
when the class is used within the EJB container, and then to invoke the
stub library when the class is used within the JSP container.
Effectively I want to rig the classloaders and method dispatch so that
com.blah.Storage.method is invoked from real.jar when called from an EJB,
and from stub.jar when called within a JSP. So there are two
implementations of the same class.
Can anyone suggest how to configure this?
At the moment I have two unappetizing alternatives:
1. Two parallel inheritance diagrams with an abstract factory doing
conversion between classes for passing to/from JSP.
2. Two instances of Orion in two VMs.
J
--
Joshua Goodall A friend of mine works for a medium-sized telco.
He has no phone, because (and I quote)
"the lady who provisions phones is on holiday"
