Hey
Jon Tirsen wrote:
> But what you explained (if I didn't misunderstand you entirely, which is not
> improbable) is how to bypass these restrictions. But you then are developing
> is non-portable beans. They will probably work in some J2EE-implementations
> but not all.
No, the beans will work in all implementations. They do this by not
doing any restricted operations internally. If the external libraries
work in all J2EE-implementations is another story though.
> Putting a recommendation on the ejb-interest-list which goes
> something like "Bypassing EJB-restrictions in three short lessons", is not
> very nice.
.. which definitely was not the intent. People wanted to know how it
worked; I explained how it worked. What you do with this knowledge is up
to you. Use your judgement.
> That's knowledge reserved for us hardcore-ejb-hackers (not in a
> positive sense) that eat J2EE-implementations for lunch.
Sorry, I didn't realize I should "shield" mortal EJB-programmers from
powerful knowledge and insights in how it works.
> We who actually
> realize that we're never gonna be able to port this bean to another server
> somewhere around this millenia... (and we just realized that this server
> won't be passing the y2k-mark with grace... or something...)
You're having a bad day, right? ;-)
> And BTW, I thought everyone immediately after installing JDK1.2.x patched
> the java.policy to say "grant all AllPermission". :) Which actually is a
> serious security-threat, imposed by Suns incapability of building good gui.
> But that's an entirely different story...
Indeed it is ;-)
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
