I'm using hibernate inside JBoss with an Oracle datasource. Usually when I do
JDBC queries against the datasource it uses the schema as defined in the
-ds.xml. But with hibernate I have to add the hibernate.default_schema property
in persistence.xml too:
|
| java:/MainDS
| .
Should deployers/metadata-deployer-jboss-beans.xml contain some stuff about the
5_1 deployment descriptors?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238818#4238818
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=42
I'm still getting the "jboss.xml is not well formed!" exception, even with an
empty jboss.xml:
| http://www.jboss.com/xml/ns/javaee";
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
| xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
|
Thanks. Moving the local-jndi-name and jndi-name elements makes the xml at
least in validate from within IDEA.
The deployment is still failing and it's less clear where the problem is now:
| Caused by: java.lang.Exception: The xml
deployfile.ear/bingo-ejbs.jar/META-INF/jboss.xml is not well
I'm having trouble getting an existing application to deploy on 5.1.0.GA. It
deploys fine on 4.2.x.
I'm using ignore-dependency elements in jboss.xml to handle circular references
and it's causing problems with descriptor validation (I can't use the
annotation because the code has to be portabl
That's a pretty rubbish workaround. The only one I've come up with that doesn't
involve lots of changes to existing code is to not use JBoss 5. It's very
disappointing.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178471#4178471
Reply to the post :
http:/
Check for any circular dependencies. JBoss doesn't like them but doesn't
actually tell you so.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178250#4178250
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178250
___
I'm getting this exception too. The ear contains a mixture of EJB2 modules and
EJB3 ones. Some of the EJB3 beans depend on EJB2 ones (via ejb-local-refs).
Could this be what's triggering the bug?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167584#4167584
Stateless EJBs are only stateless in the sense that they're not associated with
any particular client session.
The actual EJB instances can and will be pooled by the application server.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159612#4159612
Reply to t
I haven't tried this, but you should be able to add EJB 2.1 client home with
the @RemoteHome annotation.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146436#4146436
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=41464
I've got lots of cyclic dependencies between SLSBs which are apparently not
allowed with EJB3 beans on JBoss. Tracking down the exact dependencies that
JBoss doesn't like takes a long time, but adding @IgnoreDependency around the
place has fixed most of them.
The problem is that I've got some c
Should I be able to inject EJB2 homes into EJB3 beans?. This used to work on
5.0.0.Beta4 but doesn't with the latest 5.0.0 HEAD build - I'm trying to
upgrade due to a problem with JBossWebRealm (fixed in r69776).
I've got an EJB3 SLSB declared using annotations. I'm injecting an EJB2 entity
hom
I can cut the startup time to about 5mins by changing
org.jboss.ejb3.dependency.EjbLinkDemandMetaData with the following patch.
I stole some code from the ObjectName constructor. It's quick, dirty and not
production quality but proves the point that relying on Exceptions for flow
control is a b
I should add that there are dependency errors for about 40 different beans once
the server finally starts up.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139215#4139215
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=
I've got an ear with about 30 EJB modules. The modules are either all entity
beans or all SLSBs/MDBs (this is to let us migrate session beans to EJB3
without having to do the entities at the same time).
I've got two versions of the same ear: one pre-migration with all EJB2 modules,
and one wher
What URL are you requesting? index.jsp or index.jsf?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034986#4034986
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034986
___
jb
It looks like your class com.fabulous_valley.web.MyPhaseListener does implement
the PhaseListener interface.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028799#4028799
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4
I agree - the state of EJB unit testing does seem to be a bit depressing. A lot
of these projects are dormant.
We're using MockEJB for some out of container testing of EJBs here, though we
don't do anything too complex. It may be that it doesn't have the feature you
need. A forum post indicated
There are a few frameworks for testing EJBs:
MockEJB:
http://www.mockejb.org/
Cactus:
http://jakarta.apache.org/cactus/index.html
JUnitEE:
http://www.junitee.org/
and I'm sure there are more hanging around the web somewhere. Out of those
three MockEJB is the only one that runs outside the app
In your first code snippet you're using annotations to get the reference to the
queue: @Resource(mappedName="queue/A") Queue queue;
In the second you're using a JNDI lookup.
I've not used annotations to do this sort of thing so don't know much about how
that's supposed to work, but that appears
You could try Hibernate validations:
http://www-128.ibm.com/developerworks/java/library/j-hibval.html
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978751#3978751
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978751
No. JBoss is free, open source software.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971879#3971879
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971879
___
jboss-user mai
No, that's not what he said.
JBoss uses multiple threads. To illustrate this you could have a look at a
thread dump (see the wiki).
The operating system (Windows, Linux, FreeBSD, etc..) will then be able to
schedule the threads on as many CPUs as are available.
PeterJ's comment is just how th
Why not just use the minimal configuration that comes with JBoss? Use the
following to start JBoss: run.bat -c minimal
Or if you're just using JSPs and servlets you could use plain Tomcat and get
rid of JBoss altogether.
Also see the wiki.
View the original post :
http://www.jboss.com/index.h
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=88064
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963609#3963609
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963609
When you're looking up the queue, you need to use HA-JNDI with a URL that
points to all of the nodes in the cluster. E.g. For a three node cluster the
JNDI URL could be:
192.168.0.1:1100,192.168.0.2:1100,192.168.0.3:1100
The client will then try each server in turn until it reaches one. There i
Firstly, I'd upgrade JBoss and check that your JDK is up to date.
Stack traces:
http://wiki.jboss.org/wiki/Wiki.jsp?page=StackTrace
http://wiki.jboss.org/wiki/Wiki.jsp?page=GenerateAThreadDumpWithTheJMXConsole
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961
Google for "JMS" or "Java messaging".
JMS is part of J2EE and not JBoss-specific.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959533#3959533
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959533
This is expected behaviour. SLSB aren't stateless in the sense that a new one
is created with every call (the application server will be doing pooling etc).
They are stateless in the sense that they are not tied to a particular client
like Stateful Session EJBs are.
A good explanation can be fo
29 matches
Mail list logo
