March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBLOGGING-38) Enforce JDK6+ compiler

by Andrew Lee Rubinger (JIRA)

Enforce JDK6+ compiler ---------------------- Key: JBLOGGING-38 URL: https://jira.jboss.org/jira/browse/JBLOGGING-38 Project: JBoss Logging Issue Type: Task Security Level: Public (Everyone can see) Components: jboss-logmanager Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Using JDK5 leads to: [INFO] Compilation failure /home/alr/business/jboss/wc/common/jboss-logmanager/trunk/src/main/java/org/jboss/logmanager/PropertyConfigurator.java:[78,22] load(java.io.InputStream) in java.util.Properties cannot be applied to (java.io.InputStreamReader) /home/alr/business/jboss/wc/common/jboss-logmanager/trunk/src/main/java/org/jboss/logmanager/PropertyConfigurator.java:[78,22] load(java.io.InputStream) in java.util.Properties cannot be applied to (java.io.InputStreamReader) Enforce the environment. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBLOGGING-42) Include version information in stack traces

by Randall Hauch (JIRA)

Include version information in stack traces ------------------------------------------- Key: JBLOGGING-42 URL: https://jira.jboss.org/jira/browse/JBLOGGING-42 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Randall Hauch Assignee: David Lloyd Priority: Minor Including JAR and version information for each class in a stack trace provides a lot of useful information. For example (taken from the LogBack documentation): 14:28:48.835 [btpool0-7] INFO c.q.l.demo.prime.PrimeAction - 99 is not a valid value java.lang.Exception: 99 is invalid at ch.qos.logback.demo.prime.PrimeAction.execute(PrimeAction.java:28) [classes/:na] at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) [struts-1.2.9.jar:1.2.9] at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) [struts-1.2.9.jar:1.2.9] at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) [struts-1.2.9.jar:1.2.9] at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) [servlet-api-2.5-6.1.12.jar:6.1.12] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) [jetty-6.1.12.jar:6.1.12] at ch.qos.logback.demo.UserServletFilter.doFilter(UserServletFilter.java:44) [classes/:na] at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115) [jetty-6.1.12.jar:6.1.12] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361) [jetty-6.1.12.jar:6.1.12] at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417) [jetty-6.1.12.jar:6.1.12] at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) [jetty-6.1.12.jar:6.1.12] -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6292) Documentation should include transitioning from AS 4.2 to AS 5.0

by Bruce Link (JIRA)

Documentation should include transitioning from AS 4.2 to AS 5.0 ---------------------------------------------------------------- Key: JBAS-6292 URL: https://jira.jboss.org/jira/browse/JBAS-6292 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Affects Versions: JBossAS-5.0.0.GA Environment: Not applicable Reporter: Bruce Link Assignee: Samson Kittoli The installation and getting started guide should have a chapter on transitioning applications from JBoss AS 4.2 to JBoss AS 5.0. Examples discussed might be changes in build class path and configuration documents. For example, when using EJB3, the persistence.xml seems to need to specify a JBoss schema. The release notes is vague in this area. -- 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, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-7750) Update JBoss LogManager to 1.2.0

by David Lloyd (JIRA)

Update JBoss LogManager to 1.2.0 -------------------------------- Key: JBAS-7750 URL: https://jira.jboss.org/jira/browse/JBAS-7750 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Logging Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-6.0.0.M3 Some performance and memory usage improvements, plus a few new & improved features. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7830) Remove the "jboss.jmx:type=adaptor, name=Invoker, protocol=http, service=proxyFactory" object from jmx-invoker-service.xml

by David Lloyd (JIRA)

Remove the "jboss.jmx:type=adaptor,name=Invoker,protocol=http,service=proxyFactory" object from jmx-invoker-service.xml ----------------------------------------------------------------------------------------------------------------------- Key: JBAS-7830 URL: https://jira.jboss.org/jira/browse/JBAS-7830 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX Reporter: David Lloyd Fix For: JBossAS-6.0.0.M3 ...in server/src/etc/conf/web/jmx-invoker-service.xml to be exact -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-594) Reorganize svn authz file for new repository

by Paul Gier (JIRA)

Reorganize svn authz file for new repository -------------------------------------------- Key: JBBUILD-594 URL: https://jira.jboss.org/jira/browse/JBBUILD-594 Project: JBoss Build System Issue Type: Task Components: Artifact Repositories Reporter: Paul Gier Assignee: Paul Gier Fix For: Maven Repository 2.0 The svn access will need to be changed when the repository is moved over to nexus. The current repository authz file should be changed to use a sub directory in the URL which contains the list of users who have access to Nexus. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2065) Track dependency upgrades for ejb3 bom-as6 0.1.1

by jaikiran pai (JIRA)

Track dependency upgrades for ejb3 bom-as6 0.1.1 ------------------------------------------------- Key: EJBTHREE-2065 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2065 Project: EJB 3.0 Issue Type: Task Components: bom Reporter: jaikiran pai Assignee: jaikiran pai JIRA to keep track of upgrade to dependencies in the next releasable 0.1.1 version of bom-as6 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2010) Create a container spi and a singleton container impl

by jaikiran pai (JIRA)

Create a container spi and a singleton container impl ----------------------------------------------------- Key: EJBTHREE-2010 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2010 Project: EJB 3.0 Issue Type: Task Reporter: jaikiran pai Assignee: jaikiran pai A marker task to create a container spi and a (PoC) singleton container impl. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2061) ResourceHandler creates an incorrect injector when a bean has a interceptor with injection-target

by jaikiran pai (JIRA)

ResourceHandler creates an incorrect injector when a bean has a interceptor with injection-target ------------------------------------------------------------------------------------------------- Key: EJBTHREE-2061 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2061 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: EJB3_1 1.0.5, Plugin 1.0.19, 1.1.22 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: as-int 1.1.23, EJB3_1 1.0.6 Consider the following bean with an interceptor: @Stateless @Interceptors(SimpleInterceptor.class) @Remote(InjectionTester.class) public class SimpleStatelessBean implements InjectionTester { ... and the corresponding interceptor class: public class SimpleInterceptor { private EJBContext ejbContextInjectedThroughEjbJarXml; ... } and the ejb-jar.xml which configures injection-target for the interceptor: <?xml version="1.0" encoding="UTF-8"?> <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0"> <interceptors> <interceptor> <interceptor-class>org.jboss.ejb3.test.interceptor.SimpleInterceptor</interceptor-class> <resource-env-ref> <resource-env-ref-name>someOtherENCName</resource-env-ref-name> <resource-env-ref-type>javax.ejb.EJBContext</resource-env-ref-type> <injection-target> <injection-target-class>org.jboss.ejb3.test.interceptor.SimpleInterceptor</injection-target-class> <injection-target-name>ejbContextInjectedThroughEjbJarXml</injection-target-name> </injection-target> </resource-env-ref> </interceptor> </interceptors> </ejb-jar> This results in the following exception: 16:25:56,659 ERROR [FieldBeanProperty] failed to set value org.jboss.ejb3.stateless.StatelessSessionContextImpl@61a781 on field private javax.ejb.EJBContext org.jboss.ejb3.test.interceptor.SimpleInterceptor.ejbContextInjectedThroughEjbJarXml java.lang.IllegalArgumentException: Can not set javax.ejb.EJBContext field org.jboss.ejb3.test.interceptor.SimpleInterceptor.ejbContextInjectedThroughEjbJarXml to org.jboss.ejb3.test.interceptor.SimpleStatelessBean at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146) at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:150) at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:37) at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:57) at java.lang.reflect.Field.set(Field.java:657) at org.jboss.injection.lang.reflect.FieldBeanProperty.set(FieldBeanProperty.java:74) at org.jboss.injection.EJBContextPropertyInjector.inject(EJBContextPropertyInjector.java:50) at org.jboss.injection.EJBContextPropertyInjector.inject(EJBContextPropertyInjector.java:45) at org.jboss.ejb3.injection.InjectionInvocation.invokeTarget(InjectionInvocation.java:89) at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:83) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:74) at org.jboss.ejb3.EJBContainer.injectBeanContext(EJBContainer.java:1138) at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:83) at org.jboss.ejb3.InfinitePool.get(InfinitePool.java:56) at org.jboss.ejb3.InfinitePool.get(InfinitePool.java:51) at org.jboss.ejb3.pool.ThreadlocalPool.create(ThreadlocalPool.java:52) at org.jboss.ejb3.pool.ThreadlocalPool.get(ThreadlocalPool.java:92) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:438) at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:53) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:897) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:768) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:721) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) The ResourceHandler ends up creating an injector for the bean instance (instead of the interceptor): private static void loadXmlResourceEnvRefs(InjectionContainer container, Collection<ResourceEnvironmentReferenceMetaData> refs) { for (ResourceEnvironmentReferenceMetaData envRef : refs) { .... try { if(resTypeName != null) { ... if (envRef.getInjectionTargets() != null) { InjectionUtil.createInjectors(container.getInjectors(), container.getClassloader(), factory, envRef.getInjectionTargets()); continue; } (Notice the use of InjectionUtil.createInjectors which creates an injector for the bean instance (i.e. adds the injector to container.injectors()). The ResourceHandler should instead use InjectionUtil.injectionTarget(encName, envRef, container, container.getEncInjections()); -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2038) NPE while looking up java:comp/EJBContext in @PostConstruct method

by jaikiran pai (JIRA)

NPE while looking up java:comp/EJBContext in @PostConstruct method ------------------------------------------------------------------ Key: EJBTHREE-2038 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2038 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: EJB3_1 1.0.5, Plugin 1.0.19, 1.1.22 Reporter: jaikiran pai Assignee: jaikiran pai When java:comp/EJBContext is looked up in a method marked @PostConstruct of a bean, a NullPointerException is thrown from EJBContextFactory: Caused by: java.lang.NullPointerException at org.jboss.ejb3.EJBContextFactory.getObjectInstance(EJBContextFactory.java:57) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1483) at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1500) ... 70 more Please see the referenced forum thread for complete details. I was able to reproduce this issue with a SFSB too, so it's not specific to MDBs. -- 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, 3 months

2
2
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 March 2010