[JBoss JIRA] Created: (JBAS-8541) Deploying an application that has its own slf4j jars causes errors in the server log
by Nikita D (JIRA)
Deploying an application that has its own slf4j jars causes errors in the server log
------------------------------------------------------------------------------------
Key: JBAS-8541
URL: https://jira.jboss.org/browse/JBAS-8541
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: JBossAS-5.1.0.GA
Reporter: Nikita D
Assignee: David Lloyd
Priority: Minor
If an application depends on a different version of slf4j than the one packaged with JBoss, the slf4j jars (api and impl) need to be included with the application. This results in the "multiple SLF4J bindings" error message:
00:34:25,247 ERROR [STDERR] SLF4J: Class path contains multiple SLF4J bindings.
00:34:25,247 ERROR [STDERR] SLF4J: Found binding in [vfszip:/C:/a/bin/jboss/jboss-5.1.0.GA/common/lib/slf4j-jboss-logging.jar/org/slf4j/impl/StaticLoggerBinder.class]
00:34:25,247 ERROR [STDERR] SLF4J: Found binding in [vfszip:/c:/a/ear/suite.ear/lib/slf4j-log4j12-1.5.8.jar/org/slf4j/impl/StaticLoggerBinder.class]
00:34:25,247 ERROR [STDERR] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JBPORTAL-2487) Create a wizard for generating a portal extension
by eric schabell (JIRA)
Create a wizard for generating a portal extension
-------------------------------------------------
Key: JBPORTAL-2487
URL: https://jira.jboss.org/browse/JBPORTAL-2487
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Samples
Environment: Working with JBoss EPP 5.x versions
Reporter: eric schabell
Fix For: 2.8 Final
Working with extenstions like the one I will attach or the one provided in the docs directory is a bit cumbersome. Can we have someone setup a wizard for the portal to generate an extension project. Maybe a maven archtype would be enough but not sure. Would be great to have this in the portal tooling.
PS. feel free to categorize this with the proper project, not sure if it should be in JBoss Tools or not?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JBRULES-2224) multi-restriction pattern throws UnsupportedOpEx
by Wolfgang Laun (JIRA)
multi-restriction pattern throws UnsupportedOpEx
------------------------------------------------
Key: JBRULES-2224
URL: https://jira.jboss.org/jira/browse/JBRULES-2224
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.0.1.FINAL
Reporter: Wolfgang Laun
Assignee: Mark Proctor
rule "same"
when
$m : ShGraphType( $x25No : x25No, $trans : trans )
GoType( x25No == $x25No || == ($x25No % 2000), trans != $trans ) #!!!#
$e : ShType( x25No == $x25No )
$v : View( elemSet contains $m )
then
Field x25No is an int.
The marked pattern is not flagged in Eclipse, passes the compiler without an error, but crashes at runtime during fact insertion with:
Exception in thread "main" java.lang.UnsupportedOperationException: does not support method call isAllowed(Object object, InternalWorkingMemory workingMemoiry)
at org.drools.rule.ReturnValueRestriction.isAllowedCachedRight(ReturnValueRestriction.java:252)
at org.drools.rule.OrCompositeRestriction.isAllowedCachedRight(OrCompositeRestriction.java:51)
at org.drools.rule.MultiRestrictionFieldConstraint.isAllowedCachedRight(MultiRestrictionFieldConstraint.java:115)
at org.drools.common.DoubleBetaConstraints.isAllowedCachedRight(DoubleBetaConstraints.java:181)
at org.drools.reteoo.JoinNode.assertObject(JoinNode.java:172)
at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:360)
at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:344)
at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:184)
at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:146)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1094)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:1045)
at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:830)
at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:219)
at rss.checker.engine.impl.DroolsEngine.insert(DroolsEngine.java:61)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (JBAS-8521) Filters not registered when applications start up
by Lincoln Baxter III (JIRA)
Filters not registered when applications start up
-------------------------------------------------
Key: JBAS-8521
URL: https://jira.jboss.org/browse/JBAS-8521
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Java EE APIs
Affects Versions: 6.0.0.M5
Environment: JBoss AS M5 - Ubuntu 10.10
Reporter: Lincoln Baxter III
Assignee: Shelly McGowan
It seems like custom filters are not being booted when JBoss starts applications - place a breakpoint in PrettyFilter.init(ServletContext context) and it will never fire. Nor is the filter ever invoked on web-requests.
The attached application can be used to reproduce this on M5. This works on Glassfish.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months