[JBoss JIRA] (FORGE-2401) Introduce a ForgeScriptFileResource
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2401:
--------------------------------------
Summary: Introduce a ForgeScriptFileResource
Key: FORGE-2401
URL: https://issues.jboss.org/browse/FORGE-2401
Project: Forge
Issue Type: Feature Request
Components: Resources, Script
Affects Versions: 2.17.0.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.17.1.Final
It would be nice to have a {{ForgeScriptFileResource}} for .fsh files with a {{run()}} method to execute.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (FORGE-2400) Introduce script module
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2400:
--------------------------------------
Summary: Introduce script module
Key: FORGE-2400
URL: https://issues.jboss.org/browse/FORGE-2400
Project: Forge
Issue Type: Feature Request
Components: Script
Affects Versions: 2.17.0.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.x Future
The script module should provide a {{javax.script}} implementation in order to allow execution of Forge scripts
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (FORGE-2399) Test
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2399:
--------------------------------------
Summary: Test
Key: FORGE-2399
URL: https://issues.jboss.org/browse/FORGE-2399
Project: Forge
Issue Type: Quality Risk
Environment:
*Location*: http://forge.jboss.org/
*User-Agent*: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
*Screen Resolution*: 1920 x 1080
Reporter: George Gastaldi
This is a test, opened from the Forge website
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (FORGE-2398) Rework the web.xml support in javaee-descriptor project
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2398?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2398.
----------------------------------
Fix Version/s: 2.17.1.Final
(was: 2.x Future)
Resolution: Done
Implemented in javaee-descriptors 0.0.6
> Rework the web.xml support in javaee-descriptor project
> -------------------------------------------------------
>
> Key: FORGE-2398
> URL: https://issues.jboss.org/browse/FORGE-2398
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Reporter: Ivan St. Ivanov
> Assignee: George Gastaldi
> Fix For: 2.17.1.Final
>
>
> If a Forge class needs to work with web.xml, then the best way to do that is via the classes in the org.jboss.shrinkwrap.descriptor.api.webapp* packages coming from the org.jboss.forge.descriptors:javaee-descriptors-api artifact.
> There is one Servlet spec independent package there org.jboss.shrinkwrap.descriptor.api.webapp and few others for every other version of the speck: org.jboss.shrinkwrap.descriptor.api.webapp25, org.jboss.shrinkwrap.descriptor.api.webapp30 and org.jboss.shrinkwrap.descriptor.api.webapp31. The thing is that the common package does not provide much capabilities and the users of this API should go to the release specific classes. Which leads to a lot of code duplication and defining otherwise common abstractions (like a security constraint for example) in the client code instead of using the one from the API.
> The purpose of this task is to come up with a proposal and finally implement a refactoring of the API so that much more functionality is abstracted away from the webappXX packages into the common one
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (FORGE-2398) Rework the web.xml support in javaee-descriptor project
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2398?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-2398:
--------------------------------------
Assignee: George Gastaldi
> Rework the web.xml support in javaee-descriptor project
> -------------------------------------------------------
>
> Key: FORGE-2398
> URL: https://issues.jboss.org/browse/FORGE-2398
> Project: Forge
> Issue Type: Sub-task
> Components: Java EE
> Reporter: Ivan St. Ivanov
> Assignee: George Gastaldi
> Fix For: 2.x Future
>
>
> If a Forge class needs to work with web.xml, then the best way to do that is via the classes in the org.jboss.shrinkwrap.descriptor.api.webapp* packages coming from the org.jboss.forge.descriptors:javaee-descriptors-api artifact.
> There is one Servlet spec independent package there org.jboss.shrinkwrap.descriptor.api.webapp and few others for every other version of the speck: org.jboss.shrinkwrap.descriptor.api.webapp25, org.jboss.shrinkwrap.descriptor.api.webapp30 and org.jboss.shrinkwrap.descriptor.api.webapp31. The thing is that the common package does not provide much capabilities and the users of this API should go to the release specific classes. Which leads to a lot of code duplication and defining otherwise common abstractions (like a security constraint for example) in the client code instead of using the one from the API.
> The purpose of this task is to come up with a proposal and finally implement a refactoring of the API so that much more functionality is abstracted away from the webappXX packages into the common one
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (FORGE-2398) Rework the web.xml support in javaee-descriptor project
by Ivan St. Ivanov (JIRA)
Ivan St. Ivanov created FORGE-2398:
--------------------------------------
Summary: Rework the web.xml support in javaee-descriptor project
Key: FORGE-2398
URL: https://issues.jboss.org/browse/FORGE-2398
Project: Forge
Issue Type: Sub-task
Reporter: Ivan St. Ivanov
If a Forge class needs to work with web.xml, then the best way to do that is via the classes in the org.jboss.shrinkwrap.descriptor.api.webapp* packages coming from the org.jboss.forge.descriptors:javaee-descriptors-api artifact.
There is one Servlet spec independent package there org.jboss.shrinkwrap.descriptor.api.webapp and few others for every other version of the speck: org.jboss.shrinkwrap.descriptor.api.webapp25, org.jboss.shrinkwrap.descriptor.api.webapp30 and org.jboss.shrinkwrap.descriptor.api.webapp31. The thing is that the common package does not provide much capabilities and the users of this API should go to the release specific classes. Which leads to a lot of code duplication and defining otherwise common abstractions (like a security constraint for example) in the client code instead of using the one from the API.
The purpose of this task is to come up with a proposal and finally implement a refactoring of the API so that much more functionality is abstracted away from the webappXX packages into the common one
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (FORGE-2397) Being able to create new Websocket Server endpoints
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-2397?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-2397:
-------------------------------------
Labels: starter (was: )
> Being able to create new Websocket Server endpoints
> ---------------------------------------------------
>
> Key: FORGE-2397
> URL: https://issues.jboss.org/browse/FORGE-2397
> 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 be able to create a Websocket Server endpoint with the following command :
> {code}
> websocket-new-server-endpoint --name MyServerEndpoint
> {code}
> This would generate the following code with the default URI {{myServer}}:
> {code}
> @ServerEndpoint("/myServer")
> public class MyServerEndpoint {
> }
> {code}
> A {{uri}} parameter would allow to customize the URI of the endpoint
> {code}
> websocket-new-server-endpoint --name MyServerEndpoint --uri abc
> {code}
> This would generate the following code with a {{abc}} URI:
> {code}
> @ServerEndpoint("/abc")
> public class MyServerEndpoint {
> }
> {code}
> As a shortcut (see [FORGE-2394] we could easily implement basic methods such as :
> {code}
> websocket-new-server-endpoint --name MyServerEndpoint --uri abc --methods ON_OPEN ON_CLOSE ON_ERROR ON_MESSAGE
> {code}
> This would generate a server endpoint with the four following methods :
> {code}
> @ServerEndpoint("/abc")
> public class MyServerEndpoint {
> @OnOpen
> public void onOpen(Session session) {
> }
> @OnClose
> public void onClose(CloseReason closeReason) {
> }
> @OnMessage
> public void onMessage(String message, Session session) {
> }
>
> @OnError
> public void onError(Throwable t) {
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months