July 2015 - forge-issues - Jboss List Archives

[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... ] Work on FORGE-2382 started by Antonio Goncalves. ------------------------------------------------ > 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, 9 months

1
0
0 / 0

[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: ------------------------------------- Summary: Add a serializable parameter to the cdi-new-bean command (was: Add a isSerializable parameter to the cdi-new-bean command) > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2382) Add a isSerializable 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 reassigned FORGE-2382: ---------------------------------------- Assignee: Antonio Goncalves > Add a isSerializable 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2417) Being able to add a datasource definition

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2417: ---------------------------------------- Summary: Being able to add a datasource definition Key: FORGE-2417 URL: https://issues.jboss.org/browse/FORGE-2417 Project: Forge Issue Type: Sub-task Components: Java EE Affects Versions: 2.17.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future It would be good to have a command to quickly add a new {{DatasourceDefinition}} : {code} jpa-add-datasource-definition --named java:global/MyApp/myDS --className org.apache.derby.jdbc.ClientDataSource --port 1527 --server localhost -dbName testDB --user scott --password tiger {code} This will create a new class called {{org.myproject.DatasourceResources}} if it doesn't exist, and will add a new {{DatasourceDefinition}} : {code} package org.myproject; @DatasourceDefinitions({ @DatasourceDefinition( name = "java:global/MyApp/myDS", className = "org.apache.derby.jdbc.ClientDataSource", portNumber = 1527, serverName = "localhost", databaseName = "testDB", user = "lance", password = "secret" ) }) public class DatasourceResources { } {code} Tying the command a second time will add a new {{DatasourceDefinition}} to the exiting {{DatasourceDefinitions}} : {code} package org.myproject; package org.myproject; @DatasourceDefinitions({ @DatasourceDefinition( name = "java:global/MyApp/myDS", className = "org.apache.derby.jdbc.ClientDataSource", portNumber = 1527, serverName = "localhost", databaseName = "testDB", user = "lance", password = "secret" ), @DatasourceDefinition( ... ) }) public class DatasourceResources { } {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-552) Escaping of selected characters doesn't work

by Andrea Cosentino (JIRA)

[ https://issues.jboss.org/browse/FORGE-552?page=com.atlassian.jira.plugin.... ] Andrea Cosentino commented on FORGE-552: ---------------------------------------- Hi, It seems the problem still exists for & character. I'm experiencing this using UISelectOne class. Whenever I select a string with & inside it, the getValue() on the class returns the string truncated to the first occurence of &. > Escaping of selected characters doesn't work > -------------------------------------------- > > Key: FORGE-552 > URL: https://issues.jboss.org/browse/FORGE-552 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 1.0.2.Final > Environment: Ubuntu 10.04 i686 > Reporter: Jevgeni Zelenkov > Fix For: 2.0.0.Alpha14 > > > This is related to the https://issues.jboss.org/browse/FORGE-43 issue. > The following characters in file names should be escaped by the forge completion: > \* ? = ' " { } \ $ ! & ; ( ) < > | > also: TAB-char (yes, I know it is stupid, but possible) > First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped. > = char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu). > Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested): > ' " = & | ( ) < > ^ > This issue is added for completeness. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-552) Escaping of selected characters doesn't work

by Andrea Cosentino (JIRA)

[ https://issues.jboss.org/browse/FORGE-552?page=com.atlassian.jira.plugin.... ] Andrea Cosentino reopened FORGE-552: ------------------------------------ > Escaping of selected characters doesn't work > -------------------------------------------- > > Key: FORGE-552 > URL: https://issues.jboss.org/browse/FORGE-552 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 1.0.2.Final > Environment: Ubuntu 10.04 i686 > Reporter: Jevgeni Zelenkov > Fix For: 2.0.0.Alpha14 > > > This is related to the https://issues.jboss.org/browse/FORGE-43 issue. > The following characters in file names should be escaped by the forge completion: > \* ? = ' " { } \ $ ! & ; ( ) < > | > also: TAB-char (yes, I know it is stupid, but possible) > First two (*, ?) are used internally as wildcard chars, so should be allowed to be used escaped as well as unescaped. > = char doesn't need to be escaped neither on linux nor on windows but somehow forge fails to work with files containing = (at least on my ubuntu). > Windows has a slightly different set of chars to be escaped (from wikipedia, not actually tested): > ' " = & | ( ) < > ^ > This issue is added for completeness. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2413) websocket-setup command should also have 1.1 version

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2413?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2413. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.17.1.Final (was: 2.x Future) Resolution: Done > websocket-setup command should also have 1.1 version > ---------------------------------------------------- > > Key: FORGE-2413 > URL: https://issues.jboss.org/browse/FORGE-2413 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.17.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Labels: Starter > Fix For: 2.17.1.Final > > > At the moment, when setting up websocket, TAB completion only gives 1.0 version. 1.1 should also be available : > {code} > websocket-setup --webSocketVersion 1.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2415) Being able to add a JMS connection factory definition

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2415?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2415: ------------------------------------- Labels: Starter (was: ) > Being able to add a JMS connection factory definition > ------------------------------------------------------ > > Key: FORGE-2415 > URL: https://issues.jboss.org/browse/FORGE-2415 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.17.0.Final > Reporter: Antonio Goncalves > Labels: Starter > Fix For: 2.x Future > > > It would be good to have a command to quickly add a new {{JMSConnectionFactoryDefinition}} to allow sending messages : > {code} > jms-add-connection-factory-definition --named myFactory --resourceAdapter jmsra > {code} > This will create a new class called {{org.myproject.jms.MessageResources}} if it doesn't exist, and will add a new {{JMSConnectionFactoryDefinition}} : > {code} > package org.myproject.jms; > @JMSConnectionFactoryDefinitions({ > @JMSConnectionFactoryDefinition( > name = "myFactory", > interfaceName = "jmsra" > ) > }) > public class MessageResources { > } > {code} > Tying the command a second time will add a new {{JMSConnectionFactoryDefinition}} to the exiting {{JMSConnectionFactoryDefinitions}} : > @JMSConnectionFactoryDefinitions({ > @JMSConnectionFactoryDefinition( > name = "myFactory", > interfaceName = "jmsra" > ), > @JMSConnectionFactoryDefinition( > ... > ) > }) > public class MessageResources { > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2416) Being able to send JMS messages

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2416?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2416: ------------------------------------- Labels: Starter (was: ) > Being able to send JMS messages > ------------------------------- > > Key: FORGE-2416 > URL: https://issues.jboss.org/browse/FORGE-2416 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.17.0.Final > Reporter: Antonio Goncalves > Labels: Starter > Fix For: 2.x Future > > > It would be good to have a command to quickly add code to allow sending JMS messages. The following command would create the needed code using a message of type String : > {code} > jms-add-send-message-method --named sendMessage --destinationType QUEUE --destinationName myQueue > {code} > This would inject the {{javax.jms.JMSContext}} and add a method to send JMS message : > {code} > @Inject > JMSContext context; > @Resource(mappedName = "myQueue") > Queue queue; > public void sendMessage(String message) { > context.createProducer().send(queue, message); > } > {code} > To customize the message type, we just use the {{type}} parameter : > {code} > jms-add-send-message-method --named sendMessage --type MyBean --destinationType QUEUE --destinationName myQueue > {code} > We will get the following code : > {code} > @Inject > JMSContext context; > @Resource(mappedName = "myQueue") > Queue queue; > public void sendMessage(MyBean message) { > context.createProducer().send(queue, message); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2413) websocket-setup command should also have 1.1 version

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2413?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2413: ------------------------------------- Labels: Starter (was: ) > websocket-setup command should also have 1.1 version > ---------------------------------------------------- > > Key: FORGE-2413 > URL: https://issues.jboss.org/browse/FORGE-2413 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.17.0.Final > Reporter: Antonio Goncalves > Labels: Starter > Fix For: 2.x Future > > > At the moment, when setting up websocket, TAB completion only gives 1.0 version. 1.1 should also be available : > {code} > websocket-setup --webSocketVersion 1.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2015