You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Marco Zapletal (JIRA)" <ji...@apache.org> on 2011/01/04 19:37:46 UTC
[jira] Created: (CAMEL-3488) Some of JpaTraceEventMessage's
attributes require @Lob annotation
Some of JpaTraceEventMessage's attributes require @Lob annotation
-----------------------------------------------------------------
Key: CAMEL-3488
URL: https://issues.apache.org/jira/browse/CAMEL-3488
Project: Camel
Issue Type: Improvement
Components: camel-jpa
Environment: Camel 2.6-SNAPSHOT, JPA 2, Eclipse Link 2.1, MySQL 5.1
Reporter: Marco Zapletal
Attachments: JpaTraceEventMessage-Lob-patch.txt
JpaTraceEventMessage has a bunch of String attributes defined. Applying no annotations on String attributes of an @Entity result in generated database columns with a constrained length (e.g., using EclipseLink and MySQL, a String attribute of an @Entity is mapped to a VARCHAR(255) field).
Several values of JpaTraceEventMessage are probably carrying values larger than 255 characters. Using JPAs @Lob annotation tackles this problem by generating (C)LOB fields.
The attached patch defines the @Lob annotation on attributes which are expected to carry such large values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-3488) Some of JpaTraceEventMessage's
attributes require @Lob annotation
Posted by "Marco Zapletal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Zapletal updated CAMEL-3488:
----------------------------------
Attachment: JpaTraceEventMessage-Lob-patch.txt
> Some of JpaTraceEventMessage's attributes require @Lob annotation
> -----------------------------------------------------------------
>
> Key: CAMEL-3488
> URL: https://issues.apache.org/jira/browse/CAMEL-3488
> Project: Camel
> Issue Type: Improvement
> Components: camel-jpa
> Affects Versions: 2.5.0
> Environment: Camel 2.6-SNAPSHOT, JPA 2, Eclipse Link 2.1, MySQL 5.1
> Reporter: Marco Zapletal
> Attachments: JpaTraceEventMessage-Lob-patch.txt
>
>
> JpaTraceEventMessage has a bunch of String attributes defined. Applying no annotations on String attributes of an @Entity result in generated database columns with a constrained length (e.g., using EclipseLink and MySQL, a String attribute of an @Entity is mapped to a VARCHAR(255) field).
> Several values of JpaTraceEventMessage are probably carrying values larger than 255 characters. Using JPAs @Lob annotation tackles this problem by generating (C)LOB fields.
> The attached patch defines the @Lob annotation on attributes which are expected to carry such large values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-3488) Some of JpaTraceEventMessage's
attributes require @Lob annotation
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-3488:
----------------------------------
Assignee: Claus Ibsen
> Some of JpaTraceEventMessage's attributes require @Lob annotation
> -----------------------------------------------------------------
>
> Key: CAMEL-3488
> URL: https://issues.apache.org/jira/browse/CAMEL-3488
> Project: Camel
> Issue Type: Improvement
> Components: camel-jpa
> Affects Versions: 2.5.0
> Environment: Camel 2.6-SNAPSHOT, JPA 2, Eclipse Link 2.1, MySQL 5.1
> Reporter: Marco Zapletal
> Assignee: Claus Ibsen
> Priority: Minor
> Attachments: JpaTraceEventMessage-Lob-patch.txt
>
>
> JpaTraceEventMessage has a bunch of String attributes defined. Applying no annotations on String attributes of an @Entity result in generated database columns with a constrained length (e.g., using EclipseLink and MySQL, a String attribute of an @Entity is mapped to a VARCHAR(255) field).
> Several values of JpaTraceEventMessage are probably carrying values larger than 255 characters. Using JPAs @Lob annotation tackles this problem by generating (C)LOB fields.
> The attached patch defines the @Lob annotation on attributes which are expected to carry such large values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-3488) Some of JpaTraceEventMessage's
attributes require @Lob annotation
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-3488.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.6.0
trunk: 1055348.
Thanks for the patch.
> Some of JpaTraceEventMessage's attributes require @Lob annotation
> -----------------------------------------------------------------
>
> Key: CAMEL-3488
> URL: https://issues.apache.org/jira/browse/CAMEL-3488
> Project: Camel
> Issue Type: Improvement
> Components: camel-jpa
> Affects Versions: 2.5.0
> Environment: Camel 2.6-SNAPSHOT, JPA 2, Eclipse Link 2.1, MySQL 5.1
> Reporter: Marco Zapletal
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: JpaTraceEventMessage-Lob-patch.txt
>
>
> JpaTraceEventMessage has a bunch of String attributes defined. Applying no annotations on String attributes of an @Entity result in generated database columns with a constrained length (e.g., using EclipseLink and MySQL, a String attribute of an @Entity is mapped to a VARCHAR(255) field).
> Several values of JpaTraceEventMessage are probably carrying values larger than 255 characters. Using JPAs @Lob annotation tackles this problem by generating (C)LOB fields.
> The attached patch defines the @Lob annotation on attributes which are expected to carry such large values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-3488) Some of JpaTraceEventMessage's
attributes require @Lob annotation
Posted by "Marco Zapletal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Zapletal updated CAMEL-3488:
----------------------------------
Priority: Minor (was: Major)
Affects Version/s: 2.5.0
> Some of JpaTraceEventMessage's attributes require @Lob annotation
> -----------------------------------------------------------------
>
> Key: CAMEL-3488
> URL: https://issues.apache.org/jira/browse/CAMEL-3488
> Project: Camel
> Issue Type: Improvement
> Components: camel-jpa
> Affects Versions: 2.5.0
> Environment: Camel 2.6-SNAPSHOT, JPA 2, Eclipse Link 2.1, MySQL 5.1
> Reporter: Marco Zapletal
> Priority: Minor
> Attachments: JpaTraceEventMessage-Lob-patch.txt
>
>
> JpaTraceEventMessage has a bunch of String attributes defined. Applying no annotations on String attributes of an @Entity result in generated database columns with a constrained length (e.g., using EclipseLink and MySQL, a String attribute of an @Entity is mapped to a VARCHAR(255) field).
> Several values of JpaTraceEventMessage are probably carrying values larger than 255 characters. Using JPAs @Lob annotation tackles this problem by generating (C)LOB fields.
> The attached patch defines the @Lob annotation on attributes which are expected to carry such large values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.