I just did, off the very URL you gave in the message. No problems.
Ted Neward
Java Instructor, DevelopMentor (http://www.develop.com)
http://www.javageeks.com/~tneward
- Original Message -
From: "Michael Mok" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAI
so the EJB spec CAN'T, in my interpretation,
forbid RMI calls, because then a Bean could never refer to another bean in
any way. Is there some text I missed in that section? (I freely admit, I
just skimmed it just now--not a real deep read--but didn't see anything
along those lines.)
T
f, you can usually get away with just calling the
3-arg Class.forName() method, with the 3rd arg being the ClassLoader coming
from Thread.getContextClassLoader(). Or you can risk it and use the
ClassLoader that loaded you. Your choice. :-)
Ted Neward
Java Instructor, DevelopMentor ( http://www.d
va2 way.
Just a wild-*ss guess, but without any sort of confirmation or denial from
the Orion team, it's about as good as it gets, it seems. Potential
workaround: do a Class.forName(p.get(Context.INITIAL_CONTEXT_FACTORY))
before calling into the JNDI InitialContext constructor.
T
javageeks.com/Papers/ClassForName
Orion team: Make sure you get this ClassLoader thing right--BEA/WebLogic
doesn't, I know for a fact.
Ted Neward
Java Instructor, DevelopMentor ( http://www.develop.com )
http://www.javageeks.com/~tneward
-Original Message-
From: Eric Richardson <
>We will rewrite our applications with a method we call servlet-entities :
>HTTP as a protocol replacing RMI/IIOP
>XML for data exchange
>
Don't forget to have a look at SOAP--it's exactly what you're describing
above.
Ted Neward
Java Instructor, DevelopMentor ( ht
ok about
this ( http://www.manning.com/Neward3 )--but you have to understand the
risks you assume in choosing the "build" option in the "buy vs. build"
decision.
Ted Neward
Java Instructor, DevelopMentor ( http://www.develop.com )
http://www.javageeks.com/~tneward
-Orig
