Yes. Depending upon what you are building, you may have to include one or
more JRun jar files in you classpath when compiling.
The thing that really frosted me was having to write my own
ejbFindByPrimaryKey() method when using CMP *and* Allaire's insistance that
this was fine with EJB 1.1 spec.
Two other items it didn't feel right about:
(1) In addition to ejb-jar.xml, JRun uses a deploy.properties file. It
functions kinda like jboss.xml and jaws.xml but it effects *all* beans
deployed on that engine (it's not part of any bean's jar). In fact,
Allaire *prefers* you use deploy.properties vs. ejb-jar.xml for *all*
settings. Their documentation is written entirely around deploy.properties
and it's not clear where in ejb-jar.xml you might set some of the items
they require.
(2) Even with CMP, JRun requires you to spell out to the engine the JDBC
for *all* actions--findByPrimaryKey(), add, update, etc.
At 14:02 9/29/2000 -0400, James Brannan wrote:
>Doesnt JRun require some allaire.xyz classes in its EJB's. When I was
>evaluating JRun I got as far as that - when I saw that I had to import
>some proprietary stuff I opted not to use Jrun.
--------------------------------------------------------------------------
Thad Humphries "Who is this that darkens my counsel
Web Development Manager With words without knowledge?"
Phone: 540/675-3015, ext. 225 - Job 38:1, NIV
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
