This question triggered my spidy senses.
While the hacker in me can find a perverse pleasure in trying to spoof the java.security.Principal
object needed to get access to an EJB application server as a remote user, I must say that this sounds like a bad idea and a waste of time. (Oooo look at me!!! I'm Sun Certified! Watch me do my Java Certified happy dance. La la la....)
Luckily, my hacking skills aren't good enough to even try to go down that path. Even building some sort of SOAP cluge isn't going to give you access to an EJB's internal local
and local home
methods. I, personally, don't like the idea of building a test suite that only deals with an object's public face.
Luckily, there is JUnit, which is a wonderful set of testing libraries for Java. It's so cool it's even been ported to Perl.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.