[JBoss JIRA] (FORGE-1878) Incorrect command for list on docs
by Michael Rice (JIRA)
[ https://issues.jboss.org/browse/FORGE-1878?page=com.atlassian.jira.plugin... ]
Michael Rice commented on FORGE-1878:
-------------------------------------
Thanks for taking a look. I believe you're making my point for me. I downloaded version 2.6.0.Final from the web, which is what the Forge home page tells me to download, but the instructions on the url I gave you told me to type in list-command. If you want to keep those old documents up, then we should tell the community that the commands apply to version 1x, not 2x.
> Incorrect command for list on docs
> ----------------------------------
>
> Key: FORGE-1878
> URL: https://issues.jboss.org/browse/FORGE-1878
> Project: Forge
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Reporter: Michael Rice
> Priority: Minor
>
> Hey everyone--
> I would fix this myself and submit a PR, but not sure how to do it on the github docs.
> You have an incorrect instruction on this page: http://forge.jboss.org/docs/using/
> You say that the list of commands is "list-commands" but it's actually "command-list". Seems like it's not a big deal, but it cost me 15-20 minutes to figure it out since there is not a ton of extra documentation out there on the web.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1880) Being able to add @Named to an EJBs... or any annotation anywhere
by Robert Balent (JIRA)
[ https://issues.jboss.org/browse/FORGE-1880?page=com.atlassian.jira.plugin... ]
Robert Balent reassigned FORGE-1880:
------------------------------------
Assignee: Robert Balent
> Being able to add @Named to an EJBs... or any annotation anywhere
> -----------------------------------------------------------------
>
> Key: FORGE-1880
> URL: https://issues.jboss.org/browse/FORGE-1880
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Java EE
> Affects Versions: 2.6.0.Final
> Reporter: Antonio Goncalves
> Assignee: Robert Balent
> Fix For: 2.x Future
>
>
> When I create an EJB with Forge with the following command :
> {code}
> ejb-new-bean --named MyService
> {code}
> I get the following :
> {code}
> @Stateless
> @LocalBean
> public class MyService implements Serializable
> {code}
> In some cases, I would need to add an extra {{@Named}} annotation. Several ways to do it. On the EJB command itself, we could add a parameter :
> {code}
> ejb-new-bean --named MyService --addNamed
> {code}
> But I think it would be good to have something more generic that could be used anywhere. We could use the same logic as constraint-add (that adds any kind of constraint on any Entity) and have something like
> {code}
> cdi-add-qualifier --qualifier Named --target org.app.service.MyService
> // or on a property, which could be useful
> cdi-add-qualifier --qualifier Named --onProperty myProp
> cdi-add-qualifier --qualifier Named --onMethod myMethod
> {code}
> Or something even more generic would be to use the Java command
> {code}
> java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService
> java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onProperty myProp
> java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onMethod myMethod
> java-add-annotation --annotation javax.inject.Named --onProperty myProp
> java-add-annotation --annotation javax.inject.Named --onMethod myMethod
> {code}
> _Comments on the mailing list by Ivan_
> _I think that java-add-annotation is a good command that we should have. But still it would be better to have also something more explicit for creating named beans and setting stereotypes. So, I think that the three levels of abstraction that Antonio described may be implemented. Well, at the end they will reuse one and the same code for adding annotation, so no repeating ourselves will occur._
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1879) Missing a setter in the generated JSF Backing Bean
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1879?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1879:
-----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 2.6.1.Final
(was: 2.x Future)
Resolution: Done
Merged, thanks
> Missing a setter in the generated JSF Backing Bean
> --------------------------------------------------
>
> Key: FORGE-1879
> URL: https://issues.jboss.org/browse/FORGE-1879
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Scaffold
> Affects Versions: 2.6.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Priority: Trivial
> Fix For: 2.6.1.Final
>
>
> Let's say we have a {{Publisher}} entity and we scaffold a JSF app from this entity, we end up with a backing bean that looks like that :
> {code}
> @Named
> @Stateful
> @ConversationScoped
> public class PublisherBean implements Serializable {
> private Publisher publisher;
> public Publisher getPublisher() {
> return this.publisher;
> }
> ...
> {code}
> There is no setter method on {{Publisher}}. It would be great to have one so it's easier to test a backing bean with Arquillian (we then just set the Publisher)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1879) Missing a setter in the generated JSF Backing Bean
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1879?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1879:
-----------------------------------
Priority: Trivial (was: Blocker)
> Missing a setter in the generated JSF Backing Bean
> --------------------------------------------------
>
> Key: FORGE-1879
> URL: https://issues.jboss.org/browse/FORGE-1879
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Scaffold
> Affects Versions: 2.6.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Priority: Trivial
> Fix For: 2.x Future
>
>
> Let's say we have a {{Publisher}} entity and we scaffold a JSF app from this entity, we end up with a backing bean that looks like that :
> {code}
> @Named
> @Stateful
> @ConversationScoped
> public class PublisherBean implements Serializable {
> private Publisher publisher;
> public Publisher getPublisher() {
> return this.publisher;
> }
> ...
> {code}
> There is no setter method on {{Publisher}}. It would be great to have one so it's easier to test a backing bean with Arquillian (we then just set the Publisher)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1879) Missing a setter in the generated JSF Backing Bean
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1879?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-1879:
-----------------------------------
Priority: Blocker (was: Major)
> Missing a setter in the generated JSF Backing Bean
> --------------------------------------------------
>
> Key: FORGE-1879
> URL: https://issues.jboss.org/browse/FORGE-1879
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Scaffold
> Affects Versions: 2.6.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Priority: Blocker
> Fix For: 2.x Future
>
>
> Let's say we have a {{Publisher}} entity and we scaffold a JSF app from this entity, we end up with a backing bean that looks like that :
> {code}
> @Named
> @Stateful
> @ConversationScoped
> public class PublisherBean implements Serializable {
> private Publisher publisher;
> public Publisher getPublisher() {
> return this.publisher;
> }
> ...
> {code}
> There is no setter method on {{Publisher}}. It would be great to have one so it's easier to test a backing bean with Arquillian (we then just set the Publisher)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1879) Missing a setter in the generated JSF Backing Bean
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1879?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1879:
-------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/core/pull/473
> Missing a setter in the generated JSF Backing Bean
> --------------------------------------------------
>
> Key: FORGE-1879
> URL: https://issues.jboss.org/browse/FORGE-1879
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Scaffold
> Affects Versions: 2.6.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.x Future
>
>
> Let's say we have a {{Publisher}} entity and we scaffold a JSF app from this entity, we end up with a backing bean that looks like that :
> {code}
> @Named
> @Stateful
> @ConversationScoped
> public class PublisherBean implements Serializable {
> private Publisher publisher;
> public Publisher getPublisher() {
> return this.publisher;
> }
> ...
> {code}
> There is no setter method on {{Publisher}}. It would be great to have one so it's easier to test a backing bean with Arquillian (we then just set the Publisher)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1879) Missing a setter in the generated JSF Backing Bean
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1879?page=com.atlassian.jira.plugin... ]
Antonio Goncalves reassigned FORGE-1879:
----------------------------------------
Assignee: Antonio Goncalves
> Missing a setter in the generated JSF Backing Bean
> --------------------------------------------------
>
> Key: FORGE-1879
> URL: https://issues.jboss.org/browse/FORGE-1879
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Scaffold
> Affects Versions: 2.6.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.x Future
>
>
> Let's say we have a {{Publisher}} entity and we scaffold a JSF app from this entity, we end up with a backing bean that looks like that :
> {code}
> @Named
> @Stateful
> @ConversationScoped
> public class PublisherBean implements Serializable {
> private Publisher publisher;
> public Publisher getPublisher() {
> return this.publisher;
> }
> ...
> {code}
> There is no setter method on {{Publisher}}. It would be great to have one so it's easier to test a backing bean with Arquillian (we then just set the Publisher)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1880) Being able to add @Named to an EJBs... or any annotation anywhere
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1880?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1880:
-------------------------------------
Summary: Being able to add @Named to an EJBs... or any annotation anywhere (was: Adding @Named to an EJBs... or any annotation anywhere)
> Being able to add @Named to an EJBs... or any annotation anywhere
> -----------------------------------------------------------------
>
> Key: FORGE-1880
> URL: https://issues.jboss.org/browse/FORGE-1880
> Project: Forge
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Java EE
> Affects Versions: 2.6.0.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> When I create an EJB with Forge with the following command :
> {code}
> ejb-new-bean --named MyService
> {code}
> I get the following :
> {code}
> @Stateless
> @LocalBean
> public class MyService implements Serializable
> {code}
> In some cases, I would need to add an extra {{@Named}} annotation. Several ways to do it. On the EJB command itself, we could add a parameter :
> {code}
> ejb-new-bean --named MyService --addNamed
> {code}
> But I think it would be good to have something more generic that could be used anywhere. We could use the same logic as constraint-add (that adds any kind of constraint on any Entity) and have something like
> {code}
> cdi-add-qualifier --qualifier Named --target org.app.service.MyService
> // or on a property, which could be useful
> cdi-add-qualifier --qualifier Named --onProperty myProp
> cdi-add-qualifier --qualifier Named --onMethod myMethod
> {code}
> Or something even more generic would be to use the Java command
> {code}
> java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService
> java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onProperty myProp
> java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onMethod myMethod
> java-add-annotation --annotation javax.inject.Named --onProperty myProp
> java-add-annotation --annotation javax.inject.Named --onMethod myMethod
> {code}
> _Comments on the mailing list by Ivan_
> _I think that java-add-annotation is a good command that we should have. But still it would be better to have also something more explicit for creating named beans and setting stereotypes. So, I think that the three levels of abstraction that Antonio described may be implemented. Well, at the end they will reuse one and the same code for adding annotation, so no repeating ourselves will occur._
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1880) Adding @Named to an EJBs... or any annotation anywhere
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1880:
----------------------------------------
Summary: Adding @Named to an EJBs... or any annotation anywhere
Key: FORGE-1880
URL: https://issues.jboss.org/browse/FORGE-1880
Project: Forge
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Java EE
Affects Versions: 2.6.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
When I create an EJB with Forge with the following command :
{code}
ejb-new-bean --named MyService
{code}
I get the following :
{code}
@Stateless
@LocalBean
public class MyService implements Serializable
{code}
In some cases, I would need to add an extra {{@Named}} annotation. Several ways to do it. On the EJB command itself, we could add a parameter :
{code}
ejb-new-bean --named MyService --addNamed
{code}
But I think it would be good to have something more generic that could be used anywhere. We could use the same logic as constraint-add (that adds any kind of constraint on any Entity) and have something like
{code}
cdi-add-qualifier --qualifier Named --target org.app.service.MyService
// or on a property, which could be useful
cdi-add-qualifier --qualifier Named --onProperty myProp
cdi-add-qualifier --qualifier Named --onMethod myMethod
{code}
Or something even more generic would be to use the Java command
{code}
java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService
java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onProperty myProp
java-add-annotation --annotation javax.inject.Named --target org.app.service.MyService --onMethod myMethod
java-add-annotation --annotation javax.inject.Named --onProperty myProp
java-add-annotation --annotation javax.inject.Named --onMethod myMethod
{code}
_Comments on the mailing list by Ivan_
_I think that java-add-annotation is a good command that we should have. But still it would be better to have also something more explicit for creating named beans and setting stereotypes. So, I think that the three levels of abstraction that Antonio described may be implemented. Well, at the end they will reuse one and the same code for adding annotation, so no repeating ourselves will occur._
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (FORGE-1878) Incorrect command for list on docs
by Daniel Cunha (JIRA)
[ https://issues.jboss.org/browse/FORGE-1878?page=com.atlassian.jira.plugin... ]
Daniel Cunha commented on FORGE-1878:
-------------------------------------
Hi Micael,
Do you tested forge 1.x?
command-list is Forge 2.x
In forge 1.x is list-command.
They are working in a new site. :)
> Incorrect command for list on docs
> ----------------------------------
>
> Key: FORGE-1878
> URL: https://issues.jboss.org/browse/FORGE-1878
> Project: Forge
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Reporter: Michael Rice
> Priority: Minor
>
> Hey everyone--
> I would fix this myself and submit a PR, but not sure how to do it on the github docs.
> You have an incorrect instruction on this page: http://forge.jboss.org/docs/using/
> You say that the list of commands is "list-commands" but it's actually "command-list". Seems like it's not a big deal, but it cost me 15-20 minutes to figure it out since there is not a ton of extra documentation out there on the web.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months