Sorry for poluting this forum with my stupidity :(. Turned to be a classloader
problem - another mc 1.0.2 jar (from Seam) which loaded before the deployer.
Please remove this topic, if possible.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934222#3934222
R
Investigation: JBossBeanDeployer.getSchemaBinding(..) calling
BeanSchemaBinding.getSchemaBinding() gives that NullPointerException.
Looks like a problem accessing the deployment xsd?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934221#3934221
Reply to the
To add to my prev. posting - those results I got with sourceforge packaged
versions of JBoss, tried default and all servers.
Then built 4.0.4RC1 with java 1.5.0_06 and got exactly the same.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934190#3934190
Reply
MC 1.0.2 works perfecty. So being an adventureous type - I tried deployed my
POJO inside AS.
Did not fly and I wonder if anyone has ancountered the same issues.
My investigation points towards jboss-xml-bindings.jar and jboss-commons.jar.
The test.beans folder contains two files:
test.beans/Te
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