[JBoss JIRA] Created: (JBMESSAGING-585) WebServices is having trouble using Messaging
by Ovidiu Feodorov (JIRA)
WebServices is having trouble using Messaging
---------------------------------------------
Key: JBMESSAGING-585
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-585
Project: JBoss Messaging
Issue Type: Bug
Components: AS Integration
Reporter: Ovidiu Feodorov
Assigned To: Clebert Suconic
Fix For: 1.2.0.Alpha2
Thomas Diesler's report (1):
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi Folks,
on jbossas/trunk this jboss-service.xml does not deploy
<server>
<mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=RequestQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends>
</mbean>
<mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=ResponseQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends>
</mbean>
</server>
2006-09-05 10:17:36,612 DEBUG [org.jboss.deployment.SARDeployer:292] Deploying SAR, start step: url file:/home/tdiesler/svn/jboss/jbossas/trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jbossws-samples-jmstransport.sar
2006-09-05 10:17:36,612 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=RequestQueue
2006-09-05 10:17:36,614 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=RequestQueue on
2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=ResponseQueue
2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=ResponseQueue on
2006-09-05 10:17:36,631 DEBUG [org.jboss.deployment.MainDeployer:1032] End deployment start on package: jbossws-samples-jmstransport.sar
>From the error output I cannot figure out what is missing.
2006-09-05 10:17:36,653 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner:660] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB
State: INSTALLED
ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue
State: CONFIGURED
ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue
State: CONFIGURED
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue
State: CONFIGURED
ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue
State: CONFIGURED
ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB
State: INSTALLED
Hi Folks,
on jbossas/trunk this jboss-service.xml does not deploy
<server>
<mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=RequestQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends>
</mbean>
<mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=ResponseQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends>
</mbean>
</server>
2006-09-05 10:17:36,612 DEBUG [org.jboss.deployment.SARDeployer:292] Deploying SAR, start step: url file:/home/tdiesler/svn/jboss/jbossas/trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jbossws-samples-jmstransport.sar
2006-09-05 10:17:36,612 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=RequestQueue
2006-09-05 10:17:36,614 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=RequestQueue on
2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=ResponseQueue
2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=ResponseQueue on
2006-09-05 10:17:36,631 DEBUG [org.jboss.deployment.MainDeployer:1032] End deployment start on package: jbossws-samples-jmstransport.sar
>From the error output I cannot figure out what is missing.
2006-09-05 10:17:36,653 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner:660] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB
State: INSTALLED
ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue
State: CONFIGURED
ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue
State: CONFIGURED
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue
State: CONFIGURED
ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue
State: CONFIGURED
ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB
State: INSTALLED
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Thomas Diesler's report (2):
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Please follow
How can I build and install the latest?
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstallJBoss50x
Instead of Step 8, do
8. Run the jbossws testsuite
cd jbossws/src/test
ant main
ant -Dtest=org.jboss.test.ws.samples.jmstransport.JMSTransportTestCase one-test
You can also run
ant tests-samples
--
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
18 years, 11 months
[JBoss JIRA] Created: (JBRULES-439) Feature request for the rule parser / compiler that would make the code in the eclipse IDE easier
by Kris Verlaenen (JIRA)
Feature request for the rule parser / compiler that would make the code in the eclipse IDE easier
-------------------------------------------------------------------------------------------------
Key: JBRULES-439
URL: http://jira.jboss.com/jira/browse/JBRULES-439
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Reporter: Kris Verlaenen
Assigned To: Mark Proctor
This JIRA explains what improvements to the DRL parser could be very useful in the IDE.
Currently, the eclipse IDE uses the rule parser to
- create an outline view based on the PackageDescr returned when parsing the DRL file
- retrieve all imports, all functions, all queries, all templates and the package of a DRL file (so they can be used later, for example when performing auto-completion)
- determine the location of the cursor when requesting auto-completion (the part of the rule before the cursor is parsed, and based on the (unsually partically incomplete) PackageDescr returned by the parser, I try to determine in what kind of location the cursor is situation, e.g. the beginning of a column constraint, or inside an eval statement)
- retrieve all parameters defined in a rule (possibly before a certain location) when auto-completion has been requested
- retrieve errors and warnings that signal certain syntax errors in the DRL file
Other places were the results of the DRL parser could be used:
- determine which element is selected based on a character selection range
- provide real-time syntax checking
- determine what has changed after the DRL has been changed
- do refactoring
- automatic error solving
Although the info returned by the parser is very useful, I think we are kind of reaching the boundary of what we can do with the info that is currently returned. I'll try to describe possible enhancements that could allow us to do more advanced IDE features as well.
* Use of character number in addition with line number + column
Eclipse uses character numbers instead of line + column numbers in almost all situations. A character number describes at which location a certain character occurs since the beginning of the file (and not like column since the beginning of the line). Although we could try to create a mapping between character number and line + column number, this has resulted in some annoying errors related to the newline character which is different on different platforms. Using character numbers would eliminate this problem.
* All elements in the PackageDescr should have a start location
Currently, most do (PatternDescr has a getLine() and getColumn()), but some elements in the PackageDescr returned by the parser still don't:
- FunctionDescr has no line and column
- imports are just strings
- the package has no location
To be able to use this information for more advanced features, it would be necessary that all elements contain a start location (now the IDE usually does additional parsing to determine the location of these elements).
* All elements should also have an end location
Although PatternDescr has a getEndLine() and getEndColumn(), currently, only the end location of ColumnDescr is stored (thx mic for adding this already since it was necessary for code completion). To be able to use this information for more advanced features, it would be necessary that all elements contain an end location (now the IDE usually does additional parsing to determine the end location of these elements).
* For nested elements, this should be the same as much as possible
Like RuleDescr contains ColumnDescr contains FieldConstraintDescrs, each of these elements should contain a start and end location (where the start and end of the sub-descriptions are of course located inside the start and end location of its parent. I believe that this is already working quite well in the current implementation for the start location of elements.
* The parser should return as much info as possible, even if the rule is incomplete
This is very important since the DrlParser is used a lot when the DRL is not yet completely finished (for example when performing auto-completion). It would be crucial that the parser does not just return an error when it encounters an error, but tries to parse the remainder of the file as well, and tries to return as much info as possible. For example, when trying to parse the following incomplete rule:
rule MyRule
MyClass (
the parser should ideally return a RuleDescr with name MyRule, containing as lhs one ColumnDescr, with name MyClass, a start location, but no end location (since the end of the ColumnDescr has not been reached yet, since the closing bracket is missing). This used to work like this in the 3.0.x release. I have noticed though that the 3.1 branch now returns null as only sub-description. Similarly, when using an eval, currently the EvalDescr is only added to the RuleDescr once the eval has been closed. As a result, the IDE has to redo a lot of parsing to check for these situations as well. If the parser always returns as much info as available (by for example adding subdescr once they are started, not only when they are finished), the IDE would not have to do as much parsing itself.
* All errors and warnings try to give exact locations in the drl
Although previous improvements have made the errors returned by the parser already very useful, more precise feedback could be given when the exact location of the errors could be returned, preferably as character start and end, but line numbers can be used here as well. Currently, the error is mostly indicated on the start line of the rule that contains the error. More precise error determination is necessary for more precise error visualization, automatic error solving, etc.
I hope this kind of explains what improvements to the parser could be very useful to the IDE and why.
--
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
18 years, 11 months
[JBoss JIRA] Created: (JBAS-3738) On Windows: timer.test.BasicTimerUnitTestCase fails
by Prabhat Jha (JIRA)
On Windows: timer.test.BasicTimerUnitTestCase fails
---------------------------------------------------
Key: JBAS-3738
URL: http://jira.jboss.com/jira/browse/JBAS-3738
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Environment: Windows 2003, Sun JDK1.4
Reporter: Prabhat Jha
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.0.5.GA
Test Class: org.jboss.test.timer.test.BasicTimerUnitTestCase
Test Name: testMDBTimer
Message property 'UNIQUE_ID' not set.
java.lang.NumberFormatException: Message property 'UNIQUE_ID' not set.
at org.jboss.mq.SpyMessage.getIntProperty(SpyMessage.java:581)
at org.jboss.test.timer.test.BasicTimerUnitTestCase.testMDBTimer(BasicTimerUnitTestCase.java:332)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
--
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
18 years, 11 months
[JBoss JIRA] Created: (JBRULES-532) Query feature doesnt seem to work if there is more than one query.
by Sridhar Chandrasekharan (JIRA)
Query feature doesnt seem to work if there is more than one query.
------------------------------------------------------------------
Key: JBRULES-532
URL: http://jira.jboss.com/jira/browse/JBRULES-532
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Sridhar Chandrasekharan
Assigned To: Mark Proctor
Consider the following:-
*******************************************************************************
1) Foo.java
package com.foo;
public class Foo {
private int a;
private int b;
public Foo(int a, int b) {
super();
this.a = a;
this.b = b;
}
public boolean test()
{
return (a > b);
}
public int getA() {
return a;
}
public int getB() {
return b;
}
}
*******************************************************************************************
2) FooTest.java
package com.foo;
import java.io.InputStreamReader;
import java.io.*;
import java.util.*;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.rule.Package;
import org.drools.QueryResults;
import org.drools.QueryResult;
public class FooTest {
/**
* This is a sample file to launch a rule package from a rule source file.
*/
public static final void main(String[] args) {
try {
//load up the rulebase
RuleBase ruleBase = readRule();
WorkingMemory workingMemory = ruleBase.newWorkingMemory();
//go !
workingMemory.fireAllRules();
QueryResults results = workingMemory.getQueryResults( "Foo query" );
if(results == null)
{
System.out.println("Result is null");
return;
}
System.out.println( "we have " + results.size() );
for ( Iterator it = results.iterator(); it.hasNext(); ) {
QueryResult result = ( QueryResult ) it.next();
Foo foo = ( Foo ) result.get( "foo" );
System.out.println( "A="+foo.getA() + " B=" + foo.getB());
}
} catch (Throwable t) {
t.printStackTrace();
}
}
/**
* Please note that this is the "low level" rule assembly API.
*/
private static RuleBase readRule() throws Exception {
//read in the source
Reader source = new InputStreamReader( FooTest.class.getResourceAsStream( "/Foo.drl" ) );
//optionally read in the DSL (if you are using it).
//Reader dsl = new InputStreamReader( DroolsTest.class.getResourceAsStream( "/mylang.dsl" ) );
//Use package builder to build up a rule package.
//An alternative lower level class called "DrlParser" can also be used...
PackageBuilder builder = new PackageBuilder();
//this wil parse and compile in one step
//NOTE: There are 2 methods here, the one argument one is for normal DRL.
builder.addPackageFromDrl( source );
//Use the following instead of above if you are using a DSL:
//builder.addPackageFromDrl( source, dsl );
//get the compiled package (which is serializable)
Package pkg = builder.getPackage();
//add the package to a rulebase (deploy the rule package).
RuleBase ruleBase = RuleBaseFactory.newRuleBase();
ruleBase.addPackage( pkg );
return ruleBase;
}
}
**************************************************
3) Foo.drl
#created on: Oct 9, 2006
package com.foo
rule "Initialization rule"
when
#conditions
then
assert(new Foo(1,1));
assert(new Foo(2,1));
assert(new Foo(2,3));
assert(new Foo(3,2));
assert(new Foo(3,4));
assert(new Foo(4,3));
end
query "Foo query"
foo : Foo()
end
****************************************
The output is as follows:-
we have 6
A=1 B=1
A=2 B=1
A=2 B=3
A=3 B=2
A=3 B=4
A=4 B=3
*****************************************
Now add another query to the Foo.drl file
query "Bar query"
foo : Foo()
end
and the output is
Result is null
Adding a second query caused the first query to stop working properly.
--
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
18 years, 11 months
[JBoss JIRA] Created: (JBRULES-372) QueryResult.get fires ClassCastException when using the string argument
by Giovanni Cuccu (JIRA)
QueryResult.get fires ClassCastException when using the string argument
-----------------------------------------------------------------------
Key: JBRULES-372
URL: http://jira.jboss.com/jira/browse/JBRULES-372
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBoss Rules 3.0.1 and JBoss Rules as downloaded from svn trunk as of 12/07/06
Reporter: Giovanni Cuccu
Assigned To: Mark Proctor
here is the simple test case:
package simpletest;
public class AssertedObject {
private String value;
public String getValue() {
return value;
}
public void setValue(String value) {
this.value = value;
}
public AssertedObject(String value) {
// TODO Auto-generated constructor stub
this.value = value;
}
}
package simpletest;
import simpletest.AssertedObject;
rule rule1
when
then
assert( new AssertedObject( "value1") );
assert( new AssertedObject( "value2") );
end
query "assertedobjquery"
assertedobj : AssertedObject( value=="value1" )
end
package simpletest;
import java.io.InputStreamReader;
import java.util.HashMap;
import java.util.Iterator;
import java.util.Map;
import mit.rules.test.Prestazione;
import mit.rules.test.StrutturaErogante;
import mit.rules.test.TempiAttesa;
import mit.rules.test.TestRules;
import org.drools.QueryResult;
import org.drools.QueryResults;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.audit.WorkingMemoryFileLogger;
import org.drools.compiler.PackageBuilder;
public class TestQuery {
public static void main(String[] args) throws Exception {
// TODO Auto-generated method stub
final PackageBuilder builder = new PackageBuilder();
builder.addPackageFromDrl( new InputStreamReader( TestQuery.class.getResourceAsStream( "testquery.drl" ) ) );
final RuleBase ruleBase = RuleBaseFactory.newRuleBase();
ruleBase.addPackage( builder.getPackage() );
final WorkingMemory workingMemory = ruleBase.newWorkingMemory();
fireRules(workingMemory);
}
public static void fireRules(WorkingMemory workingMemory) {
final WorkingMemoryFileLogger logger = new WorkingMemoryFileLogger( workingMemory );
logger.setFileName( "log/testquery" );
workingMemory.fireAllRules();
QueryResults results = workingMemory.getQueryResults( "assertedobjquery" );
if (results==null || !results.iterator().hasNext()) {
System.err.println("Empty list");
} else {
for ( Iterator it = results.iterator(); it.hasNext(); ) {
QueryResult result = ( QueryResult )it.next();;
AssertedObject assertedObject=(AssertedObject)result.get( "assertedobj" );
System.out.println("AssertedObject with value " + assertedObject.getValue());
}
}
logger.writeToDisk();
}
}
--
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
18 years, 11 months
[JBoss JIRA] Created: (JBRULES-445) behavior of globals?
by G￡bor Lipt￡k (JIRA)
behavior of globals?
--------------------
Key: JBRULES-445
URL: http://jira.jboss.com/jira/browse/JBRULES-445
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.0.4
Reporter: G￡bor Lipt￡k
Assigned To: Mark Proctor
Priority: Minor
It seems that the value of DRL globals without external env backup is removed between rules:
package globaltest
import Policy;
global java.lang.String text;
rule "Foo"
salience 999
when
Policy()
then
text="foo";
System.out.println("foo+"+text);
end
rule "Bar"
salience 998
when
Policy()
then
System.out.println("bar+"+text);
text="bar";
System.out.println("bar+"+text);
end
results in:
foo+foo
bar+null
bar+bar
The documentation does not seem to provide details if this is the expected behavior.
Please comment. Thanks
--
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
18 years, 12 months