December 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-565) Persistence plugin needs to better guide users through a custom database configuration

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-565?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-565: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > Persistence plugin needs to better guide users through a custom database configuration > -------------------------------------------------------------------------------------- > > Key: FORGE-565 > URL: https://issues.jboss.org/browse/FORGE-565 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.4.Final > Reporter: Lincoln Baxter III > Priority: Minor > Labels: Starter > Fix For: 1.1.4.Final > > > In order to use the PostgreSQL (or any custom) database, you'll need to skip the --container JBOSS_AS7 parameter; otherwise, this will override the data-source configuration as seen in the INFO messages: > {code}***INFO*** Setting transaction-type="JTA" > ***INFO*** Using example data source [java:jboss/datasources/ExampleDS]{code} > We should probably make this more clear, or perhaps create a warning or error scenario instead of INFO. When you remove the --container parameter. > It should be much clearer that you may need to use some of the extended parameters like --jndiName and so forth. > This can probably be done by updating the PersistencePlugin and related classes: > https://github.com/forge/core/blob/master/javaee-impl/src/main/java/org/j... -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-593) Forge swallows first character of user input after restarting (typically from plugin installation)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-593?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-593: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > Forge swallows first character of user input after restarting (typically from plugin installation) > -------------------------------------------------------------------------------------------------- > > Key: FORGE-593 > URL: https://issues.jboss.org/browse/FORGE-593 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.5.Final > Reporter: Lincoln Baxter III > Labels: annoying > Fix For: 1.1.4.Final > > > 'forge install-plugin openshift' > Then type something. The first character you type will not be displayed or read. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-601) XML Parser should support inclusion of elements beginning with '<!' (e.g. DTDs)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-601?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-601: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > XML Parser should support inclusion of elements beginning with '<!' (e.g. DTDs) > ------------------------------------------------------------------------------- > > Key: FORGE-601 > URL: https://issues.jboss.org/browse/FORGE-601 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.0.5.Final > Environment: Fedora 15 (64-bit), Java 1.7 > Reporter: Ryan Bradley > Fix For: 1.1.4.Final > > > In my plugin, I use Apache Tiles, which require a reference to a DTD in their layouts/views XML declaration files. I am trying to create these files from a template, and then add more view/layout definitions later in the plugin's workflow. > However, depending on how the DTD reference (in the format <!....>) is added, it is either omitted from the generated file or causes an exception when the XML Parser tries to parse the file for the root node. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-604) Add support for Java EE 6 Full Profile

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-604?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-604: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > Add support for Java EE 6 Full Profile > -------------------------------------- > > Key: FORGE-604 > URL: https://issues.jboss.org/browse/FORGE-604 > Project: Forge > Issue Type: Task > Components: Java EE APIs > Affects Versions: 1.0.5.Final > Environment: All > Reporter: Christopher Volk > Fix For: 1.1.4.Final > > > Add support for Java EE 6 Full profile, including multi-module support (cli/maven/ear) and EAR packaging. > The EAR packaging should be fairly "easy" to implement. The maven side of multi-module should be similarly "easy". CLI multi-module support is something I would expect to take up most of this effort. > I believe this to be a critical feature - serious enterprise software requires Full Profile, and Forge would be even more useful for bootstrapping and developing against the Full Profile than even the Web Profile. I know that almost all the apps I work on professionally require Full Profile. > This would be a real home run, IMHO, especially in the wake of JBoss AS7.1's Full Profile Compliance :-) -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-606) Provide interactive command to resolve cyclic graphs in REST endpoints generated from entities

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-606?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-606: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > Provide interactive command to resolve cyclic graphs in REST endpoints generated from entities > ---------------------------------------------------------------------------------------------- > > Key: FORGE-606 > URL: https://issues.jboss.org/browse/FORGE-606 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Reporter: Dan Allen > Fix For: 1.1.4.Final > > > Currently the REST plugin generates broken endpoints if there are cyclic references in the JPA entities. Forge should provide a plugin to hep the developer resolve these references to get past this bump in the road. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-607) ResourceException after pick-up command and subsequently hitting 'up arrow' and 'tab'

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-607?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-607: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > ResourceException after pick-up command and subsequently hitting 'up arrow' and 'tab' > ------------------------------------------------------------------------------------- > > Key: FORGE-607 > URL: https://issues.jboss.org/browse/FORGE-607 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.5.Final > Reporter: Koen Aers > Fix For: 1.1.4.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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-609) @RequiresFacet and @RequiresProject should be Interceptor bindings instead of static constraints.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-609?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-609: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > @RequiresFacet and @RequiresProject should be Interceptor bindings instead of static constraints. > ------------------------------------------------------------------------------------------------- > > Key: FORGE-609 > URL: https://issues.jboss.org/browse/FORGE-609 > Project: Forge > Issue Type: Enhancement > Components: Plugin API, Shell > Affects Versions: 1.0.5.Final > Reporter: Lincoln Baxter III > Fix For: 1.1.4.Final > > > This would also incorporate FORGE-214, since these constraints could now be used on any bean Class or method. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-699) create a plugin for WildcardImportResolver

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-699?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-699: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > create a plugin for WildcardImportResolver > ------------------------------------------ > > Key: FORGE-699 > URL: https://issues.jboss.org/browse/FORGE-699 > Project: Forge > Issue Type: Story > Components: Parsers / File Manipulation > Affects Versions: 1.1.1.Final > Reporter: fiorenzo pizza > Assignee: fiorenzo pizza > Fix For: 1.1.4.Final > > > general notes > We need to create some WildcardImportResolver (Responsible for providing additional import resolution functionality for situations where classes have referenced a package or wild-card import) > summary: > - when start creation of index --> new-project > - when update the index --> re-open project | add|remove plugins to the project | add|remove maven dependencies | add|remove new class inside forge project > - where save the index --> always > - how information to save for future search --> className, jarName (null if the class is in the project), packageName, absoluteClassName > - how search inside the index --> (ram hashmap? ram db?) > - how generate new entry for the index --> cdi event > general considerations > 1) when forge create a new-project we should create some structure to add all classes used referenced by project > 2) we need to add all classes required from some plugin (persistence|scaffolding..) > 2) we need to add all classes inside maven dependencies > 3) we need to add all classes created in the project > 4) we need remove all deleted classes > 5) we need to remove all classes inside dependecies removed > 6) we need to update the index files, when forge project is reopen (the user could modify the project out of forge) > problems > 1) with a lot of jars, the indexing process should be slow!! > 2) how synchronize the access to index > 3) how we should synchronize of index update? > requirements > 1) we need some fast library to extract classes from jar files > 2) we should use cdi event to start a single jar indexing > HOW CREATE INDEX FROM JAR: > possibile libraries: jandex, tattletale, jarindexer > FIRST CANDIDATE: JANDEX > i started to hack jandex code, because jandex is very fast. > Jandex opens the jar files using java jar utilities: JarFile jar = new JarFile(jarFile); > and for every class generate a ClassInfo object: ClassInfo info = indexer.index(jar.getInputStream(entry)); > For my test, i removed some methods inside jandex: we don't care about annotations inside classes. Also i removed the generation of file index. > questions: > 1) why don't use H2, the Java SQL database, for memorize all informations about classes? > How memorize for a single class: > 1) classname, jar name (with version), package name, complete name -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-652) Remove jLine classes bundled inside Forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-652?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-652: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > Remove jLine classes bundled inside Forge > ----------------------------------------- > > Key: FORGE-652 > URL: https://issues.jboss.org/browse/FORGE-652 > Project: Forge > Issue Type: Enhancement > Reporter: George Gastaldi > Fix For: 1.1.4.Final > > > Forge should use the jline library instead of bundling the classes as a separate module (shell-impl). -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-621) Need to configure "hibernate.transaction.jta.platform" when using Hibernate outside of JBoss AS

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-621?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-621: ---------------------------------- Fix Version/s: 1.1.4.Final (was: 1.1.3.Final) > Need to configure "hibernate.transaction.jta.platform" when using Hibernate outside of JBoss AS > ----------------------------------------------------------------------------------------------- > > Key: FORGE-621 > URL: https://issues.jboss.org/browse/FORGE-621 > Project: Forge > Issue Type: Bug > Components: Java EE APIs > Affects Versions: 1.0.6.Final > Reporter: Luca Masini > Labels: hibernate_persistance_layer, weblogic > Fix For: 1.1.4.Final > > Attachments: JPAContainer.java, WebLogic12cContainer.java > > > When running in an App Server that is not JBoss we need to configure the "hibernate.transaction.jta.platform" to bind the JTA resource to the current EntityManager. For instance, using WebLogic 12c: > <property name="hibernate.transaction.jta.platform" value="org.hibernate.service.jta.platform.internal.WeblogicJtaPlatform" /> > I think that a new parameter is needed on the persistence setup command. -- 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

13 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2012