June 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-2231) Setup wizard for wiki

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-2231?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-2231. --------------------------------- Resolution: Won't Fix closing, wiki example is EOL > Setup wizard for wiki > --------------------- > > Key: JBSEAM-2231 > URL: https://issues.jboss.org/browse/JBSEAM-2231 > Project: Seam 2 > Issue Type: Feature Request > Components: Wiki > Reporter: Christian Bauer > Priority: Blocker > > Write a setup wizard that replaces the manual wiki-data.sql editing and import. We should have the following setup procedure: > - Get the recommended environment ready (JBoss AS, MySQL) > - Deploy the wiki-ddl.sql on a new database > - Deploy the wiki.war on the appserver > - Open http://server/wiki/ and go through the setup wizard > The wizard will first import the minimum dataset (guest/admin users, roles, start page) and then ask the usual setup questions (site base URL, etc.). Depending on the future of the plugin API, it could also optionally allow you to configure some plugin defaults so you don't have to go into the Admin screen to change them after the install. Also, we can offer prepackaged datasets for certain use cases that can be imported with the wizard, e.g. "Help Documents", "Blog Website", "Forum Website". -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-2645) Promote forum thread to FAQ

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-2645?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-2645. --------------------------------- Resolution: Won't Fix closing, wiki example is EOL > Promote forum thread to FAQ > --------------------------- > > Key: JBSEAM-2645 > URL: https://issues.jboss.org/browse/JBSEAM-2645 > Project: Seam 2 > Issue Type: Feature Request > Components: Wiki > Reporter: Gavin King > Priority: Blocker > > Easily promote a forum thread into the FAQ browser -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-2231) Setup wizard for wiki

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-2231?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-2231. --------------------------------- Resolution: Done closing, wiki example is EOL > Setup wizard for wiki > --------------------- > > Key: JBSEAM-2231 > URL: https://issues.jboss.org/browse/JBSEAM-2231 > Project: Seam 2 > Issue Type: Feature Request > Components: Wiki > Reporter: Christian Bauer > Priority: Blocker > > Write a setup wizard that replaces the manual wiki-data.sql editing and import. We should have the following setup procedure: > - Get the recommended environment ready (JBoss AS, MySQL) > - Deploy the wiki-ddl.sql on a new database > - Deploy the wiki.war on the appserver > - Open http://server/wiki/ and go through the setup wizard > The wizard will first import the minimum dataset (guest/admin users, roles, start page) and then ask the usual setup questions (site base URL, etc.). Depending on the future of the plugin API, it could also optionally allow you to configure some plugin defaults so you don't have to go into the Admin screen to change them after the install. Also, we can offer prepackaged datasets for certain use cases that can be imported with the wizard, e.g. "Help Documents", "Blog Website", "Forum Website". -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-2722) Wiki plugin metadata

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-2722?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-2722. --------------------------------- Resolution: Won't Fix closing, wiki example is EOL > Wiki plugin metadata > -------------------- > > Key: JBSEAM-2722 > URL: https://issues.jboss.org/browse/JBSEAM-2722 > Project: Seam 2 > Issue Type: Task > Components: Wiki > Reporter: Christian Bauer > Priority: Blocker > > Plugins/macros need metadata, some random ideas: > protected String[] skins = {"d", "m"} > protected long accessLevel = 0; > protected boolean documentDiscriminator = false; > protected boolean reentrant = true; > protected boolean renderedOnce = false; > protected boolean affectsRenderingOnly = true; > protected boolean appliesToHeader = false; > protected boolean appliesToContent = true; > protected boolean appliesToFooter = false; > protected boolean displayedInPreview = true; > createMethodBuildTime > createMethodRenderTime -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4037) Define required SPI for RESTEasy integration

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4037?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-4037. --------------------------------- Fix Version/s: 2.2.0.GA Resolution: Done closing as both referenced issues are closed too > Define required SPI for RESTEasy integration > -------------------------------------------- > > Key: JBSEAM-4037 > URL: https://issues.jboss.org/browse/JBSEAM-4037 > Project: Seam 2 > Issue Type: Task > Components: WS > Reporter: Christian Bauer > Assignee: Jozef Hartinger > Priority: Critical > Fix For: 2.2.0.GA > > > This issue is a compilation of other issues that help us summarize and define the SPI we need from RESTEasy for Seam integration. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4020) Custom RESTEasy StringConverter provider classes need special registration

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4020?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-4020. --------------------------------- Assignee: Christian Bauer Resolution: Done correct resolution > Custom RESTEasy StringConverter provider classes need special registration > -------------------------------------------------------------------------- > > Key: JBSEAM-4020 > URL: https://issues.jboss.org/browse/JBSEAM-4020 > Project: Seam 2 > Issue Type: Task > Components: WS > Reporter: Christian Bauer > Assignee: Christian Bauer > Fix For: 2.2.0.GA > > > RESTEasy offers a custom StringConverter provider extension. Unlike normal providers, the SPI in RESTEasy for registration of these providers is different: > if (StringConverter.class.isAssignableFrom(providerClass)) { > providerFactory.addStringConverter(providerClass); > } else { > providerFactory.registerProvider(providerClass); > } > This needs to be fixed in RestEasyDispatcher.java -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4020) Custom RESTEasy StringConverter provider classes need special registration

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4020?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-4020: ---------------------------------- Fix Version/s: 2.2.0.GA > Custom RESTEasy StringConverter provider classes need special registration > -------------------------------------------------------------------------- > > Key: JBSEAM-4020 > URL: https://issues.jboss.org/browse/JBSEAM-4020 > Project: Seam 2 > Issue Type: Task > Components: WS > Reporter: Christian Bauer > Fix For: 2.2.0.GA > > > RESTEasy offers a custom StringConverter provider extension. Unlike normal providers, the SPI in RESTEasy for registration of these providers is different: > if (StringConverter.class.isAssignableFrom(providerClass)) { > providerFactory.addStringConverter(providerClass); > } else { > providerFactory.registerProvider(providerClass); > } > This needs to be fixed in RestEasyDispatcher.java -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-1693) Imports

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-1693?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-1693. --------------------------------- Assignee: Gavin King Fix Version/s: 2.0.0.GA (was: The future) Resolution: Done > Imports > ------- > > Key: JBSEAM-1693 > URL: https://issues.jboss.org/browse/JBSEAM-1693 > Project: Seam 2 > Issue Type: Feature Request > Components: Core > Affects Versions: 2.0.0.BETA1 > Reporter: Gavin King > Assignee: Gavin King > Fix For: 2.0.0.GA > > > Currently Seam does no special processing for qualified names. The only way to alias a name to a shorter name is via <factory>. > We should provide: > * global import of a qualifier in components.xml > * import into a component or Java package via @Import > * import into a page (ie. a view id) via pages.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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-1693) Imports

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-1693?page=com.atlassian.jira.plugi... ] Marek Novotny reopened JBSEAM-1693: ----------------------------------- wrong resolution therefore reopenning > Imports > ------- > > Key: JBSEAM-1693 > URL: https://issues.jboss.org/browse/JBSEAM-1693 > Project: Seam 2 > Issue Type: Feature Request > Components: Core > Affects Versions: 2.0.0.BETA1 > Reporter: Gavin King > Fix For: The future > > > Currently Seam does no special processing for qualified names. The only way to alias a name to a shorter name is via <factory>. > We should provide: > * global import of a qualifier in components.xml > * import into a component or Java package via @Import > * import into a page (ie. a view id) via pages.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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3975) Load jBPM Process Def from the DB/Repo

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3975?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-3975. --------------------------------- Resolution: Deferred > Load jBPM Process Def from the DB/Repo > -------------------------------------- > > Key: JBSEAM-3975 > URL: https://issues.jboss.org/browse/JBSEAM-3975 > Project: Seam 2 > Issue Type: Feature Request > Components: BPM > Reporter: Burr Sutter > Labels: community_contributor_needed > > What about loading up process defs from their "normal" location, the database? jBPM has a "repository" that stores process instance state for long running processes as well as it versions the definitions, Seam should be able to load the process def not only from the .ear/classpath but also from the repo. -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2013