March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4219) Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs.

by Remy Maucherat (JIRA)

[ https://issues.jboss.org/browse/AS7-4219?page=com.atlassian.jira.plugin.s... ] Remy Maucherat resolved AS7-4219. --------------------------------- Resolution: Duplicate Issue AS7-2854 > Invalid descriptor doesn't rejected - requirement of <servlet-name> uniqueness by specs. > ---------------------------------------------------------------------------------------- > > Key: AS7-4219 > URL: https://issues.jboss.org/browse/AS7-4219 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.2.Final > Reporter: Pavel Janousek > Assignee: Remy Maucherat > > Invalid web.xml deployment descriptor like this: > {code:xml} > <?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" metadata-complete="false"> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > <servlet> > <servlet-name>ConflictServlet</servlet-name> > <servlet-class>org.jboss.as.test.integration.web.servlet.deployment.DummyServlet</servlet-class> > </servlet> > </web-app> > {code} > isn't rejected during deploying a such WAR application. > Uniqueness of <servlet-name> is requirement of Servlet deployment descriptor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-2166) Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea

by Ondrej Zizka (Created) (JIRA)

Alternative JDKs for building and running - OpenJDK 6, 7, Sun JDK 7, IcedTea ---------------------------------------------------------------------------- Key: AS7-2166 URL: https://issues.jboss.org/browse/AS7-2166 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondrej Zizka James Perkins: {quote} At one point there was a JIRA for OpenJDK 6, in fact I think a couple. The issue with OpenJDK 6 is in the build we use some JavaScript and OpenJDK 6 doesn't come with a JavaScript engine. I tried a couple things to get Rhino working with it as that's what the Sun JDK uses, but I think it needs to implement an SPI to get it to work. I didn't look into it much beyond that. JDK 7 is a different issue. It's a bug in the annotation processing API which the JBoss Logging Tooling uses. I just refreshed my OpenJDK 7 update source and it looks like the bug is fixed in there. It's fixed in IcedTea as well. There could be the JavaScript issue here as well I can't actually remember, but I thought I had some successful builds with custom JDK's I compiled. I did just try with IcedTea 7 and got some other errors. I'm building the latest upstream of OpenJDK 7 now and we'll see if it works. I'll let you know either way. Let me know if you have any more questions on this. I did dig into a while ago a little. {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
8
0 / 0

[JBoss JIRA] Created: (JBAS-9121) CLONE - Cannot build JBoss AS 7 using OpenJDK

by Shelly McGowan (JIRA)

CLONE - Cannot build JBoss AS 7 using OpenJDK --------------------------------------------- Key: JBAS-9121 URL: https://issues.jboss.org/browse/JBAS-9121 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: 7.0.0.Beta1 Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 7.0.0.Beta2 Compilation fails with: ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.1:compile (default-compile) on project jboss-as-arquillian-common: Compilation failure [ERROR] /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-7.0.x-testSuite-openjdk/arquillian/common/src/main/java/org/jboss/as/arquillian/container/JBossASDeploymentPackager.java:[59,16] inconvertible types [ERROR] found : org.jboss.shrinkwrap.api.Archive<capture#470 of ?> [ERROR] required: org.jboss.shrinkwrap.api.spec.WebArchive I've confirmed this is the latest version of OpenJDK: java-1.6.0-openjdk-1.6.0.0-1.20.b17.el5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
10
0 / 0

[JBoss JIRA] (AS7-2999) Integrate Remoting / SASL based authentication with EJB3

by Darran Lofthouse (Created) (JIRA)

Integrate Remoting / SASL based authentication with EJB3 -------------------------------------------------------- Key: AS7-2999 URL: https://issues.jboss.org/browse/AS7-2999 Project: Application Server 7 Issue Type: Bug Components: EJB, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker We need two approaches: - 1 - Support for the PLAIN SASL mechanism to pass the username and password straight to JAAS. 2 - Full SASL support with the JAAS security domain trusting the SASL Principal -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
12
0 / 0

[JBoss JIRA] (AS7-4300) Log more helpful message when duplicate jars prevent injection

by Randahl Fink Isaksen (JIRA)

Randahl Fink Isaksen created AS7-4300: ----------------------------------------- Summary: Log more helpful message when duplicate jars prevent injection Key: AS7-4300 URL: https://issues.jboss.org/browse/AS7-4300 Project: Application Server 7 Issue Type: Enhancement Reporter: Randahl Fink Isaksen If you package your business interfaces with both your ejb.jar and your web.war, EJB injection into the JSF backing beans of the web.war does not work. The reason is class loading issues - the bean implementing the business interface packaged in the ejb.jar is not assignment compatible with the other business interface found in the web.war. Removing the business interface classes from both the ejb.jar and web.war and packaging these in an EAR containing just 1 set of business interfaces will fix this problem. However, I just spend 24 hours trying to figure this out because the exception I got from JBoss AS 7 was not very helpful (as can be seen below). If multiple instances of the same jar lead to assignment incompatibilities that prevent EJB injection, I request that a much more developer friendly message is logged, such as the following: "It was not possible to inject EJB SurveillanceFunctionalityBean into AlarmEventView because the EJB SurveillanceFunctionalityBean implements a interface SurveillanceFunctionality loaded from another jar than the jar containing the interface used in AlarmEventView. As a result, the EJB instance is not assignment compatible with the field found in AlarmEventView. This can be solved by placing the interface SurveillanceFunctionality in its own jar inside an EAR and ensuring that no modules of the EAR contain duplicates the this particular jar." The original, less helpful exception 18:17:24,880 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http--10.0.0.110-8080-2) Error Rendering View[/iphone/alarms.xhtml]: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:95) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.deployment.component.WebComponentInstantiator$2.<init>(WebComponentInstantiator.java:96) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.deployment.component.WebComponentInstantiator.initializeInstance(WebComponentInstantiator.java:94) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.deployment.WebInjectionContainer.newInstance(WebInjectionContainer.java:86) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.deployment.jsf.JsfInjectionProvider.invokePostConstruct(JsfInjectionProvider.java:69) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at com.sun.faces.mgbean.BeanBuilder.invokePostConstruct(BeanBuilder.java:223) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.mgbean.BeanBuilder.build(BeanBuilder.java:105) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.mgbean.BeanManager.createAndPush(BeanManager.java:409) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.mgbean.BeanManager.create(BeanManager.java:269) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.el.ManagedBeanELResolver.resolveBean(ManagedBeanELResolver.java:244) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.el.ManagedBeanELResolver.getValue(ManagedBeanELResolver.java:116) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203) [jsf-impl-2.1.7-jbossorg-2.jar:] at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:72) [jbossweb-7.0.13.Final.jar:] at org.apache.el.parser.AstValue.getTarget(AstValue.java:94) [jbossweb-7.0.13.Final.jar:] at org.apache.el.parser.AstValue.getType(AstValue.java:82) [jbossweb-7.0.13.Final.jar:] at org.apache.el.ValueExpressionImpl.getType(ValueExpressionImpl.java:176) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.el.WeldValueExpression.getType(WeldValueExpression.java:93) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at com.sun.faces.facelets.el.TagValueExpression.getType(TagValueExpression.java:98) [jsf-impl-2.1.7-jbossorg-2.jar:] at org.primefaces.component.datatable.DataTable.isLazy(DataTable.java:922) [primefaces-3.1.1.jar:] at org.primefaces.component.datatable.DataTableRenderer.encodeMarkup(DataTableRenderer.java:177) [primefaces-3.1.1.jar:] at org.primefaces.component.datatable.DataTableRenderer.encodeEnd(DataTableRenderer.java:103) [primefaces-3.1.1.jar:] at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:402) [jsf-impl-2.1.7-jbossorg-2.jar:] at org.apache.myfaces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:285) [myfaces-impl-2.1.6.jar:2.1.6] at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.7-jbossorg-2.jar:] at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.7-jbossorg-2.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29] Caused by: java.lang.IllegalArgumentException: Can not set com.wefend.services.surveillance.SurveillanceFunctionality field com.wefend.web.events.AlarmEventView.surveillanceFunctionality to com.wefend.services.surveillance.SurveillanceFunctionality$$$view19 at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146) [classes.jar:1.6.0_29] at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:150) [classes.jar:1.6.0_29] at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63) [classes.jar:1.6.0_29] at java.lang.reflect.Field.set(Field.java:657) [classes.jar:1.6.0_29] at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:111) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:106) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final] ... 50 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4299) CLONE - Enable JAAS support for the SASL Realms

by Jan Lanik (JIRA)

Jan Lanik created AS7-4299: ------------------------------ Summary: CLONE - Enable JAAS support for the SASL Realms Key: AS7-4299 URL: https://issues.jboss.org/browse/AS7-4299 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Security Reporter: Jan Lanik Assignee: Darran Lofthouse Fix For: 7.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4298) CLONE - Enable use of PLAIN SASL mechanism with JAAS security domains for the Remote EJB calls.

by Jan Lanik (JIRA)

Jan Lanik created AS7-4298: ------------------------------ Summary: CLONE - Enable use of PLAIN SASL mechanism with JAAS security domains for the Remote EJB calls. Key: AS7-4298 URL: https://issues.jboss.org/browse/AS7-4298 Project: Application Server 7 Issue Type: Task Components: EJB, Remoting, Security Reporter: Jan Lanik Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.0.Final Support for the PLAIN SASL mechanism to pass the username and password straight to JAAS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4259) updating a system-property always requires a reload

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-4259: ---------------------------------------- Summary: updating a system-property always requires a reload Key: AS7-4259 URL: https://issues.jboss.org/browse/AS7-4259 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: 7.1.2.Final the /system-property=test:write-attribute operation always requires are restart for standalone. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1625) Cookies version 0 value rejected by org.apache.tomcat.util.http.Cookies

by Ondrej Zizka (JIRA)

Cookies version 0 value rejected by org.apache.tomcat.util.http.Cookies ----------------------------------------------------------------------- Key: AS7-1625 URL: https://issues.jboss.org/browse/AS7-1625 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.1.Final Environment: standalone Reporter: Ondrej Zizka Assignee: Remy Maucherat I have a cookie in browser which was set for redhat.com, so my AS 7 on ozizka.brq.redhat.com is receiving it to. Now that "version 0" cookie contains characters illegal acc. to RFC-2109 and RFC-2068: {code} Cookie: s_vi=[CS]v1|261............[CE]; ... {code} AS 7 logs: {code} 22:18:13,365 INFO [org.apache.tomcat.util.http.Cookies] (http--0.0.0.0-8080-2) Cookies: Invalid cookie. Value not a token or quoted value {code} I haven't checked whether only the single value is discarded or all cookies. Possibly related: JBPAPP-5813 Some related links: Discussion http://old.nabble.com/DO-NOT-REPLY--Bug-49525--New%3A-IE8%3A-Unabled-to-s... and bug https://issues.apache.org/bugzilla/show_bug.cgi?id=49525 about Tomcat 7's bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
13
0 / 0

[JBoss JIRA] (AS7-4297) jdbc-driver:add operation is not considering module-slot parameter

by Stefano Maestri (JIRA)

Stefano Maestri created AS7-4297: ------------------------------------ Summary: jdbc-driver:add operation is not considering module-slot parameter Key: AS7-4297 URL: https://issues.jboss.org/browse/AS7-4297 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.1.Final Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.1.2.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 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 March 2012