[JBoss JIRA] (FORGE-834) [RestPlugin] Fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created
by charles SALMON (JIRA)
[ https://issues.jboss.org/browse/FORGE-834?page=com.atlassian.jira.plugin.... ]
charles SALMON closed FORGE-834.
--------------------------------
Resolution: Done
> [RestPlugin] Fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-834
> URL: https://issues.jboss.org/browse/FORGE-834
> Project: Forge
> Issue Type: Patch
> Components: Builtin Plugins
> Reporter: charles SALMON
> Assignee: charles SALMON
> Priority: Optional
> Fix For: 1.2.3.Final
>
>
> The idea is to trigger some logic to generate javascript code when creating rest endpoint on entities.
> While it is trivial to catch the end of the "REST" command executiion by observing the CommandExecuted event, it is difficult to know exaclty which resources have been treated.
> The RestPlugin uses some logic to resolve the list of entities, but unfortunatly this list is not available through the CommandExecuted event.
> The goal here is to fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created, fired at the end of the rest command execution.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (FORGE-834) [RestPlugin] Fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created
by charles SALMON (JIRA)
[ https://issues.jboss.org/browse/FORGE-834?page=com.atlassian.jira.plugin.... ]
charles SALMON commented on FORGE-834:
--------------------------------------
I have tested it this morning and it works like a charm !
Thanks,
Charles.
> [RestPlugin] Fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-834
> URL: https://issues.jboss.org/browse/FORGE-834
> Project: Forge
> Issue Type: Patch
> Components: Builtin Plugins
> Reporter: charles SALMON
> Assignee: charles SALMON
> Priority: Optional
> Fix For: 1.2.3.Final
>
>
> The idea is to trigger some logic to generate javascript code when creating rest endpoint on entities.
> While it is trivial to catch the end of the "REST" command executiion by observing the CommandExecuted event, it is difficult to know exaclty which resources have been treated.
> The RestPlugin uses some logic to resolve the list of entities, but unfortunatly this list is not available through the CommandExecuted event.
> The goal here is to fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created, fired at the end of the rest command execution.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-835:
---------------------------------------
Of course, the behavior I described previously was tested against Hibernate 3, when the Schema was asked to be generated. Perhaps that's not needed but an additional flag won't hurt I suppose
> Forge field plugin doesn't support lobs / byte arrays
> -----------------------------------------------------
>
> Key: FORGE-835
> URL: https://issues.jboss.org/browse/FORGE-835
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 1.2.2.Final
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 1.2.3.Final
>
>
> Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
> In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
> Forge should be able to generate such fields when the command:
> {code:java}
> field lob --named <field-name>
> {code}
> is issued
> The exact name of the command (lob or bytearray or anything) is subject to discussion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-835:
---------------------------------------
lob is okay and it's similar to JPA naming standard.
I recall that some DBs (I think Derby is one of them) also needs the size of the @Column annotation to be set to Integer.MAX_VALUE
> Forge field plugin doesn't support lobs / byte arrays
> -----------------------------------------------------
>
> Key: FORGE-835
> URL: https://issues.jboss.org/browse/FORGE-835
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 1.2.2.Final
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 1.2.3.Final
>
>
> Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
> In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
> Forge should be able to generate such fields when the command:
> {code:java}
> field lob --named <field-name>
> {code}
> is issued
> The exact name of the command (lob or bytearray or anything) is subject to discussion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (FORGE-834) [RestPlugin] Fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-834?page=com.atlassian.jira.plugin.... ]
George Gastaldi commented on FORGE-834:
---------------------------------------
There is already a RestGeneratedResources class in API. I deleted the one in impl and pushed upstream.
Please, pull the master branch and test it again. It should work now.
Best Regards,
George
> [RestPlugin] Fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-834
> URL: https://issues.jboss.org/browse/FORGE-834
> Project: Forge
> Issue Type: Patch
> Components: Builtin Plugins
> Reporter: charles SALMON
> Assignee: charles SALMON
> Priority: Optional
> Fix For: 1.2.3.Final
>
>
> The idea is to trigger some logic to generate javascript code when creating rest endpoint on entities.
> While it is trivial to catch the end of the "REST" command executiion by observing the CommandExecuted event, it is difficult to know exaclty which resources have been treated.
> The RestPlugin uses some logic to resolve the list of entities, but unfortunatly this list is not available through the CommandExecuted event.
> The goal here is to fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created, fired at the end of the rest command execution.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-835:
----------------------------------
Description:
Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
Forge should be able to generate such fields when the command:
{code:java}
field lob --named <field-name>
{code}
is issued
The exact name of the command (lob or bytearray or anything) is subject to discussion.
was:
Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
Forge should be able to generate such fields when the command:
field lob --named <field-name> is issued
The exact name of the command (lob or bytearray or anything) is subject to discussion.
> Forge field plugin doesn't support lobs / byte arrays
> -----------------------------------------------------
>
> Key: FORGE-835
> URL: https://issues.jboss.org/browse/FORGE-835
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 1.2.2.Final
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 1.2.3.Final
>
>
> Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
> In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
> Forge should be able to generate such fields when the command:
> {code:java}
> field lob --named <field-name>
> {code}
> is issued
> The exact name of the command (lob or bytearray or anything) is subject to discussion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-835:
----------------------------------
Issue Type: Feature Request (was: Story)
Workflow: GIT Pull Request workflow (was: jira)
> Forge field plugin doesn't support lobs / byte arrays
> -----------------------------------------------------
>
> Key: FORGE-835
> URL: https://issues.jboss.org/browse/FORGE-835
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 1.2.2.Final
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 1.2.3.Final
>
>
> Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
> In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
> Forge should be able to generate such fields when the command:
> field lob --named <field-name> is issued
> The exact name of the command (lob or bytearray or anything) is subject to discussion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays
by Ivan St. Ivanov (JIRA)
[ https://issues.jboss.org/browse/FORGE-835?page=com.atlassian.jira.plugin.... ]
Work on FORGE-835 started by Ivan St. Ivanov.
> Forge field plugin doesn't support lobs / byte arrays
> -----------------------------------------------------
>
> Key: FORGE-835
> URL: https://issues.jboss.org/browse/FORGE-835
> Project: Forge
> Issue Type: Story
> Components: Builtin Plugins
> Affects Versions: 1.2.2.Final
> Reporter: Ivan St. Ivanov
> Assignee: Ivan St. Ivanov
> Fix For: 1.2.3.Final
>
>
> Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
> In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
> Forge should be able to generate such fields when the command:
> field lob --named <field-name> is issued
> The exact name of the command (lob or bytearray or anything) is subject to discussion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (FORGE-835) Forge field plugin doesn't support lobs / byte arrays
by Ivan St. Ivanov (JIRA)
Ivan St. Ivanov created FORGE-835:
-------------------------------------
Summary: Forge field plugin doesn't support lobs / byte arrays
Key: FORGE-835
URL: https://issues.jboss.org/browse/FORGE-835
Project: Forge
Issue Type: Story
Components: Builtin Plugins
Affects Versions: 1.2.2.Final
Reporter: Ivan St. Ivanov
Assignee: Ivan St. Ivanov
Fix For: 1.2.3.Final
Right now Forge's field plugin supports most of the common Java/JPA types as commands (string, number, date, etc.). It also supports JPA relationships (one-to-many, etc.). However, a very common scenario for a Java EE developer is to store an image or other binary object into the database.
In such situations the JPA best practices say that it should be declared as byte array field and annotated with @Lob.
Forge should be able to generate such fields when the command:
field lob --named <field-name> is issued
The exact name of the command (lob or bytearray or anything) is subject to discussion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years
[JBoss JIRA] (FORGE-834) [RestPlugin] Fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created
by charles SALMON (JIRA)
[ https://issues.jboss.org/browse/FORGE-834?page=com.atlassian.jira.plugin.... ]
charles SALMON commented on FORGE-834:
--------------------------------------
OK, that's what I thought.
I will fix the code and create a new pull request.
Thanks,
Charles.
> [RestPlugin] Fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: FORGE-834
> URL: https://issues.jboss.org/browse/FORGE-834
> Project: Forge
> Issue Type: Patch
> Components: Builtin Plugins
> Reporter: charles SALMON
> Assignee: charles SALMON
> Priority: Optional
> Fix For: 1.2.3.Final
>
>
> The idea is to trigger some logic to generate javascript code when creating rest endpoint on entities.
> While it is trivial to catch the end of the "REST" command executiion by observing the CommandExecuted event, it is difficult to know exaclty which resources have been treated.
> The RestPlugin uses some logic to resolve the list of entities, but unfortunatly this list is not available through the CommandExecuted event.
> The goal here is to fire a RestGeneratedResources event containing the resources for which a rest endpoint have been created, fired at the end of the rest command execution.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years