January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-135) Settle on *Util or *Utils suffix for static utility classes

by David Lloyd (JIRA)

David Lloyd created ELY-135: ------------------------------- Summary: Settle on *Util or *Utils suffix for static utility classes Key: ELY-135 URL: https://issues.jboss.org/browse/ELY-135 Project: WildFly Elytron Issue Type: Task Reporter: David Lloyd Fix For: 1.0.0.Alpha1 We just need to pick one or the other, then fix them to be uniform. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1243) IronJacamar 1.2.2.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1243?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1243. ------------------------------------ Resolution: Done > IronJacamar 1.2.2.Final > ----------------------- > > Key: JBJCA-1243 > URL: https://issues.jboss.org/browse/JBJCA-1243 > Project: IronJacamar > Issue Type: Release > Components: Build > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.2.2.Final > > > Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-134) Complete API JavaDoc

by David Lloyd (JIRA)

David Lloyd created ELY-134: ------------------------------- Summary: Complete API JavaDoc Key: ELY-134 URL: https://issues.jboss.org/browse/ELY-134 Project: WildFly Elytron Issue Type: Task Reporter: David Lloyd Priority: Blocker Fix For: 1.0.0.Final All API components and members must be JavaDoc'd. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-133) Complete i18n of exceptions and log messages

by David Lloyd (JIRA)

David Lloyd created ELY-133: ------------------------------- Summary: Complete i18n of exceptions and log messages Key: ELY-133 URL: https://issues.jboss.org/browse/ELY-133 Project: WildFly Elytron Issue Type: Task Reporter: David Lloyd Priority: Blocker Fix For: 1.0.0.Final All exceptions and relevant log messages must be i18nized. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1243) IronJacamar 1.2.2.Final

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1243: -------------------------------------- Summary: IronJacamar 1.2.2.Final Key: JBJCA-1243 URL: https://issues.jboss.org/browse/JBJCA-1243 Project: IronJacamar Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.2.2.Final Release notes: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310691&versi... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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: ----------------------------------------------- Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 1075353|https://bugzilla.redhat.com/show_bug.cgi?id=1075353] from ON_QA to VERIFIED > 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.11#6341)

11 years, 3 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: ---------------------------------------------- Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 1075353|https://bugzilla.redhat.com/show_bug.cgi?id=1075353] from ON_QA to VERIFIED > 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.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4245) redirect-socket="https" not explicit in default configuration

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4245?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-4245: --------------------------------- Assignee: Tomaz Cerar (was: Stuart Douglas) > redirect-socket="https" not explicit in default configuration > ------------------------------------------------------------- > > Key: WFLY-4245 > URL: https://issues.jboss.org/browse/WFLY-4245 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Environment: Linux 64bit > Reporter: Giuseppe Mazzotta > Assignee: Tomaz Cerar > Priority: Minor > > Although this problem has been reported as fixed in WFLY-2836, I am still able to reproduce a failure by removing the https socket-binding from default standalone.xml configuration file: > {noformat} > --- standalone.xml.orig 2015-01-13 11:33:57.956000250 +0100 > +++ standalone.xml 2015-01-13 11:34:04.456000250 +0100 > @@ -375,11 +375,10 @@ > <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/> > <socket-binding name="ajp" port="${jboss.ajp.port:8009}"/> > <socket-binding name="http" port="${jboss.http.port:8080}"/> > - <socket-binding name="https" port="${jboss.https.port:8443}"/> > <socket-binding name="txn-recovery-environment" port="4712"/> > <socket-binding name="txn-status-manager" port="4713"/> > <outbound-socket-binding name="mail-smtp"> > <remote-destination host="localhost" port="25"/> > </outbound-socket-binding> > </socket-binding-group> > -</server> > \ No newline at end of file > +</server> > {noformat} > Failure in log is: > {noformat} > 11:10:23,601 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => { > "Services that were unable to start:" => ["jboss.ws.config"], > "Services that may be the cause:" => [ > "jboss.binding.https", > "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" > ] > }} > 11:10:23,602 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([ > ("subsystem" => "undertow"), > ("server" => "default-server"), > ("http-listener" => "default") > ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.default is missing [jboss.binding.https]"]} > 11:10:23,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([ > ("subsystem" => "ejb3"), > ("service" => "remote") > ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]} > 11:10:23,663 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.binding.https (missing) dependents: [service jboss.undertow.listener.default] > service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector] > 11:10:23,674 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 11:10:23,675 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 11:10:23,675 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.0.Final "Tweek" started (with errors) in 3468ms - Started 175 of 231 services (3 services failed or missing dependencies, 81 services are lazy, passive or on-demand) > {noformat} > Is this expected behavior? > *Edit:* due to configuration defaults, see below comments -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3502) Create configurable strategy for dealing with serialization incompatiblities

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-3502?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-3502: ------------------------------- Summary: Create configurable strategy for dealing with serialization incompatiblities (was: Create pluggable strategy for dealing with serialization incompatiblities) > Create configurable strategy for dealing with serialization incompatiblities > ---------------------------------------------------------------------------- > > Key: WFLY-3502 > URL: https://issues.jboss.org/browse/WFLY-3502 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > When a new release of a web application is deployed to an existing cluster, any changes to the object placed in the web session can cause serialization incompatibilities. To handle this cleanly, we typically recommend that users leverage isolated cluster and mod_cluster load balancing groups (or mod_jk domains) to transition users to the new version of an application. > For simple applications, this might be overkill. It might be acceptable/preferable to create a new session in the event of a serialization incompatibility, rather than failing the request. We should allow developers to configure this behavior per-application. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-650: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1175886|https://bugzilla.redhat.com/show_bug.cgi?id=1175886] from ON_QA to VERIFIED > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 January 2015