[JBoss JIRA] (JBRULES-3438) Blanks between () causes syntax error in DSL expansion
by Wolfgang Laun (JIRA)
Wolfgang Laun created JBRULES-3438:
--------------------------------------
Summary: Blanks between () causes syntax error in DSL expansion
Key: JBRULES-3438
URL: https://issues.jboss.org/browse/JBRULES-3438
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler-DSL
Affects Versions: 5.4.0.Beta2
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Priority: Minor
// === DSL ============================================
[keyword][]greater than=>
[condition][]- where {VarName} is {AttributeName} and is {operator} {value}=
{VarName}: {AttributeName} {operator} {value}
[condition][]ThereIsProgramHistoryData = ProgramHistory ( )
// === DSLR ===========================================
rule lpygt0
when
ThereIsProgramHistoryData
- where $var01 is levelPriorYear and is greater than 0
then
end
// ====================================================
produces incorred DRL due to the redundant spaces in ProgramHistory ( )
ProgramHistory ( , $var01: levelPriorYear > 0 )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] (AS7-4405) JBAS011230: Could not load JAX-RS Application class
by Abhijit Sarkar (JIRA)
Abhijit Sarkar created AS7-4405:
-----------------------------------
Summary: JBAS011230: Could not load JAX-RS Application class
Key: AS7-4405
URL: https://issues.jboss.org/browse/AS7-4405
Project: Application Server 7
Issue Type: Bug
Components: Class Loading
Affects Versions: 7.1.1.Final
Environment: Mac OS X, Apple JDK 1.6.29, JBoss AS 7.1.1.Final
Reporter: Abhijit Sarkar
Assignee: David Lloyd
JAX-RS Resource and an Application class (both files attached). No web.xml. AS 7.1 throws the following exception when the service is deployed.
Tried adding a web.xml, not that it helped, though according to Spec I shouldn't have to. Also tried playing with jboss-deployment-structure.xml. And yes, I definitely read this https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7
14:20:36,333 INFO org.jboss.as.server.deployment (MSC service thread 1-3) JBAS015876: Starting deployment of "jaxrs-basic"
14:20:36,380 ERROR org.jboss.msc.service.fail (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit.jaxrs-basic.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.jaxrs-basic.POST_MODULE: Failed to process phase POST_MODULE of deployment "jaxrs-basic"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) jboss-as-server-7.1.1.Final.jar:7.1.1.Final
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) jboss-msc-1.0.2.GA.jar:1.0.2.GA
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) jboss-msc-1.0.2.GA.jar:1.0.2.GA
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) JBAS011230: Could not load JAX-RS Application class
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) JBAS011230: Could not load JAX-RS Application class
at java.lang.Thread.run(Thread.java:662) JBAS011230: Could not load JAX-RS Application class
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011230: Could not load JAX-RS Application class
at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.scan(JaxrsScanningProcessor.java:221)
at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.deploy(JaxrsScanningProcessor.java:101)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) jboss-as-server-7.1.1.Final.jar:7.1.1.Final
... 5 more
Caused by: java.lang.ClassNotFoundException: edu.certification.abhijitsarkar.ocewsd.jaxrs.basic.CarApplication from [Module "deployment.jaxrs-basic:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.scan(JaxrsScanningProcessor.java:217)
... 7 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] (AS7-4406) JBAS015507: Handler chain config file not found in ResourceRoot
by Abhijit Sarkar (JIRA)
Abhijit Sarkar created AS7-4406:
-----------------------------------
Summary: JBAS015507: Handler chain config file not found in ResourceRoot
Key: AS7-4406
URL: https://issues.jboss.org/browse/AS7-4406
Project: Application Server 7
Issue Type: Bug
Components: Web Services
Affects Versions: 7.1.1.Final
Environment: Mac OS X, Apple JDK 1.6.29, JBoss AS 7.1.1.Final
Reporter: Abhijit Sarkar
Assignee: Alessio Soldano
AS 7 can't find the handler config file configured on JAX-WS Stateless EJB3 Endpoint.
23:57:07,279 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit.jaxrs-ejb.PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit.jaxrs-ejb.PARSE: Failed to process phase PARSE of deployment "jaxrs-ejb"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
Caused by: javax.xml.ws.WebServiceException: JBAS015507: Handler chain config file /handler-chain.xml not found in ResourceRoot [root="/content/jaxrs-ejb"]
at org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor.getInputStream(WSHandlerChainAnnotationProcessor.java:158)
at org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor.processHandlerChainAnnotation(WSHandlerChainAnnotationProcessor.java:130)
at org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor.processHandlerChainAnnotations(WSHandlerChainAnnotationProcessor.java:116)
at org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor.deploy(WSHandlerChainAnnotationProcessor.java:93)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBRULES-1917) JBRMS does not support business rules with non ascii characters
by Gregory Chazalon (JIRA)
JBRMS does not support business rules with non ascii characters
---------------------------------------------------------------
Key: JBRULES-1917
URL: https://jira.jboss.org/jira/browse/JBRULES-1917
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.7
Reporter: Gregory Chazalon
Assignee: Mark Proctor
A very simple rule containing some Latin1 characters (e.g. 'é', 'à'..), is not compiled correctly when using the JBRMS web app.
The exact same rule defined in a DRL file, and compiled with the drools compiler API is well handled (no characters mismatch).
Actually, the rule defined both ways is :
{code}
rule "latin_message"
when
Let information message
then
information message containing latin characters léger problème à résoudre hôpital
end
{/code}
I strongly suspect a poor character encoding scheme inside the JBRMS code, but I haven't been able to identify it.
The problem is illustrated by the LatinMessageTest test case, bundled inside the small eclipse project provided.
It has two test methods, one building the rule using the drools compiler API, and the other using a binary package built with JBRMS.
The second one fails as of the poor character encoding suspected inside JBRMS web app.
Any help is appreciated.
--
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
14 years
[JBoss JIRA] Created: (JBRULES-3166) Improve the support for monitoring/conformance rules
by Davide Sottara (JIRA)
Improve the support for monitoring/conformance rules
-----------------------------------------------------
Key: JBRULES-3166
URL: https://issues.jboss.org/browse/JBRULES-3166
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-core (expert), drools-core (fusion)
Reporter: Davide Sottara
Assignee: Mark Proctor
Priority: Optional
Often, rules are written to monitor the state of a system. When the state (does not) matches the expressed conditions, appropriate actions are taken.
In addition, notification events could/should be generated for further processing. Drools could provide a dedicated syntax to facilitate the authoring of such rules.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBRULES-1602) The order of RHS statements shouldn't affect behavior (insertLogical)
by Patrick Gras (JIRA)
The order of RHS statements shouldn't affect behavior (insertLogical)
---------------------------------------------------------------------
Key: JBRULES-1602
URL: http://jira.jboss.com/jira/browse/JBRULES-1602
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Drools 4.0.7 & 4.0.4, Java5, eclipse compiler, windows XP.
Reporter: Patrick Gras
Assigned To: Mark Proctor
I have a class 'Cat' that is dynamic (JavaBean with PropertyChangeSupport ) with only a 'name' attribute.
Then I have the following rule:
rule "test"
when
$cat:Cat( name == "tom" )
then
$cat.setName("cat");
insertLogical(new String("test"));
end
When I test the rule against a Cat named tom, the logical inserted fact is not retracted. (So the fact is inserted because the rule matches, but is not retracted even if the rule is no more matching at the end.)
If I change the order of the RHS, it works fine. The fact is inserted and then retracted.
rule "test"
when
$cat:Cat( name == "tom" )
then
insertLogical(new String("test"));
$cat.setName("cat");
end
So the behavior depends on the ordering of the RHS statements.
Here is a complete example to show the problem:
public class Cat {
private String name;
protected PropertyChangeSupport changes = new PropertyChangeSupport(this);
public Cat(String name) {
super();
this.name = name;
}
public String getName() {
return this.name;
}
public void setName(String name) {
final String oldName = this.name;
this.name = name;
this.changes.firePropertyChange("name", oldName, name);
}
public void addPropertyChangeListener(final PropertyChangeListener listener) {
this.changes.addPropertyChangeListener(listener);
}
public void removePropertyChangeListener(
final PropertyChangeListener listener) {
this.changes.removePropertyChangeListener(listener);
}
}
public class RHSOrderingTest {
private static final String PACKAGE = "package ch.generali.pgr.rule ";
private static final String IMPORT = "import ch.generali.pgr.rules.Cat ";
private static final String WHEN = "rule \"test ok\" when $cat:Cat( name == \"tom\" ) ";
private static final String THEN_OK = "then insertLogical(Integer.valueOf(1)); $cat.setName(\"cat\"); end";
private static final String THEN_KO = "then $cat.setName(\"cat\"); insertLogical(Integer.valueOf(1)); end";
private static final String RULE_OK = PACKAGE + IMPORT + WHEN + THEN_OK;
private static final String RULE_KO = PACKAGE + IMPORT + WHEN + THEN_KO;
private static final String QUERY = "query \"My test Integer\" integer : Integer( intValue == 1 ) end";
public static void main(String[] args) {
boolean ok_1 = testWithRule(RULE_OK);
boolean ok_2 = testWithRule(RULE_KO);
System.out.println((ok_1 ? "SUCCESS: " : "FAILED: ") + THEN_OK);
System.out.println((ok_2 ? "SUCCESS: " : "FAILED: ") + THEN_KO);
}
private static boolean testWithRule(String rule) {
Cat tom = new Cat("tom");
RuleBase rb = createRuleBase(rule + "\n" + QUERY);
WorkingMemory wm = rb.newStatefulSession();
wm.insert(tom, true);
wm.fireAllRules();
QueryResults results = wm.getQueryResults("My test Integer");
return results.size() == 0;
}
private static RuleBase createRuleBase(String rules) {
try {
RuleBase ruleBase = RuleBaseFactory.newRuleBase();
PackageBuilderConfiguration conf = new PackageBuilderConfiguration();
PackageBuilder packageBuilder = new PackageBuilder(conf);
Reader source = new StringReader(rules);
packageBuilder.addPackageFromDrl(source);
Package pkg = packageBuilder.getPackage();
ruleBase.addPackage(pkg);
return ruleBase;
} catch (Exception e) {
throw new RuntimeException(e);
}
}
}
--
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
14 years
[JBoss JIRA] (AS7-4372) EJB remoting server side doesn't honour the max outbound messages configured on a channel
by jaikiran pai (JIRA)
jaikiran pai created AS7-4372:
---------------------------------
Summary: EJB remoting server side doesn't honour the max outbound messages configured on a channel
Key: AS7-4372
URL: https://issues.jboss.org/browse/AS7-4372
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
While sending out messages/responses on the EJB remote channel, the server side doesn't take into account the configured max outbound messages on the channel. This can lead to the following exception on the server side:
{code}
org.jboss.remoting3.ChannelBusyException: Too many open outbound writes
at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:111) [jboss-remoting-3.2.4.GA.jar:3.2.4.GA]
at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296) [jboss-remoting-3.2.4.GA.jar:3.2.4.GA]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.writeMethodInvocationResponse(MethodInvocationMessageHandler.java:330)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$500(MethodInvocationMessageHandler.java:64)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:226)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_b147-icedtea]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_b147-icedtea]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_b147-icedtea]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_b147-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_b147-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_b147-icedtea]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years