August 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFORGE-296) Provide a "Suggestion" or "Hints" API

by Lincoln Baxter III (JIRA)

Provide a "Suggestion" or "Hints" API ------------------------------------- Key: SEAMFORGE-296 URL: https://issues.jboss.org/browse/SEAMFORGE-296 Project: Seam Forge Issue Type: Feature Request Components: Builtin Plugins, Plugin API Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III The ability to supply a default set of, and extended interface for adding runtime hints while developers are working on applicatons. {code}scaffold setup ... "You've got a nice webapp there. But it doesn't look like you're connected to a database yet. Type 'persistence setup' to set up a datasource.{code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
6
0 / 0

[JBoss JIRA] (FORGE-617) Cannot access Stateful EJB from inner anonymous class

by Luca Masini (JIRA)

Luca Masini created FORGE-617: --------------------------------- Summary: Cannot access Stateful EJB from inner anonymous class Key: FORGE-617 URL: https://issues.jboss.org/browse/FORGE-617 Project: Forge Issue Type: Bug Components: Java EE APIs Reporter: Luca Masini -- 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

4
22
0 / 0

[JBoss JIRA] (FORGE-663) Enforce environment validations on Maven build

by George Gastaldi (JIRA)

George Gastaldi created FORGE-663: ------------------------------------- Summary: Enforce environment validations on Maven build Key: FORGE-663 URL: https://issues.jboss.org/browse/FORGE-663 Project: Forge Issue Type: Feature Request Components: Forge Build Reporter: George Gastaldi Fix For: 1.0.7.Final It sounds like the Forge build could use some validations to ensure the person building the project has an environment that matches the minimum requirements. Obviously, you want as few validations as possible (to make it more portable) but you can work to eliminate them once you know what they are. http://maven.apache.org/plugins/maven-enforcer-plugin/ Also, newer versions of Maven are suppose to be able to differentiate between origins of dependencies in the local repository, so we should probably be looking closer at the cases when we tell users to clean it out. -- 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

3
4
0 / 0

[JBoss JIRA] (FORGE-416) cascade=CascadeType.ALL added to @OneToOne mapped fields on scaffold from-entity com.cpox.model.partner.*

by Gabor Nagy (Created) (JIRA)

cascade=CascadeType.ALL added to @OneToOne mapped fields on scaffold from-entity com.cpox.model.partner.* --------------------------------------------------------------------------------------------------------- Key: FORGE-416 URL: https://issues.jboss.org/browse/FORGE-416 Project: Forge Issue Type: Bug Components: Forge Build Affects Versions: 1.0.0.Beta5 Reporter: Gabor Nagy {code:title=Address.java} @Entity public class Address implements Serializable { private static final long serialVersionUID = 1L; @Id @GeneratedValue private Long id; @Version private Integer version; ... } {code} {code:title=Partner.java} @Entity public class Partner implements Serializable { private static final long serialVersionUID = 1L; ... private @OneToOne(cascade=CascadeType.ALL) Address address4; ... } {code} One cascade=CascadeType.ALL added after each scaffolding. {code:title=Partner.java} @Entity public class Partner implements Serializable { private static final long serialVersionUID = 1L; ... private @OneToOne(cascade=CascadeType.ALL, cascade=CascadeType.ALL) Address address4; ... } {code} -- 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

6
9
0 / 0

[JBoss JIRA] (FORGE-660) Entity plugin doesn't create a new entity when entity exists on a different package

by George Gastaldi (JIRA)

George Gastaldi created FORGE-660: ------------------------------------- Summary: Entity plugin doesn't create a new entity when entity exists on a different package Key: FORGE-660 URL: https://issues.jboss.org/browse/FORGE-660 Project: Forge Issue Type: Bug Reporter: George Gastaldi Having: {code:java} [exemplo] model $ ls City.java State.java ex01/ [exemplo] model $ entity --named City --package ~.model.ex01 {code} When you create another entity with the same name on a subpackage, the City entity in subpackage ex01 is exactly the same as the one in the model package. Tested on Forge console with JBoss Tools. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-279) Add ability to generate Entity Instance classes with Persistence plugin

by Jason Porter (JIRA)

Add ability to generate Entity Instance classes with Persistence plugin ----------------------------------------------------------------------- Key: SEAMFORGE-279 URL: https://issues.jboss.org/browse/SEAMFORGE-279 Project: Seam Forge Issue Type: Enhancement Affects Versions: 1.0.0.Beta1 Reporter: Jason Porter The idea of the Entity Instance is pretty much a bunch of boiler plate code necessary to allow a JPA entity to be used by CDI and exposed to EL. See https://github.com/seam/seam-example-confbuzz/blob/develop/src/main/java/... for the basic boiler plate code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
2
0 / 0

[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

5
9
0 / 0

[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, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-328) Wrong import if imported class is a nested class

by Kevin Pollet (JIRA)

Wrong import if imported class is a nested class ------------------------------------------------ Key: SEAMFORGE-328 URL: https://issues.jboss.org/browse/SEAMFORGE-328 Project: Seam Forge Issue Type: Bug Components: Parsers / File Manipulation Affects Versions: 1.0.0.Beta2 Reporter: Kevin Pollet For example, if we have these classes {code} public class A { public static class B { } } {code} The following import is added for the class B, {{com.example.foo.A$B}} instead of {{com.example.foo.A.B}}. It's because {{AbstractJavaSource#addImport(Class<?> type)}} uses {{type.getName()}} to create the import which returns {{com.example.foo.A$B}}. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
5
0 / 0

[JBoss JIRA] (FORGE-627) Publish Roadmap and release dates to forge.jboss.org

by George Gastaldi (JIRA)

George Gastaldi created FORGE-627: ------------------------------------- Summary: Publish Roadmap and release dates to forge.jboss.org Key: FORGE-627 URL: https://issues.jboss.org/browse/FORGE-627 Project: Forge Issue Type: Enhancement Components: Documentation Reporter: George Gastaldi -- 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

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2012