[JBoss JIRA] Updated: (JBPM-443) JPBM does not work with MySQL 5.0
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-443?page=all ]
Ronald van Kuijk updated JBPM-443:
----------------------------------
Workaround Description: See the discussion below...
Affects Version/s: jBPM 3.1.2
jBPM 3.1.1
jBPM 3.1
jBPM 3.0.4
jBPM 3.0.3
jBPM 3.0.2
jBPM 3.0.1
jBPM 3.2 alpha 1
Workaround: [Workaround Exists]
> JPBM does not work with MySQL 5.0
> ---------------------------------
>
> Key: JBPM-443
> URL: http://jira.jboss.com/jira/browse/JBPM-443
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.0, jBPM 3.1, jBPM 3.0.1, jBPM 3.0.2, jBPM 3.0.3, jBPM 3.2 alpha 1, jBPM 3.1.1, jBPM 3.1.2, jBPM 3.0.4
> Environment: Windows XP, Mysql 5.0 beta2, JBPM 3.0
> Reporter: Ravi Prakash Reddy Ummadi
> Assigned To: Tom Baeyens
>
> When JBPM is used with MySQL 5.0, the process is skipping the intermediate steps in the process definition.
> The behaviour is unpredictable. The same works fine with MySQL 4.1 and other databases.
> The problem may be in DB scripts ( DB scrips run fine though) or .hbm.xml files .
--
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
19 years, 11 months
[JBoss JIRA] Commented: (JBPM-443) JPBM does not work with MySQL 5.0
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-443?page=comments#action_12340771 ]
Ronald van Kuijk commented on JBPM-443:
---------------------------------------
ok, thanks for finding this. Now we at least have a workaround and pinpointed this. I thought I had 5.0.x but it turned out to be the client version. Shame on me. I run 4.1.x
So there is at least the workaround to define the SQL-Type=Boolean as described in the above link, but maybe adding something to the connectionstring also works:
jdbc:mysql://localhost:3306/database?transformedBitIsBoolean=true
> JPBM does not work with MySQL 5.0
> ---------------------------------
>
> Key: JBPM-443
> URL: http://jira.jboss.com/jira/browse/JBPM-443
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.0, jBPM 3.1, jBPM 3.0.1, jBPM 3.0.2, jBPM 3.0.3, jBPM 3.2 alpha 1, jBPM 3.1.1, jBPM 3.1.2, jBPM 3.0.4
> Environment: Windows XP, Mysql 5.0 beta2, JBPM 3.0
> Reporter: Ravi Prakash Reddy Ummadi
> Assigned To: Tom Baeyens
>
> When JBPM is used with MySQL 5.0, the process is skipping the intermediate steps in the process definition.
> The behaviour is unpredictable. The same works fine with MySQL 4.1 and other databases.
> The problem may be in DB scripts ( DB scrips run fine though) or .hbm.xml files .
--
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
19 years, 11 months
[JBoss JIRA] Created: (JBWEB-67) Patch to fix usabillity issues with the rewrite valve
by Rob Hughes (JIRA)
Patch to fix usabillity issues with the rewrite valve
-----------------------------------------------------
Key: JBWEB-67
URL: http://jira.jboss.com/jira/browse/JBWEB-67
Project: JBoss Web
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Rewrite Valve
Affects Versions: JBoss Web Server 1.0.0 GA
Reporter: Rob Hughes
Assigned To: Mladen Turk
Fix For: JBoss Web Server 1.0.0 GA
Attachments: rewrite_valve.patch
I'm providing this patch which fixes the following issues with the rewrite valve and makes it's behavior more consistent with mod_rewrite.
1: Rewrite conditions were not being processed
2: Case insensitive pattern matches were not working
3: Send redirect with an arbitrary code now works and uses reflection to see if the method is available so the valve will still work with standalone tomcat
4: Patterns are no longer forced to match the whole input for conditions and rules
5: The server variable HTTP_HOST included the port if the server wasn't running on the standard ones (80/443)
6: QSA is how handled and query strings are appended where appropriate
7: Comments are now allowed in the rewrite.properties file
The patch is against the jbossweb trunk.
--
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
19 years, 11 months