December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4159) (XA) Data Sources view shows only 5 entries

by Eugen Eisler (JIRA)

[ https://issues.jboss.org/browse/WFLY-4159?page=com.atlassian.jira.plugin.... ] Eugen Eisler updated WFLY-4159: ------------------------------- Attachment: xa data sources.png > (XA) Data Sources view shows only 5 entries > ------------------------------------------- > > Key: WFLY-4159 > URL: https://issues.jboss.org/browse/WFLY-4159 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.2.0.Final > Environment: - Windows 7 Pro x64 > - Chrome Web Browser > Reporter: Eugen Eisler > Assignee: Heiko Braun > Priority: Minor > Attachments: xa data sources.png > > > 20 xa datasources configured, but only 5 are displayed in Runtime / Subsystems / Datasources / XA Data sources. Same problem with non xa datasources. > Runtime / Subsystems / JNDI View shows all 20 datasources. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1239) codegenerator fails to create ra.xml for maven-rar-plugin

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1239?page=com.atlassian.jira.plugin... ] Jesper Pedersen commented on JBJCA-1239: ---------------------------------------- It seems that the maven-rar-plugin needs an option to ignore raXmlFile such that the WARN isn't displayed. We will merge the PR, as it is more correct. > codegenerator fails to create ra.xml for maven-rar-plugin > --------------------------------------------------------- > > Key: JBJCA-1239 > URL: https://issues.jboss.org/browse/JBJCA-1239 > Project: IronJacamar > Issue Type: Bug > Components: Code Generator > Affects Versions: 1.2.0.Final > Reporter: Steve Gorman > Assignee: Jeff Zhang > Labels: maven > Fix For: 1.2.1.Final > > > After generating a maven project the ra.xml file is not part of the generated code but is referenced in the pom.xml -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1239) codegenerator fails to create ra.xml for maven-rar-plugin

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1239?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1239. ------------------------------------ Resolution: Done > codegenerator fails to create ra.xml for maven-rar-plugin > --------------------------------------------------------- > > Key: JBJCA-1239 > URL: https://issues.jboss.org/browse/JBJCA-1239 > Project: IronJacamar > Issue Type: Bug > Components: Code Generator > Affects Versions: 1.2.0.Final > Reporter: Steve Gorman > Assignee: Jeff Zhang > Labels: maven > Fix For: 1.2.1.Final > > > After generating a maven project the ra.xml file is not part of the generated code but is referenced in the pom.xml -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4159) (XA) Data Sources view shows only 5 entries

by Eugen Eisler (JIRA)

Eugen Eisler created WFLY-4159: ---------------------------------- Summary: (XA) Data Sources view shows only 5 entries Key: WFLY-4159 URL: https://issues.jboss.org/browse/WFLY-4159 Project: WildFly Issue Type: Bug Components: Web Console Affects Versions: 8.2.0.Final Environment: - Windows 7 Pro x64 - Chrome Web Browser Reporter: Eugen Eisler Assignee: Heiko Braun Priority: Minor 20 xa datasources configured, but only 5 are displayed in Runtime / Subsystems / Datasources / XA Data sources. Same problem with non xa datasources. Runtime / Subsystems / JNDI View shows all 20 datasources. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-270) Upgrade to JBoss SASL 1.0.5.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-270?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-270: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1164781|https://bugzilla.redhat.com/show_bug.cgi?id=1164781] from MODIFIED to ON_QA > Upgrade to JBoss SASL 1.0.5.Final > --------------------------------- > > Key: WFCORE-270 > URL: https://issues.jboss.org/browse/WFCORE-270 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-795) jboss-ejb-iiop_1_0.xsd has both use="required" and default attributes on some elements

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-795?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-795: ---------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1028412|https://bugzilla.redhat.com/show_bug.cgi?id=1028412] from MODIFIED to ON_QA > jboss-ejb-iiop_1_0.xsd has both use="required" and default attributes on some elements > -------------------------------------------------------------------------------------- > > Key: WFLY-795 > URL: https://issues.jboss.org/browse/WFLY-795 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: James Livingston > Assignee: David Lloyd > Fix For: 8.0.0.CR1 > > > In jboss-ejb-iiop_1_0.xsd, the "integrity", "confidentiality", "establish-trust-in-client", and "establish-trust-in-target" attributes on the "iorTransportConfigType" complexType, and the "auth-method", "realm" and "required" attributes on the "iorASContextType" complexType have both use="required" and a default attribute. > This does not make sense because default values are only applicable to optional attributes. I'm not sure which is correct, but either the attributes should be optional or the default values removed. This problem causes the XSD to not validate. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-154) ClassCastException in JSPs where spring-web tags and jstl tags are used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBEE-154?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on JBEE-154: ---------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1075353|https://bugzilla.redhat.com/show_bug.cgi?id=1075353] from MODIFIED to ON_QA > ClassCastException in JSPs where spring-web tags and jstl tags are used > ----------------------------------------------------------------------- > > Key: JBEE-154 > URL: https://issues.jboss.org/browse/JBEE-154 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jsp-api > Reporter: James Livingston > Assignee: Tomaz Cerar > Fix For: jboss-jsp-api_2.2_spec-1.0.2.Final > > > WFLY-3100 incorporated a fix to the 2.3 version of the JSP APIs, and it would be good to have it in the 2.2 APIs as well. > There is currently no maintenance branch for the 2.2 APIs, so we would need to create one similar to what was done in JBEE-147. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3100) ClassCastException in JSPs where spring-web tags and jstl tags are used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3100?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3100: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1075353|https://bugzilla.redhat.com/show_bug.cgi?id=1075353] from MODIFIED to ON_QA > ClassCastException in JSPs where spring-web tags and jstl tags are used > ----------------------------------------------------------------------- > > Key: WFLY-3100 > URL: https://issues.jboss.org/browse/WFLY-3100 > Project: WildFly > Issue Type: Bug > Components: EE, Web (Undertow) > Affects Versions: 8.0.0.Final > Reporter: abhishek vijra > Assignee: Shelly McGowan > Labels: jsp, jstl > Fix For: 8.1.0.CR1, 8.1.0.Final > > Attachments: spring-fun.war > > > Following JSP with spring tags > <%@ page contentType="text/html;charset=UTF-8" language="java" %> > <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %> > <%@ taglib prefix="spring" uri="http://www.springframework.org/tags" %> > <html> > <head><title>Simple jsp page</title></head> > <body> > > <c:set var="hasError" value="${param.hasError}" /> > <c:set var="msg" value="${param.msg}" /> > > <c:if test="${param.hasError=='true'}"> > Message: <spring:message text="${param.msg}"/> > </c:if> > > </body> > </html> > breaks following error > ERROR [org.springframework.web.servlet.tags.MessageTag] (default task-1) org.apache.taglibs.standard.lang.jstl.ImplicitObjects cannot be cast to javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects: java.lang.ClassCastException: org.apache.taglibs.standard.lang.jstl.ImplicitObjects cannot be cast to javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects > at javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects.getImplicitObjects(ImplicitObjectELResolver.java:608) [jboss-jsp-api_2.3_spec-1.0.0.Final.jar:1.0.0.Final] > at javax.servlet.jsp.el.ImplicitObjectELResolver.getValue(ImplicitObjectELResolver.java:169) [jboss-jsp-api_2.3_spec-1.0.0.Final.jar:1.0.0.Final] > at org.apache.jasper.el.JasperELResolver.getValue(JasperELResolver.java:95) [jastow-1.0.0.Final.jar:1.0.0.Final] > at org.apache.jasper.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:32) [jastow-1.0.0.Final.jar:1.0.0.Final] > at org.apache.jasper.el.ELResolverImpl.getValue(ELResolverImpl.java:78) [jastow-1.0.0.Final.jar:1.0.0.Final] > at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:116) [javax.el-3.0.0.jar:3.0.0] > at com.sun.el.parser.AstValue.getBase(AstValue.java:151) [javax.el-3.0.0.jar:3.0.0] > at com.sun.el.parser.AstValue.getValue(AstValue.java:200) [javax.el-3.0.0.jar:3.0.0] > There are two jars (jboss-jsp-api_2.3_spec-1.0.0.Final.jar and jboss-jstl-api_1.2_spec-1.0.4.Final.jar) that are incompatible with each other due to a bug -- both are storing an object in the same place, but the objects are not compatible. > The result is that a jsp page cannot contain both JSTL and Spring tags, or it will get that error. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3519) process-id-uuid and related attribute should consider alternatives/required attributes in :write-attribute handler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3519?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3519: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1090406|https://bugzilla.redhat.com/show_bug.cgi?id=1090406] from POST to ASSIGNED > process-id-uuid and related attribute should consider alternatives/required attributes in :write-attribute handler > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-3519 > URL: https://issues.jboss.org/browse/WFLY-3519 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 9.0.0.Beta1 > > > The transaction subsystem causes the server fails to start (is halted) when just process-id-uuid is set to false without specifying the process-id-socket-binding. > When you run commands: > /subsystem=transactions:write-attribute(name=process-id-uuid,value=false) > :reload > Server fails with exception [1] > The transaction subsystem should block changes that causes the server would fail on reload. The user should get information that the process-id-socket-binding has to be set before reload could proceed, i.e., fail the reload operation. > [1] > 11:13:53,630 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10] > at org.jboss.as.server.ServerService.boot(ServerService.java:321) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:253) [jboss-as-controller-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[287,17] > Message: JBAS014723: Must include one of the following elements: SOCKET, UUID > at org.jboss.as.controller.parsing.ParseUtils.missingOneOf(ParseUtils.java:194) [jboss-as-controller-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10] > at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.parseProcessIdEnvironmentElement(TransactionSubsystem14Parser.java:390) > at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.parseCoreEnvironmentElement(TransactionSubsystem14Parser.java:340) > at org.jboss.as.txn.subsystem.TransactionSubsystem15Parser.readElement(TransactionSubsystem15Parser.java:59) > at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:110) > at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:53) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2] > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2] > at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1035) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10] > at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:469) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [jboss-as-server-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10] > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2] > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.4.0.Final-redhat-10.jar:7.4.0.Final-redhat-10] > ... 3 more > 11:13:53,635 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1470) Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1470?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1470: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 901231|https://bugzilla.redhat.com/show_bug.cgi?id=901231] from MODIFIED to ON_QA > Usage of finalize() needs extra guards due to a flaw in the language feature (mostly affects IBM) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-1470 > URL: https://issues.jboss.org/browse/WFLY-1470 > Project: WildFly > Issue Type: Task > Reporter: Carlo de Wolf > Assignee: Jason Greene > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014