Actually, I had come up with 3 major problems;
- Properties are different (but there is a backwards compatibility idea
used elsewhere)
- ejbCreate returns Object instead of void for Entity beans
- Deployment Descriptors are serialized instead of xmlized
1) The hack is that you replace the Properties object with a subclass
that overrides get to do a
new
InitialContext().lookup("java:/comp/env/ejb10properties/<foo>")
2) Since jBoss uses reflection to invoke ejbCreate, and then doesn't do
anything with the return-type, that is just a matter of creating an
ejb10Verifier.
3) Not sure.
Is there anything else I'm missing on this? Am I about to walk into the
weeds with that?
Thanks in Advance,
Wes
-----Original Message-----
From: Filip Hanik [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 24, 2001 3:31 PM
To: jBoss Developer
Subject: Re: [jBoss-Dev] EJB 1.0 backwards compatibility
could be a little bit tough,
there are some significant changes, especially how the EJB objects are
tying
properties into the JNDI tree.
Also the deployment descriptors have completely changed.
Filip
~
Namaste - I bow to the divine in you.
~
Filip Hanik
Technical Architect
[EMAIL PROTECTED]
----- Original Message -----
From: "Wes Moulder" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 24, 2001 1:19 PM
Subject: [jBoss-Dev] EJB 1.0 backwards compatibility
Hey guys,
I'm working on using jBoss with an EJB 1.0 app. I was wondering if
anyone had gone down this path yet.
--Wes
