March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-299) Cobertura 1.9.4.1

by Jesper Pedersen (JIRA)

Cobertura 1.9.4.1 ----------------- Key: JBJCA-299 URL: https://jira.jboss.org/jira/browse/JBJCA-299 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha10 -- 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

14 years, 9 months

1
0
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

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-1172) UnicastTestRpcDist: show perf numbers for reads and writes separately

by Bela Ban (JIRA)

UnicastTestRpcDist: show perf numbers for reads and writes separately --------------------------------------------------------------------- Key: JGRP-1172 URL: https://jira.jboss.org/jira/browse/JGRP-1172 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.10 In addition to requests -- 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

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7574) Update the AS build to prevent jboss-ejb-api jar from being added to common/lib

by jaikiran pai (JIRA)

Update the AS build to prevent jboss-ejb-api jar from being added to common/lib ------------------------------------------------------------------------------- Key: JBAS-7574 URL: https://jira.jboss.org/jira/browse/JBAS-7574 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: JBossAS-6.0.0.M2 As part of JBAS-7557, the jboss-ejb-api jar is being included in the AS/common/lib. This jar has *some* duplicate javax.ejb.* classes which are present in jboss-javee.jar. Once JBEE-15 is resolved and a new version of jboss-javaee released, we will no longer have to add jboss-ejb-api jar to AS/common/lib. -- 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

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-7762) Upgrade web

by Remy Maucherat (JIRA)

Upgrade web ----------- Key: JBAS-7762 URL: https://jira.jboss.org/jira/browse/JBAS-7762 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Remy Maucherat Assignee: Remy Maucherat -- 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

14 years, 10 months

1
2
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

14 years, 10 months

4
6
0 / 0

[JBoss JIRA] Closed: (JBREM-398) bring AOP Remoting under JBossRemoting project

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-398?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-398. ----------------------------- Resolution: Out of Date > bring AOP Remoting under JBossRemoting project > ---------------------------------------------- > > Key: JBREM-398 > URL: https://jira.jboss.org/jira/browse/JBREM-398 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Reporter: Tom Elrod > > Need to bring AOP Remoting under the JBossRemoting project for further development and maintenance. -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-505) convert jndi to use remoting for transport

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-505?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-505. ----------------------------- Resolution: Duplicate Issue Duplicates JBAS-3151. > convert jndi to use remoting for transport > ------------------------------------------ > > Key: JBREM-505 > URL: https://jira.jboss.org/jira/browse/JBREM-505 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: External_issues > Reporter: Tom Elrod > > Need to convert jndi to use remoting as transport. Ties in with JBREM-424. -- 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

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-445) create guide for connecting externally through NAT from multiple ejb3 clients

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-445?page=com.atlassian.jira.plug... ] David Lloyd closed JBREM-445. ----------------------------- Resolution: Out of Date Assignee: (was: Tom Elrod) > create guide for connecting externally through NAT from multiple ejb3 clients > ----------------------------------------------------------------------------- > > Key: JBREM-445 > URL: https://jira.jboss.org/jira/browse/JBREM-445 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Reporter: Tom Elrod > Fix For: External_issues > > -- 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

14 years, 10 months

1
0
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

14 years, 10 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010