[JBoss JIRA] Created: (JBRULES-2745) Problems in the use of escapes in the "matches" operator
by Alessandro Lazarotti (JIRA)
Problems in the use of escapes in the "matches" operator
--------------------------------------------------------
Key: JBRULES-2745
URL: https://jira.jboss.org/browse/JBRULES-2745
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Alessandro Lazarotti
Assignee: Mark Proctor
According to official documentation, it is not necessary to use escapes:
"In contrast to Java, escapes are not needed within regular expressions written as string literals." (a note in topic 4.8.2.1.5.)
But it is not true. Actually even the example of the documentation does not work if you do not use escape:
//type is a String
Cheese( type matches "(Buffalo)?\S*Mozarella" )
... should be changed to:
//type is a String
Cheese( type matches "(Buffalo)?\\S*Mozarella" )
Curiously, if you have a attribute of the attribute which matches a regex, you shouldn't use escapes:
//type is "complex type" and value is a String
Cheese( type.value matches "(Buffalo)?\S*Mozarella" )
... it's work!
That said, a workaround to work with simple String attributes, you should use "toString":
//type is "String"
Cheese( type.toString matches "(Buffalo)?\S*Mozarella")
--
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: (JBJCA-449) TransactionSynchronization initialization incomplete causing NullPointerException.
by Jeremy Whiting (JIRA)
TransactionSynchronization initialization incomplete causing NullPointerException.
----------------------------------------------------------------------------------
Key: JBJCA-449
URL: https://jira.jboss.org/browse/JBJCA-449
Project: IronJacamar
Issue Type: Task
Components: Standalone
Environment: All environments.
Reporter: Jeremy Whiting
Assignee: Jesper Pedersen
When an application uses a transaction with the UserTransaction to perform state changes the server throws a NullPointerException.
This occurs when UserTransaction.begin() is called.
The cause is the TransactionSynchronization object has not been associated with the TransactionManager before the call to begin().
Included with this issue is a patch for org.jboss.jca.core.connectionmanager.ConnectionManagerFactory. The patch adds initialization code when the factory creates a transactional (versus a nonTransactional) ConnectionManager.
--
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: (JBJCA-447) Patch to add UserTransaction support.
by Jeremy Whiting (JIRA)
Patch to add UserTransaction support.
-------------------------------------
Key: JBJCA-447
URL: https://jira.jboss.org/browse/JBJCA-447
Project: IronJacamar
Issue Type: Task
Components: Core
Environment: All environments.
Reporter: Jeremy Whiting
Assignee: Jesper Pedersen
Priority: Minor
Attachments: diff-ironmanjca.txt, UserTransactionTestCase.java
An application wanting to use the UserTransaction object to demarcate a unit of work cannot do so.
This patch adds changes to the codebase which binds the UserTransaction object to JNDI.
The attached files are:
* An svn diff with changes to
- transaction.xml
* A unit test case to check the object can now use a Context to look up UserTransaction.
--
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