September 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-724) persistence.xml jar-file processing

by Heiko W. Rupp (JIRA)

persistence.xml jar-file processing ----------------------------------- Key: EJBTHREE-724 URL: http://jira.jboss.com/jira/browse/EJBTHREE-724 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Heiko W. Rupp EJB 3 persistence spec says in 6.2.1.6, 2nd paragraph about <jar-file> "Such JAR files are specified relative to the root of the persistence unit (e.g.,utils/myUtils.jar)" When I have a persistence.xml like this: <persistence> <persistence-unit name="jon"> <jta-data-source>java:/JONDS</jta-data-source> <jar-file>lib/on-enterprise-server-2.0-SNAPSHOT.jar</jar-file> </persistence-unit> </persistence> The PersistenceUnitDeployment gives file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar] but the root of the PersistenceUnit is file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/on-enterprise-server-entity-ejb-2.0-SNAPSHOT.jar/ 2006-10-04 18:00:43,537 DEBUG [org.jboss.ejb3.entity.PersistenceUnitDeployment] Found persistence.xml file in EJB3 jar 2006-10-04 18:00:43,538 DEBUG [org.jboss.ejb3.entity.PersistenceUnitDeployment] adding JarFile URL: file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar 2006-10-04 18:00:43,586 INFO [org.hibernate.ejb.Version] Hibernate EntityManager 3.2.0.CR2 2006-10-04 18:00:43,625 INFO [org.hibernate.cfg.annotations.Version] Hibernate Annotations 3.2.0.CR2 2006-10-04 18:00:43,638 INFO [org.hibernate.cfg.Environment] Hibernate 3.2 cr4 2006-10-04 18:00:43,649 INFO [org.hibernate.cfg.Environment] hibernate.properties not found 2006-10-04 18:00:43,654 INFO [org.hibernate.cfg.Environment] Bytecode provider name : javassist 2006-10-04 18:00:43,666 INFO [org.hibernate.cfg.Environment] using JDK 1.4 java.sql.Timestamp handling 2006-10-04 18:00:43,906 DEBUG [org.hibernate.ejb.Ejb3Configuration] Processing PersistenceUnitInfo [ name: jon persistence provider classname: org.hibernate.ejb.HibernatePersistence classloader: org.jboss.mx.loading.UnifiedClassLoader3@3b31a6{ url=file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/ ,addedOrder=43} Temporary classloader: null excludeUnlistedClasses: false JTA datasource: org.jboss.resource.adapter.jdbc.WrapperDataSource@c90acb Non JTA datasource: null Transaction type: JTA PU root URL: file:/jboss-4.0.5.CR1/server/jon/deploy/on.ear/on-enterprise-server-entity-ejb-2.0-SNAPSHOT.jar/ Jar files URLs [ file:/jboss-4.0.5.CR1/bin/lib/on-enterprise-server-2.0-SNAPSHOT.jar] Managed classes names [] Mapping files names [] Properties [ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1633) setMessageDrivenContext callback is not made to optional MessageDriven interface

by Andrew Lee Rubinger (JIRA)

setMessageDrivenContext callback is not made to optional MessageDriven interface -------------------------------------------------------------------------------- Key: EJBTHREE-1633 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1633 Project: EJB 3.0 Issue Type: Bug Components: core Environment: EJB3 Integration TestSuite: org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testQueue Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-CR1 The required callback to setMessageDrivenContext is not made in MDBs EJB 3.0 Core 5.4.6: The setMessageDrivenContext method is called by the bean's container to associate a mes- sage-driven bean instance with its context maintained by the container. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-121) Javassist based reflection objects uses the compiler

by Adrian Brock (JIRA)

Javassist based reflection objects uses the compiler ---------------------------------------------------- Key: JBMICROCONT-121 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-121 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The JavassistReflectionFactory builds up a source to compile the method, constructor and field accesors. These implementations are faster than the normal reflection equivalents, but using the compiler is slow. These methods should be optimized to generate the bytecode directly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

6
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1252) @PersistenceContext injection from a different jar fails

by jaikiran pai (JIRA)

@PersistenceContext injection from a different jar fails -------------------------------------------------------- Key: EJBTHREE-1252 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1252 Project: EJB 3.0 Issue Type: Bug Components: injection Affects Versions: AS 4.2.2.GA Environment: JBoss-4.2.2GA, Windows 2003 Server, Sun Java 1.5 Reporter: jaikiran pai I have a sample application with an EJB3 SLSB which is being injected with a PersistenceContext which is configured in a different jar file as follows package org.myapp.ejb.impl; import javax.ejb.Remote; import javax.ejb.Stateless; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; import org.jboss.annotation.ejb.RemoteBinding; import org.myapp.ejb.AppManager; @Stateless @Remote ({AppManager.class}) @RemoteBinding (jndiBinding = "AppManagerBean") public class AppManagerBean implements AppManager { @PersistenceContext (unitName="myapp_ejb3.jar#EJB3Persistence") private EntityManager em; public String getVersion() { System.out.println("EM is " + em); return "1.0"; } } The application is deployed as an EAR file in the following structure: EJB3Persistence.ear | |--- META-INF | | | |--- META-INF | | | | | |--- application.xml | | | | | |--- jboss-app.xml | | |--- myapp_ejb3.jar (contains the persistence.xml) | | | |--- META-INF | | | | | |--- persistence.xml | | | |--- another_ejb3.jar (contains the SLSB) | | | | | |--- META-INF | | | |--- org.myapp.ejb.impl.AppManagerBean When this application is deployed in 4.2.2 the deployment fails with an exception. Part of the exception is pasted below. The relevant log files (ConsoleLog_Fail.txt and serverLog_fail.txt in the logs.zip file) are attached. 22:45:41,137 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer 22:45:41,152 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=EJB3Persistence.ear,jar=another_ejb3.jar,name=AppManagerBean,service=EJB3 with dependencies: 22:45:41,152 INFO [JmxKernelAbstraction] persistence.units:jar=pp_ejb3.jar,unitName=EJB3Persistence 22:45:41,152 INFO [EJB3Deployer] Deployed: file:/D:/JBoss-4.2.2/jboss-4.2.2.GA/server/default/tmp/deploy/tmp53619EJB3Persistence.ear-contents/another_ejb3.jar 22:45:41,168 INFO [EARDeployer] Started J2EE application: file:/D:/JBoss-4.2.2/jboss-4.2.2.GA/server/default/deploy/EJB3Persistence.ear 22:45:41,184 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:ear=EJB3Persistence.ear,jar=another_ejb3.jar,name=AppManagerBean,service=EJB3 State: NOTYETINSTALLED I Depend On: persistence.units:jar=pp_ejb3.jar,unitName=EJB3Persistence --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: persistence.units:jar=pp_ejb3.jar,unitName=EJB3Persistence State: NOTYETINSTALLED Depends On Me: jboss.j2ee:ear=EJB3Persistence.ear,jar=another_ejb3.jar,name=AppManagerBean,service=EJB3 If i change the PersistenceContext injection, in the bean, to prefix 3 random letters to the unitName as follows: @PersistenceContext (unitName="XXXmyapp_ejb3.jar#EJB3Persistence") private EntityManager em; and deploy the application, then everything works fine (have also attached the successful logs ConsoleLogs_Success.txt and serverLogs_Success.txt in the logs.zip file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBREM-661) Allow server sending a stream to the client

by Helmut Wick (JIRA)

Allow server sending a stream to the client ------------------------------------------- Key: JBREM-661 URL: http://jira.jboss.com/jira/browse/JBREM-661 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Helmut Wick Assigned To: Tom Elrod As of release 2.0.0 GA, there is no way for a server to send a stream to the client (only the other way around). This is to request something like java.io.InputStream Client.invoke(java.lang.Object param) that allows for true streaming (like java.lang.Object invoke(java.io.InputStream inputStream, java.lang.Object param) does). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

4
6
0 / 0

[JBoss JIRA] Created: (JBREM-566) update jbossws to include 2.0.0 in component-info.xml

by Tom Elrod (JIRA)

update jbossws to include 2.0.0 in component-info.xml ----------------------------------------------------- Key: JBREM-566 URL: http://jira.jboss.com/jira/browse/JBREM-566 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: External_issues Have already e-mailed ws team. Need this to be updated in repository or won't be able to update build-thirdpary.xml within jbossas. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-567) Update ejb3 project for use of 2.0.0 of remoting

by Tom Elrod (JIRA)

Update ejb3 project for use of 2.0.0 of remoting ------------------------------------------------ Key: JBREM-567 URL: http://jira.jboss.com/jira/browse/JBREM-567 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: External_issues Need to make sure 'xmbean-dd="org/jboss/remoting/transport/Connector.xml" is removed from all the service descriptors, as Connector is now a standard mbean and not an xmbean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBREM-565) integration testing for 2.0.0 release

by Tom Elrod (JIRA)

integration testing for 2.0.0 release ------------------------------------- Key: JBREM-565 URL: http://jira.jboss.com/jira/browse/JBREM-565 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.CR1 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.GA (Boon) Need to do some integration testing with new 2.0.0.CR1 of remoting with JBossAS 4 & 5 to make sure everything is working correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7196) Deployment fails with slash in manifest.mf - main-class attribute

by Per Newgro (JIRA)

Deployment fails with slash in manifest.mf - main-class attribute ----------------------------------------------------------------- Key: JBAS-7196 URL: https://jira.jboss.org/jira/browse/JBAS-7196 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.1.0.GA Environment: Windows XP Reporter: Per Newgro Assignee: Ales Justin I have an ear. It contains an application.xml in Meta-inf and a jar in root. The jar contains a single class. The main-class attribute of the jar mainfest contains value Mytest/Mytest. Everything works if i change the attribute value to Mytest.Mytest. But it's an external library and so this can't be the solution. On depoyment i get 14:23:46,936 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfszip:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/my.ear/ state=ClassLoader mode=Manual required State=PostClassLoader org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/my.ear/Mytest.jar/Mytest/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NoClassDefFoundError: IllegalName: Mytest/Mytest at java.lang.ClassLoader.preDefineClass(ClassLoader.java:476) at java.lang.ClassLoader.defineClass(ClassLoader.java:614) at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:63) at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:572) at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:532) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:530) at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:507) at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:134) at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:452) at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:251) at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:150) at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:265) at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1119) at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:798) at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:441) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.deployment.OptAnnotationMetaDataDeployer.processJBossClientMetaData(OptAnnotationMetaDataDeployer.java:115) at org.jboss.deployment.OptAnnotationMetaDataDeployer.processMetaData(OptAnnotationMetaDataDeployer.java:82) at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:177) at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:93) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) ... 31 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-7153) org.jboss.test.web.test.JSFInjectionUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.web.test.JSFInjectionUnitTestCase ------------------------------------------------ Key: JBAS-7153 URL: https://jira.jboss.org/jira/browse/JBAS-7153 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2009