[JBoss JIRA] Created: (JBRULES-1262) DSL Parser "eval"
by M H (JIRA)
DSL Parser "eval"
-----------------
Key: JBRULES-1262
URL: http://jira.jboss.com/jira/browse/JBRULES-1262
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 4.0.1
Reporter: M H
Assigned To: Mark Proctor
[when]of type Item=Item()
[when]- Title equals "{value}"=eval(title.isEqual("{value}")
[when]- Event equals "{value}"=eval(id.isEqual("{value}")
[then]Log : "{message}"=System.out.println("{message}");
the dslr File:
expander Test.dsl
rule "Your First Rule"
when
$p : of type Item
- Title equals "test"
- Event equals "test"
then
#actions
end
resolves to (could be seen in the drl viewer)
rule "Your First Rule"
when
$p :Item( eval(title.isEqual("test", eval(id.isEqual("test") ) )
then
#actions
end
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (EJBTHREE-1934) Fix the Webservice testsuite failures on trunk against AS Branch 5_x
by jaikiran pai (JIRA)
Fix the Webservice testsuite failures on trunk against AS Branch 5_x
---------------------------------------------------------------------
Key: EJBTHREE-1934
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1934
Project: EJB 3.0
Issue Type: Task
Components: testsuite
Reporter: jaikiran pai
Assignee: jaikiran pai
Mike runs are showing failures in webservice testcases with JDK 1.6 and AS 5_x branch:
javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:392)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy16.echo(Unknown Source)
at org.jboss.ejb3.test.webservices.unit.WebServiceTestCase.testHandlerContext(WebServiceTestCase.java:117)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.extensions.TestSetup.run(TestSetup.java:27)
Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:445)
at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:87)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:169)
at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:57)
at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
Fix this issue.
--
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
16 years, 9 months
[JBoss JIRA] Created: (JBBUILD-561) Update plugins to latest versions
by Arnaud Heritier (JIRA)
Update plugins to latest versions
---------------------------------
Key: JBBUILD-561
URL: https://jira.jboss.org/jira/browse/JBBUILD-561
Project: JBoss Build System
Issue Type: Task
Components: JBoss Parent POM
Reporter: Arnaud Heritier
Assignee: Arnaud Heritier
Fix For: JBoss Parent POM - 5.0-beta-3
{code}
[INFO] The following plugin updates are available:
[INFO] maven-assembly-plugin ...................... 2.2-beta-2 -> 2.2-beta-4
[INFO] maven-clean-plugin ....................................... 2.2 -> 2.3
[INFO] maven-dependency-plugin .................................. 2.0 -> 2.1
[INFO] maven-ear-plugin ..................................... 2.3.1 -> 2.3.2
[INFO] maven-ejb-plugin ......................................... 2.1 -> 2.2
[INFO] maven-install-plugin ..................................... 2.2 -> 2.3
[INFO] maven-javadoc-plugin ..................................... 2.5 -> 2.6
[INFO] maven-plugin-plugin .................................... 2.4.3 -> 2.5
[INFO] maven-project-info-reports-plugin .................... 2.0.1 -> 2.1.2
[INFO] maven-resources-plugin ................................... 2.3 -> 2.4
[INFO] maven-site-plugin ............................... 2.0-beta-7 -> 2.0.1
[INFO] maven-war-plugin .......................... 2.1-alpha-2 -> 2.1-beta-1
[INFO] org.codehaus.mojo:cobertura-maven-plugin ................. 2.1 -> 2.3
[INFO] org.codehaus.mojo:findbugs-maven-plugin ................ 2.0.1 -> 2.1
[INFO] org.codehaus.mojo:taglist-maven-plugin ................... 2.0 -> 2.4
{code}
--
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
16 years, 9 months
[JBoss JIRA] Created: (JBAS-7310) JChannelFactory not passing ref to protocol to JMX wrapper object
by Brian Stansberry (JIRA)
JChannelFactory not passing ref to protocol to JMX wrapper object
-----------------------------------------------------------------
Key: JBAS-7310
URL: https://jira.jboss.org/jira/browse/JBAS-7310
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.1.0.GA
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-5.2.0.Beta1
The AS JChannelFactory is not passing a ref to the underlying JGroups protocol instance to the org.jgroups.jmx package wrapper object it registers in JMX.
As a result, If you go into the jmx-console and look at any of the mbeans in the jboss.jgroups domain with type=protocol, all of the attribute values are "javax.management.RuntimeMBeanException"
Simple, fix, just add the required call to the wrapper object's attachProtocol method.
--
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
16 years, 9 months
[JBoss JIRA] Created: (JGRP-1069) Log4jImpl: show line numbers of calling class, not of Log4jImpl
by Bela Ban (JIRA)
Log4jImpl: show line numbers of calling class, not of Log4jImpl
---------------------------------------------------------------
Key: JGRP-1069
URL: https://jira.jboss.org/jira/browse/JGRP-1069
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 2.8
Attachments: Log4JLogImpl.java
[David Forget]
We are using log4j as default logger, I have set my appender to use %l as you proposed but all logs from JGroups always have the line number of the log implementer (Log4JLogImpl) as opposed to the class calling the logger. In the following log example (Log4JLogImpl.java:73), but we are interested to get the line number of org.jgroups.JChannel not Log4JLogImpl.
<134>2009-09-29 13:44:12,376 INFO csp_in1 OTHER_0000 "JGroups version:2.8.0.CR2" <VERBOSE=71> [Thread - WrapperStart] (org.jgroups.JChannel)(Log4JLogImpl.java:73) <END>
My log4j.properties
---------------------
log4j.rootLogger=WARN, SYSLOG, FILE, CONSOLE
#define the appender named CONSOLE
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=[%d} [%t] [%-5p] [%c] - [%l][%L][%m][%n]
log4j.logger.org.jgroups=DEBUG
I did a change to Log4JLogImpl to use same method as common logging and it work fine:
<134>2009-10-02 09:54:04,116 INFO csp_in1 OTHER_0000 "JGroups version: 2.8.0.CR2" <VERBOSE=69> [Thread - WrapperStart] (org.jgroups.JChannel) (JChannel.java:1699) <END>
--
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
16 years, 9 months