[JBoss JIRA] (FORGE-2382) Add a serializable parameter to the cdi-new-bean command
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2382?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2382.
----------------------------------
Fix Version/s: 2.17.1.Final
(was: 2.x Future)
Resolution: Done
> Add a serializable parameter to the cdi-new-bean command
> --------------------------------------------------------
>
> Key: FORGE-2382
> URL: https://issues.jboss.org/browse/FORGE-2382
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.16.2.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Labels: starter
> Fix For: 2.17.1.Final
>
>
> Sometimes it's useful/mandatory to have CDI beans that are serializable. At the moment the {{cdi-new-bean}} command doesn't allow us to do that easily (except using scopes that are not always needed). A simple boolean {{isSerializable}} could do :
> {code}
> cdi-new-bean --named LoggerProducer --isSerializable
> {code}
> This would generate :
> {code}
> public class LoggerProducer implements Serializable
> {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (FORGE-2324) Being able to create Servlet Filter
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2324?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2324.
----------------------------------
Fix Version/s: 2.17.1.Final
(was: 2.x Future)
Resolution: Done
> Being able to create Servlet Filter
> -----------------------------------
>
> Key: FORGE-2324
> URL: https://issues.jboss.org/browse/FORGE-2324
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.16.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.17.1.Final
>
>
> A command such as :
> {code}
> servlet-new-filter --MyFilter
> {code}
> This would generate :
> {code}
> @WebFilter
> public class MyFilter implements Filter {
> @Override
> public void init(FilterConfig filterConfig) throws ServletException {
> }
> @Override
> public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
> }
> @Override
> public void destroy() {
> }
> }
> {code}
> This should be easier to do with [ROASTER-51]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (FORGE-2324) Being able to create Servlet Filter
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2324?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-2324:
-------------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/forge/core/pull/573
> Being able to create Servlet Filter
> -----------------------------------
>
> Key: FORGE-2324
> URL: https://issues.jboss.org/browse/FORGE-2324
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.16.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.x Future
>
>
> A command such as :
> {code}
> servlet-new-filter --MyFilter
> {code}
> This would generate :
> {code}
> @WebFilter
> public class MyFilter implements Filter {
> @Override
> public void init(FilterConfig filterConfig) throws ServletException {
> }
> @Override
> public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
> }
> @Override
> public void destroy() {
> }
> }
> {code}
> This should be easier to do with [ROASTER-51]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (FORGE-2324) Being able to create Servlet Filter
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2324?page=com.atlassian.jira.plugin... ]
Work on FORGE-2324 started by Antonio Goncalves.
------------------------------------------------
> Being able to create Servlet Filter
> -----------------------------------
>
> Key: FORGE-2324
> URL: https://issues.jboss.org/browse/FORGE-2324
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.16.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.x Future
>
>
> A command such as :
> {code}
> servlet-new-filter --MyFilter
> {code}
> This would generate :
> {code}
> @WebFilter
> public class MyFilter implements Filter {
> @Override
> public void init(FilterConfig filterConfig) throws ServletException {
> }
> @Override
> public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
> }
> @Override
> public void destroy() {
> }
> }
> {code}
> This should be easier to do with [ROASTER-51]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (FORGE-2324) Being able to create Servlet Filter
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2324?page=com.atlassian.jira.plugin... ]
Antonio Goncalves reassigned FORGE-2324:
----------------------------------------
Assignee: Antonio Goncalves
> Being able to create Servlet Filter
> -----------------------------------
>
> Key: FORGE-2324
> URL: https://issues.jboss.org/browse/FORGE-2324
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.16.0.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Fix For: 2.x Future
>
>
> A command such as :
> {code}
> servlet-new-filter --MyFilter
> {code}
> This would generate :
> {code}
> @WebFilter
> public class MyFilter implements Filter {
> @Override
> public void init(FilterConfig filterConfig) throws ServletException {
> }
> @Override
> public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
> }
> @Override
> public void destroy() {
> }
> }
> {code}
> This should be easier to do with [ROASTER-51]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (FORGE-1792) Add scopes to a the faces-new-bean command
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1792?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1792:
-------------------------------------
Description:
The command {{faces-new-bean}} should be able to add a scope. Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes)
{code}
faces-new-bean --named MyBean --scoped SESSION
{code}
This would generate the following code
{code}
@Named
@SessionScoped
public class MyBean implements Serializable {
}
{code}
For the conversation scope we could add more code :
{code}
faces-new-bean --named MyBean --scoped Conversation
{code}
This would generate the following code
{code}
@Named
@ConversationScoped
public class MyBean implements Serializable {
@Inject
private Conversation conversation;
public String begin() {
conversation.begin();
return null;
}
public String end() {
conversation.end();
return null;
}
}
{code}
was:
The command {{faces-new-bean}} should be able to add a scope. Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes)
{code}
faces-new-bean --named MyBean --scoped SESSION
{code}
This would generate the following code
{code}
@Named
@SessionScoped
public class MyBean implements Serializable {
}
{code}
For the conversation scope we could add more code :
{code}
faces-new-bean --named MyBean --scoped Conversation
{code}
This would generate the following code
{code}
@Named
@ConversationScoped
public class MyBean implements Serializable {
@Inject
private Conversation conversation;
public String begin() {
conversation.begin();
}
public String end() {
conversation.end();
}
}
{code}
> Add scopes to a the faces-new-bean command
> ------------------------------------------
>
> Key: FORGE-1792
> URL: https://issues.jboss.org/browse/FORGE-1792
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.5.0.Final
> Reporter: Antonio Goncalves
> Labels: Starter
> Fix For: 2.x Future
>
>
> The command {{faces-new-bean}} should be able to add a scope. Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes)
> {code}
> faces-new-bean --named MyBean --scoped SESSION
> {code}
> This would generate the following code
> {code}
> @Named
> @SessionScoped
> public class MyBean implements Serializable {
> }
> {code}
> For the conversation scope we could add more code :
> {code}
> faces-new-bean --named MyBean --scoped Conversation
> {code}
> This would generate the following code
> {code}
> @Named
> @ConversationScoped
> public class MyBean implements Serializable {
> @Inject
> private Conversation conversation;
> public String begin() {
> conversation.begin();
> return null;
> }
> public String end() {
> conversation.end();
> return null;
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (FORGE-1792) Add scopes to a the faces-new-bean command
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1792?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1792:
-------------------------------------
Description:
The command {{faces-new-bean}} should be able to add a scope. Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes)
{code}
faces-new-bean --named MyBean --scoped SESSION
{code}
This would generate the following code
{code}
@Named
@SessionScoped
public class MyBean implements Serializable {
}
{code}
For the conversation scope we could add more code :
{code}
faces-new-bean --named MyBean --scoped Conversation
{code}
This would generate the following code
{code}
@Named
@ConversationScoped
public class MyBean implements Serializable {
@Inject
private Conversation conversation;
public String begin() {
conversation.begin();
}
public String end() {
conversation.end();
}
}
{code}
was:
The command {{faces-new-bean}} should be able to add a scope. Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes)
{code}
faces-new-bean --named MyBean --scoped Conversation
{code}
This would generate the following code
{code}
@Named
@ConversationScoped
public class MyBean implements Serializable {
@Inject
private Conversation conversation;
public String begin() {
conversation.begin();
}
public String end() {
conversation.end();
}
}
{code}
> Add scopes to a the faces-new-bean command
> ------------------------------------------
>
> Key: FORGE-1792
> URL: https://issues.jboss.org/browse/FORGE-1792
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.5.0.Final
> Reporter: Antonio Goncalves
> Labels: Starter
> Fix For: 2.x Future
>
>
> The command {{faces-new-bean}} should be able to add a scope. Then, depending on the scope, the generated code would be different (e.g. implements Serializable for most of the other stateful scopes)
> {code}
> faces-new-bean --named MyBean --scoped SESSION
> {code}
> This would generate the following code
> {code}
> @Named
> @SessionScoped
> public class MyBean implements Serializable {
> }
> {code}
> For the conversation scope we could add more code :
> {code}
> faces-new-bean --named MyBean --scoped Conversation
> {code}
> This would generate the following code
> {code}
> @Named
> @ConversationScoped
> public class MyBean implements Serializable {
> @Inject
> private Conversation conversation;
> public String begin() {
> conversation.begin();
> }
> public String end() {
> conversation.end();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (FORGE-2374) Being able to generate an abstract or final Java class implementing serialiazable or not
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2374?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-2374:
-------------------------------------
Description:
At the moment the {{java-new-class}} only has a {{targetPackage}} and {{named}} parameter. It would be good to be able to generate abstract or final classes with serializable interfaces
{code}
$ java-new-class --named MyClass --isAbstract
public abstract class MyClass {
}
{code}
Or final :
{code}
$ java-new-class --named MyClass --isFinal
public final class MyClass {
}
{code}
What we have to be careful is that a class cannot be abstract and final. So the following is illegal :
{code}
$ java-new-class --named MyClass --isFinal --isAbstract --serializable
public final abstract class MyClass implements Serializable {
}
{code}
was:
At the moment the {{java-new-class}} only has a {{targetPackage}} and {{named}} parameter. It would be good to be able to generate abstract or final classes
{code}
$ java-new-class --named MyClass --isAbstract
public abstract class MyClass {
}
{code}
Or final :
{code}
$ java-new-class --named MyClass --isFinal
public final class MyClass {
}
{code}
What we have to be careful is that a class cannot be abstract and final. So the following is illegal :
{code}
$ java-new-class --named MyClass --isFinal --isAbstract
public final abstract class MyClass {
}
{code}
> Being able to generate an abstract or final Java class implementing serialiazable or not
> ----------------------------------------------------------------------------------------
>
> Key: FORGE-2374
> URL: https://issues.jboss.org/browse/FORGE-2374
> Project: Forge
> Issue Type: Sub-task
> Components: UI - API
> Affects Versions: 2.16.2.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> At the moment the {{java-new-class}} only has a {{targetPackage}} and {{named}} parameter. It would be good to be able to generate abstract or final classes with serializable interfaces
> {code}
> $ java-new-class --named MyClass --isAbstract
> public abstract class MyClass {
> }
> {code}
> Or final :
> {code}
> $ java-new-class --named MyClass --isFinal
> public final class MyClass {
> }
> {code}
> What we have to be careful is that a class cannot be abstract and final. So the following is illegal :
> {code}
> $ java-new-class --named MyClass --isFinal --isAbstract --serializable
> public final abstract class MyClass implements Serializable {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (FORGE-2374) Being able to generate an abstract or final Java class implementing serialiazable or not
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2374?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-2374:
-------------------------------------
Summary: Being able to generate an abstract or final Java class implementing serialiazable or not (was: Being able to generate an abstract or final Java class)
> Being able to generate an abstract or final Java class implementing serialiazable or not
> ----------------------------------------------------------------------------------------
>
> Key: FORGE-2374
> URL: https://issues.jboss.org/browse/FORGE-2374
> Project: Forge
> Issue Type: Sub-task
> Components: UI - API
> Affects Versions: 2.16.2.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> At the moment the {{java-new-class}} only has a {{targetPackage}} and {{named}} parameter. It would be good to be able to generate abstract or final classes
> {code}
> $ java-new-class --named MyClass --isAbstract
> public abstract class MyClass {
> }
> {code}
> Or final :
> {code}
> $ java-new-class --named MyClass --isFinal
> public final class MyClass {
> }
> {code}
> What we have to be careful is that a class cannot be abstract and final. So the following is illegal :
> {code}
> $ java-new-class --named MyClass --isFinal --isAbstract
> public final abstract class MyClass {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months
[JBoss JIRA] (FORGE-2382) Add a serializable parameter to the cdi-new-bean command
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2382?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-2382:
-------------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/forge/core/pull/572
> Add a serializable parameter to the cdi-new-bean command
> --------------------------------------------------------
>
> Key: FORGE-2382
> URL: https://issues.jboss.org/browse/FORGE-2382
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.16.2.Final
> Reporter: Antonio Goncalves
> Assignee: Antonio Goncalves
> Labels: starter
> Fix For: 2.x Future
>
>
> Sometimes it's useful/mandatory to have CDI beans that are serializable. At the moment the {{cdi-new-bean}} command doesn't allow us to do that easily (except using scopes that are not always needed). A simple boolean {{isSerializable}} could do :
> {code}
> cdi-new-bean --named LoggerProducer --isSerializable
> {code}
> This would generate :
> {code}
> public class LoggerProducer implements Serializable
> {
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 8 months