[JBoss JIRA] (FORGE-1192) Ill behaved addons can screw up the command popup in Eclipse
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/FORGE-1192?page=com.atlassian.jira.plugin... ]
Koen Aers updated FORGE-1192:
-----------------------------
Description:
- Create a test addon with a command that e.g. uses PersistenceFacet
- Include javaee-api in the implementation pom.xml so everything compiles
- Don't include the javaee addon in the addon pom.xml
- Install the test addon
- Try bringing up the command popup using Cmd+5
=> It doesn't come up because of a ClassNotFoundException
> Ill behaved addons can screw up the command popup in Eclipse
> ------------------------------------------------------------
>
> Key: FORGE-1192
> URL: https://issues.jboss.org/browse/FORGE-1192
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Eclipse
> Affects Versions: 2.0.0.Alpha12
> Reporter: Koen Aers
>
> - Create a test addon with a command that e.g. uses PersistenceFacet
> - Include javaee-api in the implementation pom.xml so everything compiles
> - Don't include the javaee addon in the addon pom.xml
> - Install the test addon
> - Try bringing up the command popup using Cmd+5
> => It doesn't come up because of a ClassNotFoundException
--
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
12 years, 6 months
[JBoss JIRA] (FORGE-1191) Template title has wrong EL
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1191?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1191:
------------------------------------------
Works perfectly ;o)
Can't wait for 1.4.1 ;o)
> Template title has wrong EL
> ---------------------------
>
> Key: FORGE-1191
> URL: https://issues.jboss.org/browse/FORGE-1191
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.4.0.Final
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 1.4.1.Final
>
>
> Hi,
> The generate {{pageTemplate.xhtml}} has the following expression :
> {code}
> <title>#{empty pageTitle ? '{#pageTitle}' : pageTitle}</title>
> {code}
> This doesn't work anymore with GlassFish 4.0.1-b03 because it says the expression is incorrect. Indeed, Intellij IDEA reports a bug in the expression. The following works, but I'm not sure it's exactly what Forge wants to do :
> {code}
> <title>#{empty pageTitle ? '#pageTitle' : pageTitle}</title>
> {code}
> PS : I actually thought the right syntax was the following... but it's not (getting lost in the EL + JSF maze)
> {code}
> <title>#{empty pageTitle ? '#{pageTitle}' : pageTitle}</title>
> {code}
--
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
12 years, 6 months
[JBoss JIRA] (FORGE-1191) Template title has wrong EL
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1191?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1191.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 1.4.1.Final
Resolution: Done
Changed to
{code}
<title>#{empty pageTitle ? 'Page Title' : pageTitle}</title>
{code}
> Template title has wrong EL
> ---------------------------
>
> Key: FORGE-1191
> URL: https://issues.jboss.org/browse/FORGE-1191
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.4.0.Final
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 1.4.1.Final
>
>
> Hi,
> The generate {{pageTemplate.xhtml}} has the following expression :
> {code}
> <title>#{empty pageTitle ? '{#pageTitle}' : pageTitle}</title>
> {code}
> This doesn't work anymore with GlassFish 4.0.1-b03 because it says the expression is incorrect. Indeed, Intellij IDEA reports a bug in the expression. The following works, but I'm not sure it's exactly what Forge wants to do :
> {code}
> <title>#{empty pageTitle ? '#pageTitle' : pageTitle}</title>
> {code}
> PS : I actually thought the right syntax was the following... but it's not (getting lost in the EL + JSF maze)
> {code}
> <title>#{empty pageTitle ? '#{pageTitle}' : pageTitle}</title>
> {code}
--
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
12 years, 6 months
[JBoss JIRA] (FORGE-1191) Template title has wrong EL
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1191?page=com.atlassian.jira.plugin... ]
George Gastaldi edited comment on FORGE-1191 at 9/11/13 1:06 PM:
-----------------------------------------------------------------
I think it could be:
{code}<title>#{empty pageTitle ? 'Page Title' : pageTitle}</title>{code}
was (Author: gastaldi):
I think it could be:
{code}
<title>#{empty pageTitle ? 'Page Title' : pageTitle}</title>
{code}
> Template title has wrong EL
> ---------------------------
>
> Key: FORGE-1191
> URL: https://issues.jboss.org/browse/FORGE-1191
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.4.0.Final
> Reporter: Antonio Goncalves
>
> Hi,
> The generate {{pageTemplate.xhtml}} has the following expression :
> {code}
> <title>#{empty pageTitle ? '{#pageTitle}' : pageTitle}</title>
> {code}
> This doesn't work anymore with GlassFish 4.0.1-b03 because it says the expression is incorrect. Indeed, Intellij IDEA reports a bug in the expression. The following works, but I'm not sure it's exactly what Forge wants to do :
> {code}
> <title>#{empty pageTitle ? '#pageTitle' : pageTitle}</title>
> {code}
> PS : I actually thought the right syntax was the following... but it's not (getting lost in the EL + JSF maze)
> {code}
> <title>#{empty pageTitle ? '#{pageTitle}' : pageTitle}</title>
> {code}
--
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
12 years, 6 months
[JBoss JIRA] (FORGE-1191) Template title has wrong EL
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1191?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1191:
----------------------------------------
I think it could be:
{code}
<title>#{empty pageTitle ? 'Page Title' : pageTitle}</title>
{code}
> Template title has wrong EL
> ---------------------------
>
> Key: FORGE-1191
> URL: https://issues.jboss.org/browse/FORGE-1191
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.4.0.Final
> Reporter: Antonio Goncalves
>
> Hi,
> The generate {{pageTemplate.xhtml}} has the following expression :
> {code}
> <title>#{empty pageTitle ? '{#pageTitle}' : pageTitle}</title>
> {code}
> This doesn't work anymore with GlassFish 4.0.1-b03 because it says the expression is incorrect. Indeed, Intellij IDEA reports a bug in the expression. The following works, but I'm not sure it's exactly what Forge wants to do :
> {code}
> <title>#{empty pageTitle ? '#pageTitle' : pageTitle}</title>
> {code}
> PS : I actually thought the right syntax was the following... but it's not (getting lost in the EL + JSF maze)
> {code}
> <title>#{empty pageTitle ? '#{pageTitle}' : pageTitle}</title>
> {code}
--
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
12 years, 6 months
[JBoss JIRA] (FORGE-1191) Template title has wrong EL
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1191:
----------------------------------------
Summary: Template title has wrong EL
Key: FORGE-1191
URL: https://issues.jboss.org/browse/FORGE-1191
Project: Forge
Issue Type: Bug
Affects Versions: 1.4.0.Final
Reporter: Antonio Goncalves
Hi,
The generate {{pageTemplate.xhtml}} has the following expression :
{code}
<title>#{empty pageTitle ? '{#pageTitle}' : pageTitle}</title>
{code}
This doesn't work anymore with GlassFish 4.0.1-b03 because it says the expression is incorrect. Indeed, Intellij IDEA reports a bug in the expression. The following works, but I'm not sure it's exactly what Forge wants to do :
{code}
<title>#{empty pageTitle ? '#pageTitle' : pageTitle}</title>
{code}
PS : I actually thought the right syntax was the following... but it's not (getting lost in the EL + JSF maze)
{code}
<title>#{empty pageTitle ? '#{pageTitle}' : pageTitle}</title>
{code}
--
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
12 years, 6 months
[JBoss JIRA] (FORGE-1164) `project remove-managed-dependency` does not remove managed dependency
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1164?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1164:
------------------------------------------
This is not vital, I can always do stuff manually. I'm trying to automate migrating from Java EE 6 to 7 but some tasks can be manual. If you find it for 1.4.1 just before JavaOne, good ;o) if not, it's not a big issue.
> `project remove-managed-dependency` does not remove managed dependency
> ----------------------------------------------------------------------
>
> Key: FORGE-1164
> URL: https://issues.jboss.org/browse/FORGE-1164
> Project: Forge
> Issue Type: Bug
> Affects Versions: 1.4.0.Final
> Reporter: Antonio Goncalves
> Fix For: 1.x Future
>
>
> I want to turn a Forge project from being Java EE 6 to Java EE 7 centric. One of these tasks is to change the dependencies in the {{pom.xml}}. So I add the {{javax:javaee-api:7.0}} to the pom and list the managed dependencies :
> {code}
> $ project list-managed-dependencies
> org.jboss.spec : jboss-javaee-6.0 : 3.0.2.Final : pom : import
> org.hibernate : hibernate-validator : 5.1.0.Alpha1 : jar : provided
> javax : javaee-api : 7.0 : jar : provided
> {code}
> If I remove the added {{javax:javaee-api:7.0}}, it works. But if I want to remove the {{org.jboss.spec:jboss-javaee-6.0}}, the console says it doesn't exist :
> {code}
> $ project remove-managed-dependency org.jboss.spec:jboss-javaee-6.0
> Managed dependency [org.jboss.spec:jboss-javaee-6.0:::] not found in project...
> {code}
> I even tried adding version, scope and so on, but it doesn't work :
> {code}
> $ project remove-managed-dependency
> ? [[ groupId :artifactId {:version :scope :packaging} ] (of type org.jboss.forge.project.dependencies.Dependency)]: org.jboss.spec:jboss-javaee-6.0:3.0.2.Final:pom:import
> Managed dependency [org.jboss.spec:jboss-javaee-6.0:import::3.0.2.Final] not found in project...
> {code}
> PS : same occur in Forge 1.3.3-Final
--
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
12 years, 6 months
[JBoss JIRA] (FORGE-1061) REST plugin should support user-driven mapping of DTOs to JPA entities
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1061?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1061:
-----------------------------------
Fix Version/s: 2.x Future
> REST plugin should support user-driven mapping of DTOs to JPA entities
> ----------------------------------------------------------------------
>
> Key: FORGE-1061
> URL: https://issues.jboss.org/browse/FORGE-1061
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 1.3.3.Final
> Reporter: Vineet Reynolds
> Fix For: 2.x Future
>
>
> This is to extend the work done in FORGE-1060 which is scoped to generate DTOs in a pre-determined manner for JPA entities. We should be able to support user-driven mapping of the JPA entities to create the DTOs first, and then generate the appropriate business services that would update the underlying entities in the database.
> Doing so would allow the REST resources to function in a similar manner to the [REST workflow pattern|http://www.infoq.com/articles/webber-rest-workflow]. This would improve the transactional behavior of the resources, since the constructed DTOs could house all related entities that participate in a business transaction. Since metadata of business transactions is not available in the object model, the mapping process to derive the DTOs will be user-driven.
> Not doing so would yield REST resources that are just representations of database tables, thus requiring associations to be established for entities that participate in a business transaction.
--
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
12 years, 6 months