Yes, the new jbossall-client.jar with the references only. I have a high
inhibition threshold to post in this forum, so I check things like Class-Path
several times ;-)
I found the problem: I've included my ejb-jar into my small test client to make
available the EJB interfaces. Eclipse adds the
Hello everyone,
i try to migrate my JBoss 4.2.2 Application (and an Eclipse based remote
client) to JBoss 5.0.0.
I am getting some exceptions during remote calls of SLSBs and SFSBs on my
client.
The context creation and lookup has been performed correctly. As I see in the
server log, the SFSB
Using Hibernate 3 i could define composite-elements like @Embeddable with Java
Persistence.
But Hibernate also allows collections of those composite-element's.
|
| ...
|
|
|
|
|
| ...
|
|
| ...
|
Solved it myself using JDK 1.5 instead of JDK 1.6 for client and JBoss.
Are there known problems with JBoss and Java 6? My remote clients run on the
Eclipse Rich Client Platform and i think, i cant hope that no one of my users
will upgrade to Java 6...
View the original post :
http://www.jboss
Got a ClassLoader-Problem with EJB 3's Stateful Session Bean's i don't
unterstand.
Have got included all required Client-JAR's (incl. jboss-aop-jdk50-client.jar).
Stateless Session Bean's are working fine, but if i look up for a Stateful i am
getting a problem with a ClassLoader, can't find
org
