January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1015) ServiceDelegateWrapper should delegate MBeanRegistration and NotificationEmitter calls

by Galder Zamarreno (JIRA)

ServiceDelegateWrapper should delegate MBeanRegistration and NotificationEmitter calls -------------------------------------------------------------------------------------- Key: EJBTHREE-1015 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1015 Project: EJB 3.0 Issue Type: Feature Request Components: EJB3 Extensions Affects Versions: AS 4.2.1.GA Reporter: Galder Zamarreno Fix For: AS 4.2.2.GA ServiceDelegateWrapper should delegate MBeanRegistration and NotificationEmitter calls to EJB3 Services if users made their EJB3 services implement these interfaces. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-754) isCallerInRole checks should go through JACC layer (if JACC is configured)

by Anil Saldhana (JIRA)

isCallerInRole checks should go through JACC layer (if JACC is configured) -------------------------------------------------------------------------- Key: EJBTHREE-754 URL: http://jira.jboss.com/jira/browse/EJBTHREE-754 Project: EJB 3.0 Issue Type: Task Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Scott M Stark Fix For: EJB 3.0 RC10 - FD Since Scott is going to review the ejb3 JACC implementation, I am assigning this issue to Scott. The EJBContext.isCallerInRole checks need to go through the jacc layer, if the user has configured jacc. I am not sure what the best way to tell the xxxContext layer to use jacc helper if user desires. Maybe a simple system property may do it. -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1132) EJB3 tests should not assume server is bound to localhost

by Brian Stansberry (JIRA)

EJB3 tests should not assume server is bound to localhost --------------------------------------------------------- Key: EJBTHREE-1132 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1132 Project: EJB 3.0 Issue Type: Task Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: AS 5.0.0.Beta3, Branch_4_2 A number of EJB3 tests are hard coding localhost in various URLs. Should be the value returned by system property jbosstest.server.host, which build-test.xml should set to the value of ant property ${node0}. -- 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, 3 months

2
3
0 / 0

[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

14 years, 3 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

14 years, 3 months

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

14 years, 3 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

14 years, 3 months

5
13
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

14 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-884) META-INF/orm.xml should be read for both the main persistence jar and all the explicit jars

by Emmanuel Bernard (JIRA)

META-INF/orm.xml should be read for both the main persistence jar and all the explicit jars ------------------------------------------------------------------------------------------- Key: EJBTHREE-884 URL: http://jira.jboss.com/jira/browse/EJBTHREE-884 Project: EJB 3.0 Issue Type: Task Reporter: Emmanuel Bernard Priority: Minor Fix For: EJB 3.0 RC10 - FD See http://opensource.atlassian.com/projects/hibernate/browse/EJB-259 I've fixed the issue in HEM, but it worth having a testcase in the container's code base to be safe -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-872) Unable to call EJB Remotely

by Henning Vogt (JIRA)

Unable to call EJB Remotely --------------------------- Key: EJBTHREE-872 URL: http://jira.jboss.com/jira/browse/EJBTHREE-872 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC9 - FD Environment: two separate, non clustered jbosses Reporter: Henning Vogt Fix For: EJB 3.0 RC10 - FD See also the linked bug for detailed descripton. Calling a remote SLSB does not work, if the equally named SLSB is deployed on the calling JBoss. See also: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96098 and http://jira.jboss.com/jira/browse/EJBTHREE-823 and numerous other topics on this. In my opinion, ther should be an easier way to do this, instead of writing your own interceptor, patching JBoss or the like. Also, in a non clustered environment, if you give a hostname to the InitialContext(), you should get the remote server session beans, regardless of possibly locally deployed equally named stateless sessionbeans. -- 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, 3 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008