[JBoss JIRA] (FURNACE-70) PreShutdown events are called more than once for a single addon
by George Gastaldi (JIRA)
George Gastaldi created FURNACE-70:
--------------------------------------
Summary: PreShutdown events are called more than once for a single addon
Key: FURNACE-70
URL: https://issues.jboss.org/browse/FURNACE-70
Project: Forge: Furnace
Issue Type: Bug
Components: Container - CDI, Container - Simple, Runtime
Affects Versions: 2.20.1.Final
Reporter: George Gastaldi
Fix For: 2.x Future
I've noticed that the {{PreShutdown}} event for an addon is called more than once for the {{EventManager}} associated with that addon, but the {{PostStartup}} is not called (or called once) before this happens.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGE-1792) Add scopes to a the faces-new-bean command
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1792?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1792.
----------------------------------
Fix Version/s: 2.17.1.Final
(was: 2.x Future)
Resolution: Done
> 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
> Assignee: Antonio Goncalves
> Labels: Starter
> Fix For: 2.17.1.Final
>
>
> 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)
9 years, 4 months
[JBoss JIRA] (FORGE-2381) Being able to create a new SOAP webservice
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2381?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-2381:
-------------------------------------
Description:
It would be good to have a command to create a SOAP webservice (even if it's not fashionable, it's still heavily used ;o). A command like this :
{code}
soap-new-service --named MyWebService
{code}
Would generate
{code}
@WebService
public class MyWebService {
}
{code}
This new command should go under the {{org.jboss.forge.addon.javaee.jaxws.ui}} package.
was:
It would be good to have a command to create a SOAP webservice (even if it's not fashionable, it's still heavily used ;o). A command like this :
{code}
soap-new-service --named MyWebService
{code}
Would generate
{code}
@WebService
public class MyWebService {
}
{code}
> Being able to create a new SOAP webservice
> ------------------------------------------
>
> Key: FORGE-2381
> URL: https://issues.jboss.org/browse/FORGE-2381
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.16.2.Final
> Reporter: Antonio Goncalves
> Labels: starter
> Fix For: 2.x Future
>
>
> It would be good to have a command to create a SOAP webservice (even if it's not fashionable, it's still heavily used ;o). A command like this :
> {code}
> soap-new-service --named MyWebService
> {code}
> Would generate
> {code}
> @WebService
> public class MyWebService {
> }
> {code}
> This new command should go under the {{org.jboss.forge.addon.javaee.jaxws.ui}} package.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGE-2318) Being able to setup a logger
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2318?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-2318:
------------------------------------------
agoncal The idea is when you setup a logger, you also generate the appropriate producer method... but that means the project relies on CDI
16:35:05 gastaldi Interesting
16:35:36 gastaldi Maybe this could be a separate addon
16:35:53 agoncal gastaldi Yes, I think so
16:36:09 gastaldi We could start by creating it outside of core
16:36:09 agoncal And what about the producer method and the CDI dependency ?
16:36:24 gastaldi Roaster can generate that
16:36:51 gastaldi It should depend on javaee facet
16:36:55 agoncal yes, I know, I'm just wondering if it's a good idea to always depend on CDI
16:36:57 gastaldi CDIFacet
16:37:04 agoncal (Spring projects for example)
16:37:21 gastaldi That depends on the facets installed in the project
16:37:23 agoncal I like CDI and would love to see it used everywhere... but it's not the case yet
16:37:36 agoncal or maybe :
16:37:40 agoncal logger-setup
16:37:49 agoncal logger-new-producer
16:37:51 agoncal or
16:37:54 agoncal logger-new-factory
16:38:12 gastaldi Yeah thats a good idea too
16:38:14 agoncal One uses CDI, the other doesn't.... but is that really useful ?
16:38:37 agoncal logger-new-producer would install the CDIFacet, the other no
16:38:39 gastaldi New factory could do the same as new producer
16:38:52 agoncal ok
16:39:01 gastaldi Hm. I think that it wouldnt need to install the CDIFacet
16:39:27 gastaldi Just enable the commands if the facet is already installed should be enough
16:40:28 agoncal Hum.... When we create a backing bean, the command faces-new-bean is enabled without or without CDI... and then, it installs it
16:40:47 agoncal I think the behevior should stay the same
16:40:57 gastaldi Ah right
16:41:05 gastaldi Yeah makes sense
> Being able to setup a logger
> ----------------------------
>
> Key: FORGE-2318
> URL: https://issues.jboss.org/browse/FORGE-2318
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.16.0.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> It would be good to have a few commands to setup a logger and inject it into bean. And because logs are a pain (too many frameworks) it would help to have a {{logger-setup}} command. It will create the needed dependency (in the {{pom.xml}}) and add some basic configuration (eg. {{logback.xml}}) and why not, create a producer method so it can be injected.
> A basic logger would use JUL :
> {code}
> logger-setup
> {code}
> Or we could choose a provider and a version
> {code}
> logger-setup --provider LOG4J --version 4.1
> {code}
> The different logging frameworks are :
> * JUL (out of the box, no need to have a dependency)
> * LOG4J2 : http://logging.apache.org/log4j/2.x/
> * LOG4J1 : http://logging.apache.org/log4j/2.x/manual/migration.html
> * SLF4J : http://www.slf4j.org/
> * COMMONS_LOGGING : http://commons.apache.org/proper/commons-logging/
> * LOGBACK : http://logback.qos.ch/
> Setting up a logger would add the right dependency but also generate a producer that would look like that, and therefore could be injected :
> {code}
> public class LoggingProducer {
> @Produces
> public Logger produceLogger(InjectionPoint injectionPoint) {
> return Logger.getLogger(injectionPoint.getMember().getDeclaringClass().getName());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (FORGE-2318) Being able to setup a logger
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2318?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-2318:
-------------------------------------
Description:
It would be good to have a few commands to setup a logger and inject it into bean. And because logs are a pain (too many frameworks) it would help to have a {{logger-setup}} command. It will create the needed dependency (in the {{pom.xml}}) and add some basic configuration (eg. {{logback.xml}}) and why not, create a producer method so it can be injected.
A basic logger would use JUL :
{code}
logger-setup
{code}
Or we could choose a provider and a version
{code}
logger-setup --provider LOG4J --version 4.1
{code}
The different logging frameworks are :
* JUL (out of the box, no need to have a dependency)
* LOG4J2 : http://logging.apache.org/log4j/2.x/
* LOG4J1 : http://logging.apache.org/log4j/2.x/manual/migration.html
* SLF4J : http://www.slf4j.org/
* COMMONS_LOGGING : http://commons.apache.org/proper/commons-logging/
* LOGBACK : http://logback.qos.ch/
Setting up a logger would add the right dependency but also generate a producer that would look like that, and therefore could be injected :
{code}
public class LoggingProducer {
@Produces
public Logger produceLogger(InjectionPoint injectionPoint) {
return Logger.getLogger(injectionPoint.getMember().getDeclaringClass().getName());
}
}
{code}
was:
It would be good to have a few commands to setup a logger and inject it into bean. And because logs are a pain (too many frameworks) it would help to have a {{logger-setup}} command. It will create the needed dependency (in the {{pom.xml}}) and add some basic configuration (eg. {{logback.xml}}).
A basic logger would use JUL :
{code}
logger-setup
{code}
Or we could chosse a provider
{code}
logger-setup --provider LOG4J
{code}
> Being able to setup a logger
> ----------------------------
>
> Key: FORGE-2318
> URL: https://issues.jboss.org/browse/FORGE-2318
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Affects Versions: 2.16.0.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> It would be good to have a few commands to setup a logger and inject it into bean. And because logs are a pain (too many frameworks) it would help to have a {{logger-setup}} command. It will create the needed dependency (in the {{pom.xml}}) and add some basic configuration (eg. {{logback.xml}}) and why not, create a producer method so it can be injected.
> A basic logger would use JUL :
> {code}
> logger-setup
> {code}
> Or we could choose a provider and a version
> {code}
> logger-setup --provider LOG4J --version 4.1
> {code}
> The different logging frameworks are :
> * JUL (out of the box, no need to have a dependency)
> * LOG4J2 : http://logging.apache.org/log4j/2.x/
> * LOG4J1 : http://logging.apache.org/log4j/2.x/manual/migration.html
> * SLF4J : http://www.slf4j.org/
> * COMMONS_LOGGING : http://commons.apache.org/proper/commons-logging/
> * LOGBACK : http://logback.qos.ch/
> Setting up a logger would add the right dependency but also generate a producer that would look like that, and therefore could be injected :
> {code}
> public class LoggingProducer {
> @Produces
> public Logger produceLogger(InjectionPoint injectionPoint) {
> return Logger.getLogger(injectionPoint.getMember().getDeclaringClass().getName());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 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... ]
Issue was automatically transitioned when Antonio Goncalves created pull request #579 in GitHub
-----------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Coding In Progress)
> 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
> Assignee: 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)
9 years, 4 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... ]
Work on FORGE-1792 started by Antonio Goncalves.
------------------------------------------------
> 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
> Assignee: 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)
9 years, 4 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 reassigned FORGE-1792:
----------------------------------------
Assignee: Antonio Goncalves
> 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
> Assignee: 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)
9 years, 4 months
[JBoss JIRA] (FORGE-1944) Create Junit commands
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1944?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1944:
------------------------------------------
And what about an abstraction like the one we have with building (Maven or Gradle) ? Instead of {{junit-}} commands we could have something more abstract, such as {{test-}} and let us choose between Junit and TestNG. The Arquillian addon does that :
{code}
// Sets up a test framework
test-setup --testFramework JUnit / TestNG --version
// Creates a new test case
test-new-test --named TheClassNameTest
// Adds a new test to a test case
test-add-test --named theMethodName --targetClass TheClassNameTes
// Generates a test case for a given class (generates one test per public method)
test-create-test --targets TheClassToGenerateTests
...
{code}
> Create Junit commands
> ---------------------
>
> Key: FORGE-1944
> URL: https://issues.jboss.org/browse/FORGE-1944
> Project: Forge
> Issue Type: Feature Request
> Components: Developer Tools - Java
> Affects Versions: 2.7.0.Final
> Reporter: George Gastaldi
> Assignee: Ivan St. Ivanov
> Labels: Starter
> Fix For: 2.x Future
>
>
> Create a command to create a JUnit test case and setup Junit in a project
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months