February 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8891) Parse issue with namespaces in web.xml

by Alessio Soldano (JIRA)

Parse issue with namespaces in web.xml -------------------------------------- Key: JBAS-8891 URL: https://issues.jboss.org/browse/JBAS-8891 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Alessio Soldano Assignee: Remy Maucherat Fix For: 7.0.0.Alpha2 When parsing the following web.xml (that used to work on AS 6) <?xml version="1.0" encoding="UTF-8"?> <web-app version="3.0" 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/web-app_3_0.xsd"> <display-name>ServletTestClient</display-name> <servlet> <servlet-name>ServletTestClient</servlet-name> <servlet-class>org.jboss.test.ws.jaxws.jbws3140.ServletTestClient</servlet-class> </servlet> <servlet-mapping> <servlet-name>ServletTestClient</servlet-name> <url-pattern>/ServletTest</url-pattern> </servlet-mapping> <session-config> <session-timeout>60</session-timeout> </session-config> <service-ref> <service-ref-name>service/mtomTest</service-ref-name> <service-interface>org.jboss.test.ws.jaxws.jbws3140.EndpointService</service-interface> <service-ref-type>org.jboss.test.ws.jaxws.jbws3140.MTOMTest</service-ref-type> <wsdl-file>WEB-INF/wsdl/TestEndpoint.wsdl</wsdl-file> <service-qname xmlns:servicens="http://TestEndpoint.org">servicens:TestEndpointService</service-qname> <port-component-ref> <service-endpoint-interface>org.jboss.test.ws.jaxws.jbws3140.MTOMTest</service-endpoint-interface> <enable-mtom>true</enable-mtom> <mtom-threshold>750</mtom-threshold> <addressing> <enabled>true</enabled> <responses>ANONYMOUS</responses> </addressing> </port-component-ref> </service-ref> </web-app> I get a parsing exception: java.lang.IllegalArgumentException: Invalid QName: servicens:TestEndpointService at org.jboss.metadata.parser.util.MetaDataElementParser.parseQName(MetaDataElementParser.java:320) at org.jboss.metadata.parser.ee.ServiceReferenceMetaDataParser.parse(ServiceReferenceMetaDataParser.java:100) at org.jboss.metadata.parser.ee.EnvironmentRefsGroupMetaDataParser.parse(EnvironmentRefsGroupMetaDataParser.java:81) at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:150) at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:66) ... 5 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8897) Web Filter's init() method executed before EJBs are deployed

by Jozef Hartinger (JIRA)

Web Filter's init() method executed before EJBs are deployed ------------------------------------------------------------ Key: JBAS-8897 URL: https://issues.jboss.org/browse/JBAS-8897 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: 6.0.0.Final Reporter: Jozef Hartinger Assignee: Carlo de Wolf Priority: Blocker Having a singleton (or stateless session) bean @Singleton @Startup @ApplicationScoped public class Echo { public boolean ping() { return true; } } and a web filter @WebFilter(urlPatterns = "/*") public class Filter implements javax.servlet.Filter { private static final Logger log = Logger.getLogger(Filter.class); @Inject private Echo echo; @Override public void init(FilterConfig filterConfig) throws ServletException { log.info("Init starting"); echo.ping(); log.info("Init done"); } @Override public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException { chain.doFilter(request, response); } @Override public void destroy() { } } Deployment of the application fails with the following exception: 10:56:57,152 INFO [org.jboss.seam.rest.test.compat.ejb.deployment.Filter] Init starting 10:56:57,153 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/test]] Exception starting filter org.jboss.seam.rest.test.compat.ejb.deployment.Filter: org.jboss.weld.exceptions.CreationException: WELD-000079 Could not find the EJB in JNDI: class org.jboss.seam.rest.test.compat.ejb.deployment.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$home$jharting$jboss$RESTEasy-int-clean$jboss-6$0$0$Final$server$default$deploy$test$war"-SessionBean-Echo_$$_WeldProxy at org.jboss.weld.bean.SessionBean.create(SessionBean.java:348) [:6.0.0.Final] at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:121) [:6.0.0.Final] at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:99) [:6.0.0.Final] at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:87) [:6.0.0.Final] at org.jboss.seam.rest.test.compat.ejb.deployment.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$home$jharting$jboss$RESTEasy-int-clean$jboss-6$0$0$Final$server$default$deploy$test$war"-SessionBean-Echo_$$_WeldClientProxy.ping(org$jboss$weld$bean-jboss$classloader:id="vfs:$$$home$jharting$jboss$RESTEasy-int-clean$jboss-6$0$0$Final$server$default$deploy$test$war"-SessionBean-Echo_$$_WeldClientProxy.java) at org.jboss.seam.rest.test.compat.ejb.deployment.Filter.init(Filter.java:29) [:] at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447) [:6.0.0.Final] at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3246) [:6.0.0.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3843) [:6.0.0.Final] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final] at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final] at sun.reflect.GeneratedMethodAccessor405.invoke(Unknown Source) [:1.6.0_23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_23] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_23] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA] at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA] at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:53) [:2.2.0.GA] at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:41) [:2.2.0.GA] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA] at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2] at org.jboss.profileservice.plugins.deploy.actions.DeploymentStartAction.doPrepare(DeploymentStartAction.java:98) [:0.2.2] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:101) [:0.2.2] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2] at org.jboss.profileservice.plugins.deploy.AbstractDeployHandler.startDeployments(AbstractDeployHandler.java:168) [:0.2.2] at org.jboss.profileservice.management.upload.remoting.DeployHandlerDelegate.startDeployments(DeployHandlerDelegate.java:74) [:6.0.0.Final] at org.jboss.profileservice.management.upload.remoting.DeployHandler.invoke(DeployHandler.java:156) [:6.0.0.Final] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:898) [:6.0.0.Final] at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791) [:6.0.0.Final] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744) [:6.0.0.Final] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548) [:6.0.0.Final] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) [:6.0.0.Final] Caused by: java.lang.RuntimeException: Error retreiving EJB from JNDI Echo (Singleton); BeanClass: class org.jboss.seam.rest.test.compat.ejb.deployment.Echo; Local Business Interfaces: [Business interface: class org.jboss.seam.rest.test.compat.ejb.deployment.Echo] at org.jboss.weld.integration.ejb.JBossEjbServices.resolveEjb(JBossEjbServices.java:69) [:6.0.0.Final] at org.jboss.weld.bean.SessionBean.createReference(SessionBean.java:476) [:6.0.0.Final] at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.<init>(EnterpriseBeanProxyMethodHandler.java:75) [:6.0.0.Final] at org.jboss.weld.bean.SessionBean.create(SessionBean.java:331) [:6.0.0.Final] ... 56 more Caused by: javax.naming.NameNotFoundException: no-interface not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) [:5.0.5.Final] at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) [:5.0.5.Final] at org.jnp.server.NamingServer.getObject(NamingServer.java:785) [:5.0.5.Final] at org.jnp.server.NamingServer.lookup(NamingServer.java:443) [:5.0.5.Final] at org.jnp.server.NamingServer.lookup(NamingServer.java:399) [:5.0.5.Final] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:728) [:5.0.5.Final] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) [:5.0.5.Final] at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_23] at org.jboss.weld.integration.ejb.JBossSessionObjectReference.<init>(JBossSessionObjectReference.java:44) [:6.0.0.Final] at org.jboss.weld.integration.ejb.JBossEjbServices.resolveEjb(JBossEjbServices.java:65) [:6.0.0.Final] ... 59 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-8871) AS7 undeployment doesn't work properly for identically named deployments (with different content)

by Richard Opalka (JIRA)

AS7 undeployment doesn't work properly for identically named deployments (with different content) ------------------------------------------------------------------------------------------------- Key: JBAS-8871 URL: https://issues.jboss.org/browse/JBAS-8871 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.0.0.Alpha2 Currently DeploymentUndeployHandler.undeploy() calls controller.setMode(ServiceController.Mode.NEVER) to "undeploy DU". This causes the following issue: There's TestA that deploys & undeploys example.war There's TestB that deploys & undeploys example.war too (but with different content). The problem is TestB will see TestA example.war content :( This is because there's still controller (for example.war DU) registered with MSC registry, and it's started again during the deploy phase. The code that will start it again is --- final ServiceController<?> controller = serviceRegistry.getService(deploymentUnitServiceName); if(controller != null) { controller.setMode(ServiceController.Mode.ACTIVE); } else { --- located in DeploymentHandlerUtil.deploy(). The solution to this problem is to call controller.setMode(ServiceController.Mode.REMOVE) to undeploy DU properly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Moved: (JBAS-8904) JPA needs a temporary classloader that can load the same classes as the Module.getClassLoader() returns

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBAS-8904?page=com.atlassian.jira.plugin.... ] David Lloyd moved MSC-66 to JBAS-8904: -------------------------------------- Project: JBoss Application Server (was: Modular Service Container) Key: JBAS-8904 (was: MSC-66) Security: Public > JPA needs a temporary classloader that can load the same classes as the Module.getClassLoader() returns > ------------------------------------------------------------------------------------------------------- > > Key: JBAS-8904 > URL: https://issues.jboss.org/browse/JBAS-8904 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Scott Marlow > Assignee: Scott Marlow > Attachments: getNewTempClassLoader.patch > > > JPA PersistenceUnitInfo has a getNewTempClassLoader method that I need to implement. This would be similar to the classloader returned from Module.getClassLoader(). Also see http://download.oracle.com/javaee/6/api/javax/persistence/spi/Persistence... > This is a JPA spec requirement but not needed by the Hibernate Persistence Provider (currently). So, we could put this off for a bit. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8900) Arquillian embedded container return after partial server startup

by Thomas Diesler (JIRA)

Arquillian embedded container return after partial server startup ----------------------------------------------------------------- Key: JBAS-8900 URL: https://issues.jboss.org/browse/JBAS-8900 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler We see ARQ tests being deployed to a partially started server. This shows particularly on EC2 Hudson -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (LOGTOOL-10) MessageFormat.format is instance method

by Jonathan Halliday (JIRA)

MessageFormat.format is instance method --------------------------------------- Key: LOGTOOL-10 URL: https://issues.jboss.org/browse/LOGTOOL-10 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta3 Reporter: Jonathan Halliday Assignee: David Lloyd for methods of the form @Message(id = 1, value = "foo", format = MESSAGE_FORMAT) public String foobar(); then generated code of the form String result = MessageFormat.format(((projectCode +"-1:")+ foo$str())); won't compile as format is an instance method. MessageLoggerImplementor.createBundleMethod needs patch to differentiate MESSAGE_FORMAT and PRINTF cases? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Resolved: (JBAS-8898) Provide AS7 embedded container

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBAS-8898?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved JBAS-8898. ---------------------------------- Resolution: Done Done > Provide AS7 embedded container > ------------------------------ > > Key: JBAS-8898 > URL: https://issues.jboss.org/browse/JBAS-8898 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.0.0.Alpha2 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8899) Provide AS7 remote container

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBAS-8899?page=com.atlassian.jira.plugin.... ] Thomas Diesler moved ARQ-334 to JBAS-8899: ------------------------------------------ Project: JBoss Application Server (was: Arquillian) Key: JBAS-8899 (was: ARQ-334) Issue Type: Feature Request (was: Task) Component/s: (was: JBoss Containers) Security: Public Fix Version/s: 7.0.0.Alpha2 (was: 1.0.0.Beta1) > Provide AS7 remote container > ---------------------------- > > Key: JBAS-8899 > URL: https://issues.jboss.org/browse/JBAS-8899 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.0.0.Alpha2 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-8899) Provide AS7 remote container

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBAS-8899?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved JBAS-8899. ---------------------------------- Resolution: Done Done > Provide AS7 remote container > ---------------------------- > > Key: JBAS-8899 > URL: https://issues.jboss.org/browse/JBAS-8899 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 7.0.0.Alpha2 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8653) Provide initial Arquillian integration

by Thomas Diesler (JIRA)

Provide initial Arquillian integration -------------------------------------- Key: JBAS-8653 URL: https://jira.jboss.org/browse/JBAS-8653 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.Alpha2 Provide an Arquillian subsystem with associated smoke tests -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

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