EJX is dead; a popular replacement is XDoclet (formerly EJBDoclet),
which generates home/remote interfaces, primary key classes, deployment
descriptors, and the occasional kitchen sink from a single source file.
XDoclet is a Javadoc doclet that runs at compile time as opposed to a
GUI like EJX,
There's a great tool called XDoclet (formerly EJBDoclet)
http://sourceforge.net/projects/xdoclet/ that uses a Javadoc plugin to
generate deployment descriptors as well as the home/remote interfaces,
pk classes, etc for your beans. It's a huge timesaver.
Steve
-Original Message-
From:
This is a shot in the darkhave you made sure that all of your IP
addresses are set correctly? (i.e. not hardcoded, and correctly
configured in the jcml file?
Steve
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hunter
Hillegas
Sent: Friday, July
When you start, make sure you're using run_with_tomcat.bat (or
run_with_tomcat.sh on unix) instead of run.bat/run.sh. If tomcat is
indeed starting, you should see the following in your console during
startup:
[...]
[EmbeddedTomcat] Initializing
[EmbeddedTomcat] Initialized
[...]
If it's not
I believe that you'll have to provide the logging yourself - JAWS
handles only the CMP beans, so the settings in jaws.xml will only affect
SQL from CMP beans. BMP beans talk directly to the database via
connections, statements, etc. If there were a logging feature for BMP
beans it would be in
From the manual:
If you are using both jboss.jcml and jboss-auto.jcml capabilities you
have to note the following. If there is a need to remove any of the
MBeans listed in jboss.jcml you also have to remove it from
jboss-auto.jcml (if such is listed in jboss-auto.jcml ) to achieve the
desired
It's still a draft. The second PFD came out just a week or two ago; it
included some fairly major changes:
http://java.sun.com/products/ejb/docs.html
JBoss will support EJB 2.0 once the spec is final...
Steve
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
There's still wiggle room there, and each app server that I've seen
behaves a bit differently. When you see the words typically and
should in the same sentence, I guarantee that people (app server
developers, here) will do what you suggest they not do. I agree with the
JBoss interpretation, but
The trans-attribute tag must be set to Required, RequiresNew, or
Mandatory or JBoss won't persist your beans. Other application servers
(Weblogic, for example) have different behavior; the EJB 1.1 spec isn't
trmendously clear how this should be handled. Change the transaction
attribute + things
Obtaining a connection in setEntityContext and releasing it in
unsetEntityContext is usually a bad thing to do for exactly that reason
- the beans are almost always pooled. Read Tip #7 (at the bottom) from
http://www.flashline.com/content/bq/bq080200.jsp; it does a pretty good
job of explaining
Hi Kashif,
JBoss 2.2 supports some features of EJB 2.0 (message driven beans, for
example) but doesn't implement full support because the EJB 2.0 spec
hasn't been finalized. Once the spec is done, JBoss will support it.
For info on MDBs, check out the manual at
11 matches
Mail list logo
