March 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-822) Proxy settings utility for plugin writers

by Ivan St. Ivanov (JIRA)

Ivan St. Ivanov created FORGE-822: ------------------------------------- Summary: Proxy settings utility for plugin writers Key: FORGE-822 URL: https://issues.jboss.org/browse/FORGE-822 Project: Forge Issue Type: Enhancement Components: Shell Affects Versions: 1.2.3.Final Reporter: Ivan St. Ivanov Assignee: Ivan St. Ivanov Fix For: 1.2.3.Final There is a utility class that the built-in plugins may use to read the proxy information from the Forge user configuration. This is the org.jboss.forge.shell.util.ProxySettgins class, which is part of the forge-shell project. However, the plugins that are not part of that module do not have access at runtime to this utility class. So if they need information about the HTTP proxy, the plugin writers have to know all the details how these are set in the ~/.forge/config.xml file. The solution is to move the ProxySettings class to the same package, but in the forge-shell-api project. The latter can be safely accessed by the plugins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-821) Plugin to secure application

by George Gastaldi (JIRA)

George Gastaldi created FORGE-821: ------------------------------------- Summary: Plugin to secure application Key: FORGE-821 URL: https://issues.jboss.org/browse/FORGE-821 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.2.2.Final Reporter: George Gastaldi Fix For: 1.2.3.Final The plugin should primarily: - Add a <security-constraint> entry to the web.xml file. - Introduce a SecurityFacet for interoperability with other plugins - The ScaffoldPlugin could create entries for the login and login-error pages if the SecurityFacet is enabled in the current project -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-820) No XPathFactory implementation found inside a forge addon

by George Gastaldi (JIRA)

George Gastaldi created FORGE-820: ------------------------------------- Summary: No XPathFactory implementation found inside a forge addon Key: FORGE-820 URL: https://issues.jboss.org/browse/FORGE-820 Project: Forge Issue Type: Bug Components: Container Affects Versions: 2.0.0.Alpha1 Reporter: George Gastaldi Fix For: 2.0.0.Alpha1 The following test fails: {code:java} @RunWith(Arquillian.class) public class XPathContainerTest { @Deployment public static ForgeArchive getDeployment() { ForgeArchive archive = ShrinkWrap.create(ForgeArchive.class) .addClasses(XPathContainerTest.class) .addBeansXML(); return archive; } @Test public void testContainerStartup() { Assert.assertNotNull(XPathFactory.newInstance().newXPath()); } } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-819) JPAProvider should be pluggable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-819?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-819: ---------------------------------- Description: JPAProvider should be pluggable, allowing plugins to provide a new container without changing the core. The enum should be still be used though (deprecated perhaps), since some external plugins may still be using it. was: JPAContainer should be pluggable, allowing plugins to provide a new container without changing the core. The enum should be still be used though (deprecated perhaps), since some external plugins may still be using it. > JPAProvider should be pluggable > ------------------------------- > > Key: FORGE-819 > URL: https://issues.jboss.org/browse/FORGE-819 > Project: Forge > Issue Type: Enhancement > Components: Java EE APIs > Affects Versions: 1.2.2.Final > Reporter: George Gastaldi > Fix For: 1.2.3.Final > > > JPAProvider should be pluggable, allowing plugins to provide a new container without changing the core. > The enum should be still be used though (deprecated perhaps), since some external plugins may still be using it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-819) JPAProvider should be pluggable

by George Gastaldi (JIRA)

George Gastaldi created FORGE-819: ------------------------------------- Summary: JPAProvider should be pluggable Key: FORGE-819 URL: https://issues.jboss.org/browse/FORGE-819 Project: Forge Issue Type: Enhancement Components: Java EE APIs Affects Versions: 1.2.2.Final Reporter: George Gastaldi Fix For: 1.2.3.Final JPAContainer should be pluggable, allowing plugins to provide a new container without changing the core. The enum should be still be used though (deprecated perhaps), since some external plugins may still be using it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-818) JPAContainer should be pluggable

by George Gastaldi (JIRA)

George Gastaldi created FORGE-818: ------------------------------------- Summary: JPAContainer should be pluggable Key: FORGE-818 URL: https://issues.jboss.org/browse/FORGE-818 Project: Forge Issue Type: Enhancement Components: Java EE APIs Affects Versions: 1.2.2.Final Reporter: George Gastaldi Fix For: 1.2.3.Final JPAContainer should be pluggable, allowing plugins to provide a new container without changing the core. The enum should be still be used though (deprecated perhaps), since some external plugins may still be using it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-817) Add support for SAP's Lean Java Server container

by George Gastaldi (JIRA)

George Gastaldi created FORGE-817: ------------------------------------- Summary: Add support for SAP's Lean Java Server container Key: FORGE-817 URL: https://issues.jboss.org/browse/FORGE-817 Project: Forge Issue Type: Feature Request Components: Java EE APIs Affects Versions: 1.2.2.Final Reporter: George Gastaldi Assignee: Ivan St. Ivanov Fix For: 1.2.3.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-817) Add support for SAP's Lean Java Server container

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-817?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-817. --------------------------------- Resolution: Done > Add support for SAP's Lean Java Server container > ------------------------------------------------ > > Key: FORGE-817 > URL: https://issues.jboss.org/browse/FORGE-817 > Project: Forge > Issue Type: Feature Request > Components: Java EE APIs > Affects Versions: 1.2.2.Final > Reporter: George Gastaldi > Assignee: Ivan St. Ivanov > Fix For: 1.2.3.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-816) Field command should "pick-up" the newly created field to provide a better user experience with Constraint command

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-816?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-816: ---------------------------------- Labels: starter (was: ) > Field command should "pick-up" the newly created field to provide a better user experience with Constraint command > ------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-816 > URL: https://issues.jboss.org/browse/FORGE-816 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.2.2.Final > Reporter: Lincoln Baxter III > Labels: starter > Fix For: 1.2.3.Final > > > {code} > entity --named Customer > field string --named firstName > constraint size --min 0 --max 25 > {code} > Currently, the user must CD into the field in order to add constraints, which is not the most natural interaction. > This will not break scripts because field is still a member of a JavaResource, so new-field should still be available (must verify.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-816) Field command should "pick-up" the newly created field to provide a better user experience with Constraint command

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-816: ---------------------------------------- Summary: Field command should "pick-up" the newly created field to provide a better user experience with Constraint command Key: FORGE-816 URL: https://issues.jboss.org/browse/FORGE-816 Project: Forge Issue Type: Enhancement Components: Builtin Plugins Affects Versions: 1.2.2.Final Reporter: Lincoln Baxter III Fix For: 1.2.3.Final {code} entity --named Customer field string --named firstName constraint size --min 0 --max 25 {code} Currently, the user must CD into the field in order to add constraints, which is not the most natural interaction. This will not break scripts because field is still a member of a JavaResource, so new-field should still be available (must verify.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2013