September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-772) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: EJBTHREE-772 URL: http://jira.jboss.com/jira/browse/EJBTHREE-772 Project: EJB 3.0 Issue Type: Task Reporter: Rajesh Rajasekaran Fix For: EJB 3.0 RC10 - FD Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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

15 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1034) Port ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to Branch_4_2

by Frank Langelage (JIRA)

Port ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to Branch_4_2 ------------------------------------------------------------------------------------------ Key: EJBTHREE-1034 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1034 Project: EJB 3.0 Issue Type: Patch Affects Versions: AS 4.2.2.GA Reporter: Frank Langelage Fix For: AS 4.2.2.GA Port the changes made on ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java in Head to Branch 4.2. Using an ear with seperated session and entity beans (different ejb-modules) I got the exception "There is no default persistence nit in this deployment." when using "@PersistenceContext private EntityManager entityManager;" in my Session Bean. Using the head version of the source file within my 4.2.2.GA cvs checkout the problem went away. -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-421) Put FlushMode.NEVER back on track through @FlushMode, at least in a proprietary manner

by Carlo de Wolf (JIRA)

[ https://jira.jboss.org/browse/EJBTHREE-421?page=com.atlassian.jira.plugin... ] Carlo de Wolf resolved EJBTHREE-421. ------------------------------------ Resolution: Out of Date This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of JBoss EJB 3 please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. > Put FlushMode.NEVER back on track through @FlushMode, at least in a proprietary manner > -------------------------------------------------------------------------------------- > > Key: EJBTHREE-421 > URL: https://jira.jboss.org/browse/EJBTHREE-421 > Project: EJB 3.0 > Issue Type: Feature Request > Reporter: Emmanuel Bernard > Fix For: Branch_4_2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCOMMON-6) Archive Browser does not support jar:file: url protocol

by Chris Mercer (JIRA)

Archive Browser does not support jar:file: url protocol ------------------------------------------------------- Key: JBCOMMON-6 URL: http://jira.jboss.com/jira/browse/JBCOMMON-6 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: core Environment: jdk 1.5.8 jboss 4.0.4ga hibernate 3.2cr2 hibernate entity manager 3.2.0.CR1 Using ejb3/entity manager annotations Reporter: Chris Mercer Assigned To: Dimitris Andreadis Priority: Critical We have a seperate jar file that contains all of our model/entity objects. This jar gets put in the WEB-INF/lib directory, since we are only using wars and not ears. Using the hibernate auto-discovery feature causes an exception to occur. In this configuration. Caused by: java.lang.RuntimeException: NOT IMPLEMENTED at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:42) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:541) ... 148 more org.jboss.util.file.ArchiveBrowser.getBrowser(URL url, Filter filter) only supports URLS that have a protocol of "file". However, jars have a protocol of "jar:file:" and therefore it will throw a RuntimeException saying "NOT IMPLEMENTED" (at least according to my debugger). There is already a JarArchiveBrowser class, the ArchiveBrowser just needs to recognize the protocol and handle it. This also affects Hibernate entity manager, since it gets included in the jboss-archive-browsing.jar in order to handle the auto-discovery of mapped entities feature. I've marked this as critical, since it effects entity manager features (though its only advanced hibernate only functionality) -- 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

15 years, 8 months

11
22
0 / 0

[JBoss JIRA] Created: (EJBTHREE-832) HEM using JBossCache raise a CCE

by Emmanuel Bernard (JIRA)

HEM using JBossCache raise a CCE -------------------------------- Key: EJBTHREE-832 URL: http://jira.jboss.com/jira/browse/EJBTHREE-832 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Emmanuel Bernard Priority: Blocker Fix For: EJB 3.0 RC10 - FD Acording to Gavin In persistence.xml: <property name="hibernate.cache.provider_class" value="org.hibernate.cache.OptimisticTreeCacheProvider"/> And I got: 00:39:56,421 INFO [SettingsFactory] Cache provider: org.hibernate.cache.OptimisticTreeCacheProvider 00:39:56,421 WARN [ServiceController] Problem starting service persistence.units:ear=jboss-seam-registration.ear,jar=jboss-seam-registr ation.jar,unitName=userDatabase java.lang.RuntimeException: java.lang.NoClassDefFoundError: org/jboss/cache/TransactionManagerLookup at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrappe r.java:108) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp ort.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean Support.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy190.start(Unknown Source) at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:96 ) at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java: 467) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:317) at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp ort.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean Support.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy36.start(Unknown Source) at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:449) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor. java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBea nOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.ja va:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorSe rviceMBeanSupport.java:238) at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterce ptor.java:92) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.sta rt(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerIntercepto r.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy37.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor. java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBea nOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy6.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc anner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan ner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doS can(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loo p(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run (AbstractDeploymentScanner.java:225) Caused by: java.lang.NoClassDefFoundError: org/jboss/cache/TransactionManagerLookup at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Unknown Source) at java.lang.Class.getConstructor0(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.hibernate.cfg.SettingsFactory.createCacheProvider(SettingsFactory.ja va:358) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:232 ) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1933) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1 216) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Config uration.java:688) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFacto ry(HibernatePersistence.java:127) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDep loyment.java:264) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrappe r.java:102) ... 92 more -- 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

15 years, 8 months

5
13
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-344) Deployment should fail for resource injection to both field and method

by Carlo de Wolf (JIRA)

[ https://jira.jboss.org/browse/EJBTHREE-344?page=com.atlassian.jira.plugin... ] Carlo de Wolf resolved EJBTHREE-344. ------------------------------------ Resolution: Out of Date This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of JBoss EJB 3 please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. > Deployment should fail for resource injection to both field and method > ---------------------------------------------------------------------- > > Key: EJBTHREE-344 > URL: https://jira.jboss.org/browse/EJBTHREE-344 > Project: EJB 3.0 > Issue Type: Bug > Environment: org.jboss.ejb3.test.naming.unit.BadInjectionsUnitTestCase > Reporter: Scott M Stark > Assignee: William DeCoste > Fix For: Branch_4_2 > > > I belive the indicated BadInjectionsUnitTestCase should be failing to deploy due to the attempt to inject an env-entry via both a field and method annotation. The ejb-jar.xml key env-entry value is not being injected via either mechanism it appears. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-322) implement discarding rules

by Carlo de Wolf (JIRA)

[ https://jira.jboss.org/browse/EJBTHREE-322?page=com.atlassian.jira.plugin... ] Carlo de Wolf resolved EJBTHREE-322. ------------------------------------ Resolution: Out of Date This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of JBoss EJB 3 please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. > implement discarding rules > -------------------------- > > Key: EJBTHREE-322 > URL: https://jira.jboss.org/browse/EJBTHREE-322 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC1, EJB 3.0 RC2, EJB 3.0 RC3 > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: Branch_4_2 > > > we are not discarding EJB instances where appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1891) ServiceContainer may not be popping the Principal

by Anil Saldhana (JIRA)

ServiceContainer may not be popping the Principal ------------------------------------------------- Key: EJBTHREE-1891 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1891 Project: EJB 3.0 Issue Type: Bug Components: core Reporter: Anil Saldhana Fix For: Branch_4_2 AS described in the forum thread, there may not be a pop of the principal on return. Please investigate. -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-729) Injecting a EJB 2.1 bean in EJB 3 bean can show misleading warning message: IGNORING DEPENDENCY:...

by Galder Zamarreno (JIRA)

Injecting a EJB 2.1 bean in EJB 3 bean can show misleading warning message: IGNORING DEPENDENCY:... --------------------------------------------------------------------------------------------------- Key: EJBTHREE-729 URL: http://jira.jboss.com/jira/browse/EJBTHREE-729 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Galder Zamarreno Fix For: EJB 3.0 RC10 - FD An EJB 2.1 bean injected in a EJB 3 bean via: @EJB(mappedName="ejb/IdGenerator") private IdGeneratorHome idGeneratorHome; leads to the following warning message being logged: "server.log:6202:2006-10-05 14:28:36,171 WARN [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only com.acme.ejb2.uuid.IdGeneratorHome in ejb-jar.xml of SqlTimeStampBeannot used by any EJBs" The message is misleading as it seems to indicate that the dependency was not set, but it actually did. Create call on the home interface works returning a valid bean. -- 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

15 years, 8 months

3
7
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-342) Unify configuration file names and bootstrap

by Carlo de Wolf (JIRA)

[ https://jira.jboss.org/browse/EJBTHREE-342?page=com.atlassian.jira.plugin... ] Carlo de Wolf resolved EJBTHREE-342. ------------------------------------ Resolution: Out of Date This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of JBoss EJB 3 please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. > Unify configuration file names and bootstrap > -------------------------------------------- > > Key: EJBTHREE-342 > URL: https://jira.jboss.org/browse/EJBTHREE-342 > Project: EJB 3.0 > Issue Type: Bug > Reporter: Christian Bauer > Assignee: Bill Burke > Fix For: Branch_4_2 > > > The microcontainer can be booted with StandaloneBootstrap, and it searches for jboss-beans.xml in / and META-INF. > The E-EJB3 container is booted with EJB3StandaloneBootstrap, which searches for embedded-jboss-beans.xml in / and supports a "basepath" argument. > Unify these two bootstrap classes. Wishlist: > - sensible default name for the configuration file ("jboss-beans.xml" sounds good) > - searches in default locations (/ and META-INF) > - supports parameters to completely override not only the "basepath", but the full location of the configuration file > The EJB3StandaloneBootstrap should _extend_ the StandaloneBootstrap, not reimplement it. The current situation makes documentation and explanation unecessarily difficult. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

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