[JBoss JIRA] Created: (JBRULES-965) Unexpected token 'not'
by Brian Enderle (JIRA)
Unexpected token 'not'
-----------------------
Key: JBRULES-965
URL: http://jira.jboss.com/jira/browse/JBRULES-965
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 4.0.0.MR3
Environment: Win XP, Drools MR3 (Snapshot from 7/2/2007)
Reporter: Brian Enderle
Assigned To: Mark Proctor
Priority: Minor
Attachments: Address.drl
The following rule works in a DRL file
$i : Address( city not matches "[ a-zA-Z]" )
But when entered into a DSL file an "Unexpected token 'not'" error is thrown.
DRL file: DSL entry:
There is a Address $i : {Instance}()
- city is not alpha only {field} not matches "[ a-zA-Z]"
--
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
17 years, 6 months
[JBoss JIRA] Created: (JBAS-4488) Write BMTCleanUp tests for web-apps
by Adrian Brock (JIRA)
Write BMTCleanUp tests for web-apps
-----------------------------------
Key: JBAS-4488
URL: http://jira.jboss.com/jira/browse/JBAS-4488
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Reporter: Adrian Brock
Assigned To: Remy Maucherat
Priority: Blocker
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.1.CR1
We need to port the BMTCleanUp tests described on JBAS-4487 to web applications.
The fix has already been applied to the CachedConnectionValve.
The difficulty is that Tomcat does not provide a way to guarantee that two requests will occur on the same thread.
One possiblity is to deploy an additional connector on a different tcp/ip port with a max thread pool size of 1
just for this test.
--
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
17 years, 6 months
[JBoss JIRA] Created: (JGRP-543) build.xml: target one-test doesn't work
by Bela Ban (JIRA)
build.xml: target one-test doesn't work
---------------------------------------
Key: JGRP-543
URL: http://jira.jboss.com/jira/browse/JGRP-543
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.5
To reproduce:
./build.sh -v -Dtest=org.jgroups.tests.FlushTest one-test
Output includes:
runtests:
Property ${testname.ext} has not been set
Property ${formatter.class} has not been set
[echo] Tests running with parameters:
[echo] channel.conf=udp.xml
[echo] channel.conf.flush=flush-udp.xml
[echo] mux.on=false
[echo] mux.conf=stacks.xml
[echo] mux.conf.stack=udp
[echo] mux.factorycount=4
[echo] threadcount=false
[echo] test.verbose=true
[echo] testname.ext=${testname.ext}
[echo] formatter.class=${formatter.class}
[echo]
[echo] Using set: one.test
Property ${testname.ext} has not been set
Property ${testname.ext} has not been set
[antcall] Exiting C:\JGroups\build.xml.
BUILD SUCCESSFUL
Total time: 1 second
--
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
17 years, 6 months
[JBoss JIRA] Created: (JBAS-4510) Upgrade jboss remoting to v2.2.1.GA (from v2.2.0.SP4)
by Dimitris Andreadis (JIRA)
Upgrade jboss remoting to v2.2.1.GA (from v2.2.0.SP4)
-----------------------------------------------------
Key: JBAS-4510
URL: http://jira.jboss.com/jira/browse/JBAS-4510
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Remoting
Affects Versions: JBossAS-4.2.0.GA
Reporter: Dimitris Andreadis
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.1.GA
Upgrade jboss remoting to 2.2.1.GA to incorporate some nice (and backwards compatible fixes):
JBREM-747: "org.jboss.remoting.transport.Connector should unregister server invoker from MBeanServer"
JBREM-748: "BisocketClientInvoker should guard agains scheduling on an expired Timer"
JBREM-751: "Eliminate unnecessary "Unable to process control connection:" message from BisocketServerInvoker"
JBREM-761: "NPE in BisocketServerInvoker$ControlConnectionThread"
Ron has also added a 2.2.1.GA <--> 2.2.0.SP4 compatibility test to the Remoting compatibility test suite. 2.2.1.GA is compatible back to 1.4.3.GA, which covers JBossAS 4.0.4, 4.0.5, and 4.2.0.
Thanks Ron.
--
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
17 years, 6 months