[JBoss JIRA] (DROOLS-667) Profile why day.index is so much slower than day.getIndex()
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-667?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet commented on DROOLS-667:
-----------------------------------------
I think the difference is because of stateful or stateless. In TTP, it's used in a statefull context, with thousands of fireAllRules() calls on 1 KieBase. In the microbenchmark I saw earlier, it's used in just 1 fireAllRules().
> Profile why day.index is so much slower than day.getIndex()
> -----------------------------------------------------------
>
> Key: DROOLS-667
> URL: https://issues.jboss.org/browse/DROOLS-667
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 6.2.0.CR3
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
>
> day.index is 3 times slower than day.getIndex() (and it's gets more as the dataset grows)
> As discussed with Mario. Rough benchmark speeds here:
> https://gist.github.com/ge0ffrey/7662856f357dbec7f7ec
> Reproduce recipe
> - git clone optaplanner
> - Run TravelingTournamentApp, load dataset bra24, solve it for about 30 seconds.
> - Open travelingTournamentScoreRules.drl. Replace all occurrences of "day.getIndex()" with "day.index".
> - Run TravelingTournamentApp again, load dataset bra24, solve it for about 30 seconds again.
> - Compare the last log message of both runs: look for average calculate count per second (x). Higher is faster. For bra24, day.getIndex() is 3 times faster than day.index.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (WFLY-2509) Method invocation of a non serializable remote EJB
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-2509?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski closed WFLY-2509.
--------------------------------
> Method invocation of a non serializable remote EJB
> ---------------------------------------------------
>
> Key: WFLY-2509
> URL: https://issues.jboss.org/browse/WFLY-2509
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: omar al kababji
> Assignee: Tomasz Adamski
> Priority: Optional
>
> If you have a remote EJB that is not Serializable (i.e. does not implement the interface Serializable) you can lookup such class from a remote EJB client however when you execute a method you get an error as follows:
> java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling
> The enhancement is to give an error or warning message when the EJB is deployed notifying the developer that he is deploying a Remote EJB that is not implementing the Serializable interface.
> The same thing happens if you deploy an EJB marked with the annotation @Remote but with no @Stateless nor @Statefull annotations.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (WFLY-2509) Method invocation of a non serializable remote EJB
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-2509?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski resolved WFLY-2509.
----------------------------------
Resolution: Rejected
> Method invocation of a non serializable remote EJB
> ---------------------------------------------------
>
> Key: WFLY-2509
> URL: https://issues.jboss.org/browse/WFLY-2509
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: omar al kababji
> Assignee: Tomasz Adamski
> Priority: Optional
>
> If you have a remote EJB that is not Serializable (i.e. does not implement the interface Serializable) you can lookup such class from a remote EJB client however when you execute a method you get an error as follows:
> java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling
> The enhancement is to give an error or warning message when the EJB is deployed notifying the developer that he is deploying a Remote EJB that is not implementing the Serializable interface.
> The same thing happens if you deploy an EJB marked with the annotation @Remote but with no @Stateless nor @Statefull annotations.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (WFLY-2509) Method invocation of a non serializable remote EJB
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-2509?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-2509:
--------------------------------------
There is no requirement that EJB's or their remotes implement serialisable (I don't think any of the remote EJB's in our test suite do).
If you are having trouble with remote EJB invocation please ask in the forums first with more details.
> Method invocation of a non serializable remote EJB
> ---------------------------------------------------
>
> Key: WFLY-2509
> URL: https://issues.jboss.org/browse/WFLY-2509
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: omar al kababji
> Assignee: Tomasz Adamski
> Priority: Optional
>
> If you have a remote EJB that is not Serializable (i.e. does not implement the interface Serializable) you can lookup such class from a remote EJB client however when you execute a method you get an error as follows:
> java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling
> The enhancement is to give an error or warning message when the EJB is deployed notifying the developer that he is deploying a Remote EJB that is not implementing the Serializable interface.
> The same thing happens if you deploy an EJB marked with the annotation @Remote but with no @Stateless nor @Statefull annotations.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (WFLY-4188) Client Mapping expressions are allowed but are not resolved if used
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4188?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-4188:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1175442
> Client Mapping expressions are allowed but are not resolved if used
> -------------------------------------------------------------------
>
> Key: WFLY-4188
> URL: https://issues.jboss.org/browse/WFLY-4188
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, ConfigAdmin
> Affects Versions: 8.2.0.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Paul Ferraro
>
> If socket binding with client-mapping is used to provide a valid client address for EJB invocation to the client the expressions are not resolved.
> Depend on the attribute the parsing failed direct during startup (port# is not numeric) or the expression is send to the client where the Exception is thrown at runtime.
> Notice for EJB invocation the problem is only visible if the application is clustered, otherwise the cluster view (where the client-mapping take effect) is not send to the client.
> Dec 17, 2014 2:53:43 PM org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager getEJBReceiver
> INFO: Could not create a connection for cluster node ClusterNode{clusterName='ejb', nodeName='redhat', clientMappings=[ClientMapping{sourceNetworkAddress=/0:0:0:0:0:0:0:0, sourceNetworkMaskBits=0, destinationAddress='${jboss.node.name}', destinationPort=8080}], resolvedDestination=[Destination address=${jboss.node.name}, destination port=8080]} in cluster ejb
> java.lang.RuntimeException: java.io.IOException: java.net.URISyntaxException: Illegal character in authority at index 7: http://@${jboss.node.name}:8080/?#
> at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:92)
> at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:77)
> at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
> at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:79)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:405)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:379)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.io.IOException: java.net.URISyntaxException: Illegal character in authority at index 7: http://@${jboss.node.name}:8080/?#
> at org.jboss.remoting3.remote.HttpUpgradeConnectionProvider.createConnection(HttpUpgradeConnectionProvider.java:102)
> at org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:215)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:298)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:388)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:153)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:133)
> at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:75)
> at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
> at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:79)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:405)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:379)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:388)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:153)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:133)
> at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:75)
> ... 8 more
> Caused by: java.net.URISyntaxException: Illegal character in authority at index 7: http://@${jboss.node.name}:8080/?#
> at java.net.URI$Parser.fail(URI.java:2829)
> at java.net.URI$Parser.parseAuthority(URI.java:3167)
> at java.net.URI$Parser.parseHierarchical(URI.java:3078)
> at java.net.URI$Parser.parse(URI.java:3034)
> at java.net.URI.<init>(URI.java:680)
> at org.jboss.remoting3.remote.HttpUpgradeConnectionProvider.createConnection(HttpUpgradeConnectionProvider.java:100)
> at org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:215)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:298)
> ... 12 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (WFLY-4188) Client Mapping expressions are allowed but are not resolved if used
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created WFLY-4188:
--------------------------------------
Summary: Client Mapping expressions are allowed but are not resolved if used
Key: WFLY-4188
URL: https://issues.jboss.org/browse/WFLY-4188
Project: WildFly
Issue Type: Bug
Components: Clustering, ConfigAdmin
Affects Versions: 8.2.0.Final
Reporter: Wolf-Dieter Fink
Assignee: Paul Ferraro
If socket binding with client-mapping is used to provide a valid client address for EJB invocation to the client the expressions are not resolved.
Depend on the attribute the parsing failed direct during startup (port# is not numeric) or the expression is send to the client where the Exception is thrown at runtime.
Notice for EJB invocation the problem is only visible if the application is clustered, otherwise the cluster view (where the client-mapping take effect) is not send to the client.
Dec 17, 2014 2:53:43 PM org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager getEJBReceiver
INFO: Could not create a connection for cluster node ClusterNode{clusterName='ejb', nodeName='redhat', clientMappings=[ClientMapping{sourceNetworkAddress=/0:0:0:0:0:0:0:0, sourceNetworkMaskBits=0, destinationAddress='${jboss.node.name}', destinationPort=8080}], resolvedDestination=[Destination address=${jboss.node.name}, destination port=8080]} in cluster ejb
java.lang.RuntimeException: java.io.IOException: java.net.URISyntaxException: Illegal character in authority at index 7: http://@${jboss.node.name}:8080/?#
at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:92)
at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:77)
at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:79)
at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:405)
at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:379)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: java.net.URISyntaxException: Illegal character in authority at index 7: http://@${jboss.node.name}:8080/?#
at org.jboss.remoting3.remote.HttpUpgradeConnectionProvider.createConnection(HttpUpgradeConnectionProvider.java:102)
at org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:215)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:298)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:388)
at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:153)
at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:133)
at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:75)
at org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:79)
at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:405)
at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:379)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ...asynchronous invocation...(Unknown Source)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:388)
at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:153)
at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:133)
at org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:75)
... 8 more
Caused by: java.net.URISyntaxException: Illegal character in authority at index 7: http://@${jboss.node.name}:8080/?#
at java.net.URI$Parser.fail(URI.java:2829)
at java.net.URI$Parser.parseAuthority(URI.java:3167)
at java.net.URI$Parser.parseHierarchical(URI.java:3078)
at java.net.URI$Parser.parse(URI.java:3034)
at java.net.URI.<init>(URI.java:680)
at org.jboss.remoting3.remote.HttpUpgradeConnectionProvider.createConnection(HttpUpgradeConnectionProvider.java:100)
at org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:215)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:298)
... 12 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (WFCORE-485) Standalone.bat not support log dir with spaces in path (jboss.server.log.dir)
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-485?page=com.atlassian.jira.plugin... ]
James Perkins moved WFLY-4032 to WFCORE-485:
--------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-485 (was: WFLY-4032)
Affects Version/s: (was: 8.1.0.Final)
Component/s: Logging
Scripts
(was: Logging)
(was: Scripts)
(was: Batch)
> Standalone.bat not support log dir with spaces in path (jboss.server.log.dir)
> -----------------------------------------------------------------------------
>
> Key: WFCORE-485
> URL: https://issues.jboss.org/browse/WFCORE-485
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging, Scripts
> Environment: Windows 7
> Reporter: Duc Quoc
> Assignee: James Perkins
> Priority: Minor
>
> I tried to specify a custom log folder for WildFly, by overriding property jboss.server.log.dir
> https://docs.jboss.org/author/display/WFLY8/Command+line+parameters
> But it only works for folder without space in path. The ones with space when used with "jboss.server.log.dir" will prevent wildfly from starting.
> Working:
> C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat
> C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Windows"
> Not working (server can not start):
> C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> (More info:
> JBoss AS 7.1 works:
> C:\> start C:\jboss-as-7.1.1.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> JBoss EAP 6 and WildFly 8.0 not working either:
> C:\> start C:\jboss-eap-6.2\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> C:\> start C:\wildfly-8.0.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> Aready tried setting jboss.server.log.dir="C:\Program Files" in JAVA_OPTS but did not work either. Should have been fixed in WFLY-1358 or WFLY-2348.
> )
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (WFLY-4032) Standalone.bat not support log dir with spaces in path (jboss.server.log.dir)
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-4032?page=com.atlassian.jira.plugin.... ]
James Perkins reopened WFLY-4032:
---------------------------------
> Standalone.bat not support log dir with spaces in path (jboss.server.log.dir)
> -----------------------------------------------------------------------------
>
> Key: WFLY-4032
> URL: https://issues.jboss.org/browse/WFLY-4032
> Project: WildFly
> Issue Type: Bug
> Components: Batch, Logging, Scripts
> Affects Versions: 8.1.0.Final
> Environment: Windows 7
> Reporter: Duc Quoc
> Assignee: James Perkins
> Priority: Minor
>
> I tried to specify a custom log folder for WildFly, by overriding property jboss.server.log.dir
> https://docs.jboss.org/author/display/WFLY8/Command+line+parameters
> But it only works for folder without space in path. The ones with space when used with "jboss.server.log.dir" will prevent wildfly from starting.
> Working:
> C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat
> C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Windows"
> Not working (server can not start):
> C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> (More info:
> JBoss AS 7.1 works:
> C:\> start C:\jboss-as-7.1.1.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> JBoss EAP 6 and WildFly 8.0 not working either:
> C:\> start C:\jboss-eap-6.2\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> C:\> start C:\wildfly-8.0.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> Aready tried setting jboss.server.log.dir="C:\Program Files" in JAVA_OPTS but did not work either. Should have been fixed in WFLY-1358 or WFLY-2348.
> )
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[JBoss JIRA] (WFLY-4032) Standalone.bat not support log dir with spaces in path (jboss.server.log.dir)
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-4032?page=com.atlassian.jira.plugin.... ]
James Perkins commented on WFLY-4032:
-------------------------------------
Looks like it's only fixed upstream, https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/src.... We won't be back porting it to the 8.x branch as it's frozen.
> Standalone.bat not support log dir with spaces in path (jboss.server.log.dir)
> -----------------------------------------------------------------------------
>
> Key: WFLY-4032
> URL: https://issues.jboss.org/browse/WFLY-4032
> Project: WildFly
> Issue Type: Bug
> Components: Batch, Logging, Scripts
> Affects Versions: 8.1.0.Final
> Environment: Windows 7
> Reporter: Duc Quoc
> Assignee: James Perkins
> Priority: Minor
>
> I tried to specify a custom log folder for WildFly, by overriding property jboss.server.log.dir
> https://docs.jboss.org/author/display/WFLY8/Command+line+parameters
> But it only works for folder without space in path. The ones with space when used with "jboss.server.log.dir" will prevent wildfly from starting.
> Working:
> C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat
> C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Windows"
> Not working (server can not start):
> C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> (More info:
> JBoss AS 7.1 works:
> C:\> start C:\jboss-as-7.1.1.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> JBoss EAP 6 and WildFly 8.0 not working either:
> C:\> start C:\jboss-eap-6.2\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> C:\> start C:\wildfly-8.0.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files"
> Aready tried setting jboss.server.log.dir="C:\Program Files" in JAVA_OPTS but did not work either. Should have been fixed in WFLY-1358 or WFLY-2348.
> )
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 7 months
[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 POST to MODIFIED
> 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, 7 months