[JBoss Tools (users)] - Re: Wrong JBossTools Entity Generation on DB Table Name with
by max.andersen＠jboss.com
kabil,
No really fun to have wait 1 minute for a simple download...next time please just show the relevant part of the file instead of everything.
The error says that it has a problem finding the property oTestTestTestTest in home.xhtml - but there is no such reference in the files you sent.
What did you do to get the error ?
In any case I think I know what is causing the error. Your table starts with o_test which result in OTest which in javabeans spec result in the property to be named OTest and not oTest because of the double capitals. I got a feeling that Seam-gen's templates does not "obey" those rules strictly enough as the code generation does.
So if you go an rename whatever reference you have from oTest... to OTest it should work.
In any case I think what is the problem
And looking at the class OTestTestTestTestList.java the method getOTestTestTestTestList
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197772#4197772
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197772
17 years, 4 months
[EJB/JBoss] - Re: EJB lookup failure in 5.0.0.GA
by jhsingle
Here is the exception stacktrace:
java.lang.ClassCastException: javax.naming.Reference
| at security.ejb.server.SecurityManagerRemoteFactory.createSecurityManangerRemote(SecurityManagerRemoteFactory.java:44)
| at security.ejb.server.SecurityManagerTest.cleanup(SecurityManagerTest.java:760)
| at security.ejb.server.SecurityManagerTest.setUp(SecurityManagerTest.java:742)
| at junit.framework.TestCase.runBare(TestCase.java:128)
| at junit.framework.TestResult$1.protect(TestResult.java:106)
| at junit.framework.TestResult.runProtected(TestResult.java:124)
| at junit.framework.TestResult.run(TestResult.java:109)
| at junit.framework.TestCase.run(TestCase.java:120)
| at junit.framework.TestSuite.runTest(TestSuite.java:230)
| at junit.framework.TestSuite.run(TestSuite.java:225)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
| at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
| at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
| at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
| at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
|
Here is the toString of the object returned by the lookup:
EJB lookup returned: Reference Class Name: Proxy for: security.ejb.client.SecurityManagerRemote
| Type: ProxyFactoryKey
| Content: ProxyFactory/SecurityManager/usermgmt/SecurityManager/remote
| Type: EJB Container Name
| Content: jboss.j2ee:ear=usermgmt.ear,jar=usermgmt-ejb-2.7.0.jar,name=SecurityManager,service=EJB3
| Type: Proxy Factory is Local
| Content: false
| Type: Remoting Host URL
| Content: socket://Macintosh.home:3873/?
| Type: Remote Business Interface
| Content: security.ejb.client.SecurityManagerRemote
As far as using jbossall-client.jar from the distro client directory, there is a problem there. My client, a JUnit test, like everything else in our project uses a Maven2 build. So we don't point to any local directories, but rather our pom.xml file points to artifacts from networked maven repositories. I was unable to locate the client jar files in the current jboss maven repository (http://repository.jboss.org/maven2/) so for this test I loaded the jbosssx-as-client.jar from the distribution client directory into our local project maven repository. This raises two questions: (1) are the JBoss5 client jars available in any maven repository, and (2) given the indirect nature of jbossall-client.jar, will it even work with maven, or do I need to name all of the referenced jar files in my pom for this test?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197768#4197768
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197768
17 years, 4 months