[JBoss JIRA] Created: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
5:50 p.m.
store element properties in a VARCHAR column instead of LONGVARCHAR for oracle
compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
--
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
5:52 p.m.
New subject: [JBoss JIRA] Updated: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]
Alejandro Guizar updated BPEL-230:
----------------------------------
Description: Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the
JDBC type LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the JDBC type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
7:26 p.m.
New subject: [JBoss JIRA] Updated: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]
Alejandro Guizar updated BPEL-230:
----------------------------------
Issue Type: Bug (was: Feature Request)
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the JDBC type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
8 p.m.
New subject: [JBoss JIRA] Updated: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]
Alejandro Guizar updated BPEL-230:
----------------------------------
Workaround Description: Replace jbpm-bpel.jar in the base directory of the
distribution with the attached file. Rebuild the service archive as described in the
documentation.
Description: Properties of type org.jbpm.bpel.db.type.ElementType in jBPM
BPEL use the SQL type LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
(was: Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the JDBC type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently. )
Workaround: [Workaround Exists]
Changing the column type in org.jbpm.bpel.db.type.ElementType from LONGVARCHAR to VARCHAR
causes Hibernate to generate a column of length 255. Such a short length is likely to be
insufficient for most applications. For this reason, all ElementType occurrences were
given an explicit length of 4000. This figure is consistent with jBPM's
"long" text columns. See
http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmDbCompatibility.
The attached jar has the above changes applied.
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
9:26 p.m.
New subject: [JBoss JIRA] Updated: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]
Alejandro Guizar updated BPEL-230:
----------------------------------
Attachment: jbpm-bpel.jar
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
Attachments: jbpm-bpel.jar
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
6:55 p.m.
New subject: [JBoss JIRA] Updated: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]
Alejandro Guizar updated BPEL-230:
----------------------------------
Attachment: (was: jbpm-bpel.jar)
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
7:03 p.m.
New subject: [JBoss JIRA] Updated: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]
Alejandro Guizar updated BPEL-230:
----------------------------------
Attachment: jbpm-bpel.jar
Updating jar to incorporate resolution of BPEL-231.
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
Attachments: jbpm-bpel.jar
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
5:47 p.m.
New subject: [JBoss JIRA] Resolved: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]
Alejandro Guizar resolved BPEL-230.
-----------------------------------
Resolution: Done
Updated ElementType and its occurrences in mapping documents.
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.GA
Attachments: jbpm-bpel.jar
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
5:23 p.m.
New subject: [JBoss JIRA] Commented: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=comments#action_12364815 ]
Alejandro Guizar commented on BPEL-230:
---------------------------------------
I am removing the patched Jar attached to this issue because it was the source of yet
another unsuspected issue, BPEL-250. If you want the preeliminary binaries towards jBPM
BPEL 1.1.GA visit http://repository.jboss.org/jbpm/bpel/1.1.0.GA/lib/. Please be aware
that these are mere SNAPSHOTS of a yet UNRELEASED version, to be used under your own
risk.
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
Attachments: jbpm-bpel.jar
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
5:25 p.m.
New subject: [JBoss JIRA] Updated: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]
Alejandro Guizar updated BPEL-230:
----------------------------------
Attachment: (was: jbpm-bpel.jar)
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
4:47 a.m.
New subject: [JBoss JIRA] Closed: (BPEL-230) store element properties in a VARCHAR column instead of LONGVARCHAR for oracle compatibility
[ http://jira.jboss.com/jira/browse/BPEL-230?page=all ]
Alejandro Guizar closed BPEL-230.
---------------------------------
store element properties in a VARCHAR column instead of LONGVARCHAR
for oracle compatibility
--------------------------------------------------------------------------------------------
Key: BPEL-230
URL: http://jira.jboss.com/jira/browse/BPEL-230
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
Properties of type org.jbpm.bpel.db.type.ElementType in jBPM BPEL use the SQL type
LONGVARCHAR. HSQL and MySQL support it but not Oracle, apparently.
--
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
6056
days inactive
6542
days old
10 comments
1 participants
participants (1)
-
Alejandro Guizar (JIRA)