March 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1651) Introduce a parser-json addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1651?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1651: ---------------------------------------- Other features: - Integration with Resources addon through a JSONResource - > Introduce a parser-json addon > ----------------------------- > > Key: FORGE-1651 > URL: https://issues.jboss.org/browse/FORGE-1651 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Labels: Starter > Fix For: 2.x Future > > > Just like the Java parser and XML parser addons, we should have a JSON parser addon (based on the Java API for JSON processing (JSR-353). > API and IMPL could be based on https://jsonp.java.net/download.html -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1651) Introduce a parser-json addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1651?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1651: ----------------------------------- Description: Just like the Java parser and XML parser addons, we should have a JSON parser addon (based on the Java API for JSON processing (JSR-353). API and IMPL could be based on https://jsonp.java.net/download.html was:API and IMPL could be based on https://jsonp.java.net/download.html > Introduce a parser-json addon > ----------------------------- > > Key: FORGE-1651 > URL: https://issues.jboss.org/browse/FORGE-1651 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Labels: Starter > Fix For: 2.x Future > > > Just like the Java parser and XML parser addons, we should have a JSON parser addon (based on the Java API for JSON processing (JSR-353). > API and IMPL could be based on https://jsonp.java.net/download.html -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1652) Create a json-parser addon

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1652: -------------------------------------- Summary: Create a json-parser addon Key: FORGE-1652 URL: https://issues.jboss.org/browse/FORGE-1652 Project: Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 2.1.1.Final Reporter: Vineet Reynolds Just like the Java parser and XML parser addons, we should have a JSON parser addon (based on the Java API for JSON processing (JSR-353). -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1652) Create a json-parser addon

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1652?page=com.atlassian.jira.plugin... ] Vineet Reynolds deleted FORGE-1652: ----------------------------------- > Create a json-parser addon > -------------------------- > > Key: FORGE-1652 > URL: https://issues.jboss.org/browse/FORGE-1652 > Project: Forge > Issue Type: Feature Request > Reporter: Vineet Reynolds > > Just like the Java parser and XML parser addons, we should have a JSON parser addon (based on the Java API for JSON processing (JSR-353). -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1651) Introduce a parser-json addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1651?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1651: ---------------------------------------- Javadocs: http://docs.oracle.com/javaee/7/api/javax/json/package-summary.html > Introduce a parser-json addon > ----------------------------- > > Key: FORGE-1651 > URL: https://issues.jboss.org/browse/FORGE-1651 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Labels: Starter > Fix For: 2.x Future > > > API and IMPL could be based on https://jsonp.java.net/download.html -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1651) Introduce a parser-json addon

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1651: -------------------------------------- Summary: Introduce a parser-json addon Key: FORGE-1651 URL: https://issues.jboss.org/browse/FORGE-1651 Project: Forge Issue Type: Feature Request Components: Parsers / File Manipulation Affects Versions: 2.1.1.Final Reporter: George Gastaldi Fix For: 2.x Future API and IMPL could be based on https://jsonp.java.net/download.html -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1650) Support creation of JSON object models from application code through JSON-P APIs

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1650: -------------------------------------- Summary: Support creation of JSON object models from application code through JSON-P APIs Key: FORGE-1650 URL: https://issues.jboss.org/browse/FORGE-1650 Project: Forge Issue Type: Feature Request Components: Java EE Affects Versions: 2.1.1.Final Reporter: Vineet Reynolds One could automate generation of parsers that construct JSONObjects from application models, through Forge. This would reduce unnecessary typing involved in mapping the application model to the JSON model. This could be supported for both the object-model ({{JSONObjectBuilder}}) as well as the stream-model ({{JsonParser}}) of JSON-P. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1643) Embed the JAXP implementation in the xml-parser JAR

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1643?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1643: ----------------------------------- Summary: Embed the JAXP implementation in the xml-parser JAR (was: ClassNotFoundException when running Furnace-SE under Wildfly) > Embed the JAXP implementation in the xml-parser JAR > --------------------------------------------------- > > Key: FORGE-1643 > URL: https://issues.jboss.org/browse/FORGE-1643 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 2.1.1.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > https://github.com/forgeide/forgeide is an attempt to run Furnace as a service inside a web application. Furnace starts up, the following exception is thrown: > {code} > 14:27:54,813 ERROR [stderr] (Furnace Container ) Exception in thread "Furnace Container " javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory not found > 14:27:54,814 ERROR [stderr] (Furnace Container ) at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:127) > 14:27:54,814 ERROR [stderr] (Furnace Container ) at org.jboss.forge.parser.xml.XMLParser.parse(XMLParser.java:115) > 14:27:54,815 ERROR [stderr] (Furnace Container ) at org.jboss.forge.parser.xml.XMLParser.parse(XMLParser.java:81) > 14:27:54,815 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.getXmlRoot(AddonRepositoryImpl.java:585) > 14:27:54,815 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.access$000(AddonRepositoryImpl.java:51) > 14:27:54,816 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl$13.call(AddonRepositoryImpl.java:509) > 14:27:54,816 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl$13.call(AddonRepositoryImpl.java:501) > 14:27:54,817 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.LockManagerImpl.performLocked(LockManagerImpl.java:48) > 14:27:54,817 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listEnabled(AddonRepositoryImpl.java:500) > 14:27:54,817 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl$14.call(AddonRepositoryImpl.java:545) > 14:27:54,818 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl$14.call(AddonRepositoryImpl.java:541) > 14:27:54,818 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.LockManagerImpl.performLocked(LockManagerImpl.java:48) > 14:27:54,819 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonRepositoryImpl.listEnabledCompatibleWithVersion(AddonRepositoryImpl.java:540) > 14:27:54,819 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.ImmutableAddonRepository.listEnabledCompatibleWithVersion(ImmutableAddonRepository.java:87) > 14:27:54,820 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.getAllEnabledAddonsInAllRepositories(CompleteAddonGraph.java:81) > 14:27:54,820 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.graph.CompleteAddonGraph.<init>(CompleteAddonGraph.java:26) > 14:27:54,820 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:194) > 14:27:54,821 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager$4.call(AddonLifecycleManager.java:182) > 14:27:54,821 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.LockManagerImpl.performLocked(LockManagerImpl.java:48) > 14:27:54,822 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.addons.AddonLifecycleManager.forceUpdate(AddonLifecycleManager.java:181) > 14:27:54,822 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:192) > 14:27:54,822 ERROR [stderr] (Furnace Container ) at org.jboss.forge.furnace.impl.FurnaceImpl$1.run(FurnaceImpl.java:123) > 14:27:54,823 ERROR [stderr] (Furnace Container ) Caused by: java.lang.ClassNotFoundException: __redirected/__DocumentBuilderFactory > 14:27:54,823 ERROR [stderr] (Furnace Container ) at java.lang.Class.forName0(Native Method) > 14:27:54,823 ERROR [stderr] (Furnace Container ) at java.lang.Class.forName(Class.java:270) > 14:27:54,824 ERROR [stderr] (Furnace Container ) at javax.xml.parsers.FactoryFinder.getProviderClass(FactoryFinder.java:123) > 14:27:54,824 ERROR [stderr] (Furnace Container ) at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:178) > 14:27:54,824 ERROR [stderr] (Furnace Container ) at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:147) > 14:27:54,825 ERROR [stderr] (Furnace Container ) at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:219) > 14:27:54,825 ERROR [stderr] (Furnace Container ) at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:121) > 14:27:54,825 ERROR [stderr] (Furnace Container ) ... 21 more > {code} > An elegant solution would be xml-parser to pack its own JAXP implementation, not relying on external confguration. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1649) Support creation of Encoders and Decoders for Websocket Messages

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1649: -------------------------------------- Summary: Support creation of Encoders and Decoders for Websocket Messages Key: FORGE-1649 URL: https://issues.jboss.org/browse/FORGE-1649 Project: Forge Issue Type: Feature Request Components: Java EE Affects Versions: 2.1.1.Final Reporter: Vineet Reynolds We should support creation of Encoders and Decoders for POJOs so that they can be converted into Websocket Messages. This needs to be done with the message mediatype in mind. For instance, if we are to produce JSON messages, we should generate encoders and decoders that support different APIs, but notably one that uses the new JSON-P API (possibly supporting both object and stream based APIs). Likewise, for XML, we should support several APIs to marshal/unmarshal messages of type XML. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (FORGE-1362) Shell is sluggish when the first command is typed

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1362?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1362: -------------------------------------- Assignee: George Gastaldi > Shell is sluggish when the first command is typed > ------------------------------------------------- > > Key: FORGE-1362 > URL: https://issues.jboss.org/browse/FORGE-1362 > Project: Forge > Issue Type: Enhancement > Components: UI - Shell > Affects Versions: 2.0.0.Beta3 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.x Future > > > After shell starts, when any command is executed or <TAB> is pressed, the shell takes a little longer to execute than subsequent times. This may be related to lazy initialization. -- 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

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2014