Hi.
My apologies if this question betrays my status as an EJB neophyte. I
_think_ it's a JBoss question, not a general EJB question. Here goes:
I'm having a bit of trouble declaring a many-to-many relationship on
one of my CMP beans. Specifically, I want to create trees (i.e.,
graphs with no cyc
One last thing: don't forget to use the -m jar switch or the manifest
attribute of the ANT jar task. You can't just drop your own MANIFEST.MF file
in META-INF. That seems like it should work but it's never worked for me.
What I do is create one dot MF file for each component in the ear and then
use
On Sunday 09 February 2003 18:34, Rod Macpherson wrote:
> In your case the class-path settings belong in the WAR file but in general
> it belongs with the referrent - putting jar files in the EAR manifest might
> work but I doubt it. Here's an example with two utility jars under the ear
> root and
In your case the class-path settings belong in the WAR file but in general
it belongs with the referrent - putting jar files in the EAR manifest might
work but I doubt it. Here's an example with two utility jars under the ear
root and one utility in directory called base. There is also a war file a
On Sunday 09 February 2003 13:47, Rod Macpherson wrote:
> What you have described is not a valid structure because the upper bound of
> a manifest path setting is the ear root. Putting your jars (struts or
> otherwise) in the ear will correct the problem. Those jars are then
> accessible with a pat
>>> [EMAIL PROTECTED] 7/02/03 20:20:34 >>>
If the problem is simply between the web and ejb tiers - try toggling
the Java2Compliance flag in your jbossweb.sar/META-INF/jboss-service.xml...
[...]
Let me know if this does the trick - if so it is a useful development
trick and should go in my FAQ.
Hi!
I bet 1 Euro on that you are using MySQL 3.23 or older.
There is a bug in the Connector/J 3.0.5 code for getting the isolation
level from a 3.23 server.
The bug does not appear when accessing MySQL 4.x
Regards,
Olle Hallin
Márcio Emílio Cruz Vono de Azevedo wrote:
Hi all,
We've been t
What you have described is not a valid structure because the upper bound of
a manifest path setting is the ear root. Putting your jars (struts or
otherwise) in the ear will correct the problem. Those jars are then
accessible with a path relative to teh ear root. Assume you placed a jar in
/lib/foo
Hello,
I've got jboss 3.0.6 with Jetty installed and have configured a web
application for use with struts. I've used the following layout:
ear file
---> contains the war file
---> contains an ejb jar file with both session and entity beans
The war file contains a custom manifest that ha
