I'm trying to deploy jboss-el-2.0.1.GA.jar within my webapp. It works fine if
I put the jar in $JBOSS_HOME/server/default/lib/. However, if I try to put the
jar in my webapp ear, I can't instantiate ExpressionFactoryImpl:
| java.lang.ClassNotFoundException: No ClassLoaders found for:
org.jb
Nevermind, got it working now. Had to put the destinations file in the root of
the ear and referenced it as a service module in jboss-app.xml.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180257#4180257
Reply to the post :
http://www.jboss.com/index.html?
Oh, and I just realized that specifying a name of "queue/mdb" will actually
create the queue "queue/queue/mdb". The name should read just "mdb".
However, it's still just ignoring my META-INF/jboss-destinations-service.xml,
so I still don't know what's going on.
View the original post :
http:/
I forgot to mention that my application is scoped. My META-INF/jboss-app.xml
contains:
|
| http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd";>
|
|
| net.app:archive=ear
| java2ParentDelegation=false
|
|
|
|
I tried to do something simi
So I'm using JBoss 4.2.2.GA to create a handful of MDB's. I'm using the
@MessageDriven annotation to configure the destination for the bean. Can I
provide a *-service.xml in an EAR to create the Queue?
I tried putting the following in myEar/META-INF/jboss-destinations-service.xml:
|
|
And all is well in the world... or at least my app.
Thanks again, jaikiran!
Justin.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171035#4171035
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171035
_
OK, thanks for bearing with me. I'm now back to the NoSuchMethodException:
org.hibernate.validator.ClassValidator exception. There was an error in my ant
script and the hibernate jars went into the ear root instead of lib/... oops!
Now, after jboss starts and I try to use hibernate from my .wa
Well it's definitely pulling the hibernate jars in from
jboss-4.2.2.GA/server/default/lib/ and not my ear. The verbose log doesn't
load anything from the jars in my ear lib directory.
I also put those other two jars in the ear, no change.
justin.
View the original post :
http://www.jboss.com
To me it still smells like my app is using the old hibernate. According to the
hibernate forum thread linked by ANN-554, the last post says to use hibernate
annotations 3.3.0.
I only see this issue if I leave the default hibernate jars in jboss (hibernate
annotations 3.2.1.GA). If I overwri
Hmm, when I build the ear via ant, the exception is different than the one I
previously posted which was built from eclipse. I guess the difference is that
no hibernate jars are in the classpath when building with ant (I have no direct
compile dependencies).
| Caused by: java.lang.NullPoint
Thanks.
hibernate-commons-annotations.jar: 3.0.0.GA
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170804#4170804
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170804
___
jb
Are there any configuration files I'm missing? Or am I going about this the
wrong way? Again, everything works fine if I just overwrite the hibernate jars
in the jboss server lib directory. However, if I keep the original hibernate
jars in the jboss server lib directory, copy the new jars int
The hibernate jars in my ear are:
Hibernate Core 3.2.6.GA
Hibernate Annotations 3.3.1.GA
Hibernate EntityManager 3.3.2.GA
These all work fine together. If I copy the jars in my ear (hibernate3.jar,
hibernate-annotations.jar, hibernate-commons-annotations.jar,
hibernate-entitymanager.ja
Well, this still isn't working correctly. My .war file within the .ear is
still trying to use the old hibernate version in the jboss lib directory. I
see this exception when the .war tries to use hibernate:
| Caused by: java.lang.NoSuchMethodException:
org.hibernate.validator.ClassValidator
After disassembling the bean class file I noticed that the static version
strings were listed as the old hibernate version. So this turned out to just
be a build path issue in eclipse that kicked by butt.
Thanks for looking into it, jaikiran!
justin.
View the original post :
http://www.jboss
Sure.
MyManagedIfc.java
| package org.myOrg;
|
| import org.jboss.annotation.ejb.Management;
|
| @Management
| public interface MyManagedIfc {
|void create() throws Exception;
|void start() throws Exception;
|void stop();
|void destroy();
|
Well I tried to do you one better and create a simple project that illustrates
the problem. I created two projects in eclipse (myEjb and myEar), built and
deployed them. As expected, the service bean printed out the old hibernate
versions. I then wrote an ant script to build the same projects
OK, I can't seem to get this working. I'm clearly doing something wrong.
Essentially, I want my ear application to use hibernate v3.2.6. Here is the
structure of my ear (containing the upgraded hibernate):
| myEar
| |-- META-INF
| | |-- application.xml
| | |-- jboss-app.xml
| |
thanks!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170294#4170294
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170294
___
jboss-user mailing list
jboss-user@lists.jboss.
Argh, forum didn't like the formatting in my original post. The path I meant to
type is: /server/< config >/lib/
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170180#4170180
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply
Hi,
I have an application that requires an upgrade to the version of hibernate that
is bundled with JBoss 4.2.2.GA. If I bundle the new hibernate jars in my
application ear, will my application be guaranteed to use the upgraded version
as opposed to the version bundled in server//lib/? Or, do
21 matches
Mail list logo
