[JBoss JIRA] (FORGE-169) Persistence plugin should optionally add maven configuration for a meta-model generator
by Thomas Hug (JIRA)
[ https://issues.jboss.org/browse/FORGE-169?page=com.atlassian.jira.plugin.... ]
Thomas Hug commented on FORGE-169:
----------------------------------
Hey all,
Started to play around with metamodel generation and noted kind of late that there's already something in progress :-) Anyway, if you're interested, there's something around to be packed into a pull request - basically adding the Maven processor plugin with some configuration (depending on the JPA provider). Just let me know.
> Persistence plugin should optionally add maven configuration for a meta-model generator
> ---------------------------------------------------------------------------------------
>
> Key: FORGE-169
> URL: https://issues.jboss.org/browse/FORGE-169
> Project: Forge
> Issue Type: Enhancement
> Components: Java EE APIs
> Affects Versions: 1.0.6.Final
> Reporter: Paul Bakker
> Assignee: Ken Finnigan
> Fix For: 1.0.7.Final
>
>
> If JPA 2.0 is used, and the provider supports a meta-model generator it should be added to the pom file.
--
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
13 years, 7 months
[JBoss JIRA] (FORGE-572) Forge scaffold faces creates view beans with Id always Long against user-generated Entities
by Will Dinyes (JIRA)
Will Dinyes created FORGE-572:
---------------------------------
Summary: Forge scaffold faces creates view beans with Id always Long against user-generated Entities
Key: FORGE-572
URL: https://issues.jboss.org/browse/FORGE-572
Project: Forge
Issue Type: Bug
Components: Scaffold
Affects Versions: 1.0.2.Final
Environment: JBoss Developer Studio 5 Beta 2, Embedded Forge 1.0.2.Final
Reporter: Will Dinyes
Priority: Minor
When running:
scaffold from-entity ~.domain.* --overwrite
The generated view Bean will always use an id field as a long, even if the entity uses a different type for the @Id. For instance, this code, in an Entity class called ValMealtype:
@Id
@GeneratedValue(strategy=GenerationType.IDENTITY)
@Column(unique=true, nullable=false, length=20)
private String meal;
Generates, in ValMealtypeBean:
private Long id;
<-- associated gettters and setters -->
And, later in the class:
return ValMealtypeBean.this.entityManager.find(ValMealtype.class, Long.valueOf(value));
That line in particular doesn't work at all, of course, since a Long can't be parsed out of a non-numeric String. I suppose I could name my meals with hex digits . . . CAFE . . . BEEF . . . but sadly, Chicken isn't going to fly.
Basically, scaffold probably needs to look at the type of @Id in the entity and use that to set the id field type in the generated bean.
As this is reported against a non-current release, I understand it may be fixed already. In this case, a new Beta of JBDS 5 is probably in order, as that's where I'm seeing this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (FORGE-672) faces scaffold generated app breaks on ambiguity of property and method "search" when Seam Faces present
by Thomas Frühbeck (JIRA)
Thomas Frühbeck created FORGE-672:
-------------------------------------
Summary: faces scaffold generated app breaks on ambiguity of property and method "search" when Seam Faces present
Key: FORGE-672
URL: https://issues.jboss.org/browse/FORGE-672
Project: Forge
Issue Type: Bug
Components: Scaffold
Affects Versions: 1.0.6.Final
Reporter: Thomas Frühbeck
Assignee: Thomas Frühbeck
Priority: Minor
The backing beans carry the property "search" for form field based dynamic query and the method search() to invoke the selection.
After adding Seam3 Faces module to the project the application fails on "Search" because the ELResolver will take the method search() instead of the property "search" first:
Caused by: javax.el.PropertyNotFoundException: /searchTest/search.xhtml @34,90 value="#{searchTestBean.search.name}": Target Unreachable, 'search' returned null
remedy:
- rename property "search" to "example"
--
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
13 years, 7 months
[JBoss JIRA] (FORGE-664) Forge should intercept some logger messages and publish them as shell messages
by Rafael Benevides (JIRA)
Rafael Benevides created FORGE-664:
--------------------------------------
Summary: Forge should intercept some logger messages and publish them as shell messages
Key: FORGE-664
URL: https://issues.jboss.org/browse/FORGE-664
Project: Forge
Issue Type: Feature Request
Components: Brainstorming, Shell, Usability
Reporter: Rafael Benevides
I have a separate API that publishs his operations on logger messages. I wan't to reuse that API and would like that this logger messages should appear as shell messages (debug only when verbose is setted).
Forge could intercept some logger messages (on certain categoy/level) or even provide a appender so that logger messages should be printed as shell messages
--
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
13 years, 8 months