December 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-728) Documentation for Getting Started omits crucial details

by Robert Dalgleish (JIRA)

Robert Dalgleish created FORGE-728: -------------------------------------- Summary: Documentation for Getting Started omits crucial details Key: FORGE-728 URL: https://issues.jboss.org/browse/FORGE-728 Project: Forge Issue Type: Bug Components: Documentation Reporter: Robert Dalgleish The documentation in http://forge.jboss.org/docs/using/basic-javaee-app.html omits critical details. 1) In section "Set up persistence (JPA)", useful values for "{your JPA implementation}" and "{your container}" are not provided. From slopping around, I found that "HIBERNATE" and "JBOSS" worked. 2) While trying to follow section "Deploy/undeploy to AS7", issuing the command "forge install-plugin jboss-as-7" yields the error: ***ERROR*** Exception encountered: no default repository set: (to set, type: set DEFAULT_PLUGIN_REPO <repository>) (type "set VERBOSE true" to enable stack traces) At one point in the documentation, I founnd what the value of <repository> should be, namely https://raw.github.com/forge/plugin-repository/master/repository.yaml -- however, I don't think this is the correct value, as the command then proceeded to mangle the value, changing the .yaml to yaml.yaml -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-621) Support Weblogic 12c as a container in the Persistence plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-621?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-621: ---------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done Merged. Thanks for the fix Luca ! > Support Weblogic 12c as a container in the Persistence plugin > ------------------------------------------------------------- > > Key: FORGE-621 > URL: https://issues.jboss.org/browse/FORGE-621 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.6.Final > Reporter: Luca Masini > Assignee: 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-621) Support Weblogic 12c as a container in the Persistence plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-621?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-621: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/248 > Support Weblogic 12c as a container in the Persistence plugin > ------------------------------------------------------------- > > Key: FORGE-621 > URL: https://issues.jboss.org/browse/FORGE-621 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.6.Final > Reporter: Luca Masini > Assignee: 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-621) Support Weblogic 12c as a container in the Persistence plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-621?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-621: ---------------------------------- Component/s: Builtin Plugins > Support Weblogic 12c as a container in the Persistence plugin > ------------------------------------------------------------- > > Key: FORGE-621 > URL: https://issues.jboss.org/browse/FORGE-621 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-621) Support Weblogic 12c as a container in the Persistence plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-621?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-621: ---------------------------------- Assignee: Luca Masini > Support Weblogic 12c as a container in the Persistence plugin > ------------------------------------------------------------- > > Key: FORGE-621 > URL: https://issues.jboss.org/browse/FORGE-621 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.6.Final > Reporter: Luca Masini > Assignee: 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-621) Support Weblogic 12c as a container in the Persistence plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-621?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-621: ---------------------------------- Summary: Support Weblogic 12c as a container in the Persistence plugin (was: Need to configure "hibernate.transaction.jta.platform" when using Hibernate outside of JBoss AS) > Support Weblogic 12c as a container in the Persistence plugin > ------------------------------------------------------------- > > 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-719) Design an user interface API for addons

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on FORGE-719: ------------------------------------------- My comment about "fully running forge" was about not having to run Forge *inside* eclipse since that brings a whole slew of other problems with it. For this jira my concern is not about memory/performance/startup etc. thats a separate topic which I put on forge-dev so i'll leave that out of this part about UI interaction. This one is about how we avoid having Eclipse users to have to relate to things like absolute paths, keep entering data that eclipse can already provide good defaults for and how to combine commands. The wizard UI api looks interesting, but would like to see an example of how it would be used to fully grok it. I'm not sure what you mean by "build a menu" and "generate metadata for eclipse to use to build its menu" - the wizard API talks about wizards which aren't menus ? And looking at the API its dynamic (understandably) so the wizard can't be generated/deduced before actually having the input data to know which pages to show etc. > Design an user interface API for addons > --------------------------------------- > > Key: FORGE-719 > URL: https://issues.jboss.org/browse/FORGE-719 > Project: Forge > Issue Type: Story > Components: Brainstorming > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Requirements: > - It must be usable in a Shell UI > - It should be usable in a Visual UI (SWT, Swing) > - It must be typesafe, therefore allowing the use of complex types. > Let's use this JIRA to brainstorm about 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-719) Design an user interface API for addons

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-719: ------------------------------------------ In order to alleviate the startup cost of Forge just to build a menu, this new API could easily be consumed by an addon that generates metadata for Eclipse to use to build its menu. This addon could be run periodically (or after addon installation/removal) if you really want to go that route, but I think you'll find that the startup time of Forge 2.0 is minimal, and we continue to improve it. > Design an user interface API for addons > --------------------------------------- > > Key: FORGE-719 > URL: https://issues.jboss.org/browse/FORGE-719 > Project: Forge > Issue Type: Story > Components: Brainstorming > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Requirements: > - It must be usable in a Shell UI > - It should be usable in a Visual UI (SWT, Swing) > - It must be typesafe, therefore allowing the use of complex types. > Let's use this JIRA to brainstorm about 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-719) Design an user interface API for addons

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-719: ------------------------------------------ I don't think you will get around fully running Forge. But I'll assume that your gripe there is memory/performance/startup, so... let me just say that's being addressed. To address your gripe/concern - https://github.com/forge/core/tree/2.0/ui/api/src/main/java/org/jboss/for... Let us know what you think. Thanks, Lincoln > Design an user interface API for addons > --------------------------------------- > > Key: FORGE-719 > URL: https://issues.jboss.org/browse/FORGE-719 > Project: Forge > Issue Type: Story > Components: Brainstorming > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Requirements: > - It must be usable in a Shell UI > - It should be usable in a Visual UI (SWT, Swing) > - It must be typesafe, therefore allowing the use of complex types. > Let's use this JIRA to brainstorm about 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-719) Design an user interface API for addons

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on FORGE-719: ------------------------------------------- My biggest gripe/concern with the current Forge approach is that it is all very "(re)action based". i.e. plugins seem to follow the pattern of "ask user question 1,2,3,4 (based of the cmd annotations)", do something - realize something was not possible to ask about via cmd annotations "ask user question 2,3,4", do something, "ask user some more questions", do things. This is all great in a cmd-line world but really really hard for newbie users to grok (IMO) and when you actually have to do or combine multiple forge level operations things becomes really hard from an IDE user perspective - i.e. IDE users expect to be able to just press Cancel in a multi-step wizard and not see any change in his project from that, also when driving from the IDE, we'll need to be able to call out to Forge and query for the possible values etc. (something the current 'single Is this issue about solving/improving this challenge or "just" about providing an UI on top of the existing "cmd line/reaction pattern" ? Things to consider here is how forge can provide rich enough info to have "Browse.." buttons work for file/resource, database resource selection, etc. And how a multistep wizard could be created outlining pages needed to provide the questions ...and in a way that does not require fully running forge inside something like Eclipse. > Design an user interface API for addons > --------------------------------------- > > Key: FORGE-719 > URL: https://issues.jboss.org/browse/FORGE-719 > Project: Forge > Issue Type: Story > Components: Brainstorming > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Requirements: > - It must be usable in a Shell UI > - It should be usable in a Visual UI (SWT, Swing) > - It must be typesafe, therefore allowing the use of complex types. > Let's use this JIRA to brainstorm about 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2012