June 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1034) Usage of jBPM core:process-definitions needs clarification

by Arjan van Bentem (JIRA)

Usage of jBPM core:process-definitions needs clarification ---------------------------------------------------------- Key: JBSEAM-1034 URL: http://jira.jboss.com/jira/browse/JBSEAM-1034 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Minor The Seam documentation for "21.6. Configuring jBPM in Seam" describes how to add jBPM process definitions to components.xml: <core:jbpm> <core:pageflow-definitions> <value>createDocument.jpdl.xml</value> <value>editDocument.jpdl.xml</value> <value>approveDocument.jpdl.xml</value> </core:pageflow-definitions> <core:process-definitions> <value>documentLifecycle.jpdl.xml</value> </core:process-definitions> </core:jbpm> Nice, but as a side-effect a new copy is inserted into the database each time JBoss AS is started, even if the deployed EAR has not changed. This, of course, can only be noticed if in the example hibernate.cfg.xml from the DVD Store example the line <property name="hbm2ddl.auto">create-drop</property> is changed into <property name="hbm2ddl.auto">update</property> Apparently using <core:pageflow-definitions> is considered to be a developers tool: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98430 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90206 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103819 I think this needs some clarification in the documentation, but unfortunately (right now) I would not know what is the preferred way to deploy processes in Seam on a production machine. The third topic might include some ideas from others on that. Arjan. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-652) Allow use of EHCache with <s:cache/>

by Gavin King (JIRA)

Allow use of EHCache with <s:cache/> ------------------------------------ Key: JBSEAM-652 URL: http://jira.jboss.com/jira/browse/JBSEAM-652 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-650) <s:formattedText value="#{post.body}" highlight="#{word}"/>

by Gavin King (JIRA)

<s:formattedText value="#{post.body}" highlight="#{word}"/> ----------------------------------------------------------- Key: JBSEAM-650 URL: http://jira.jboss.com/jira/browse/JBSEAM-650 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.5.GA Seam needs to support wikitext ootb. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1502) Declarative renderers in seam-ui

by Pete Muir (JIRA)

Declarative renderers in seam-ui -------------------------------- Key: JBSEAM-1502 URL: http://jira.jboss.com/jira/browse/JBSEAM-1502 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Pete Muir Fix For: 1.3.0.BETA1 Evaluate and implement -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1499) Remove org.jboss.seam.ui.util.cdk.*

by Pete Muir (JIRA)

Remove org.jboss.seam.ui.util.cdk.* ----------------------------------- Key: JBSEAM-1499 URL: http://jira.jboss.com/jira/browse/JBSEAM-1499 Project: JBoss Seam Issue Type: Task Components: JSF Reporter: Pete Muir Fix For: 1.3.0.BETA1 These classes have been copied from ajax4jsf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1522) @Intercept is gone but still documented

by Christian Bauer (JIRA)

@Intercept is gone but still documented --------------------------------------- Key: JBSEAM-1522 URL: http://jira.jboss.com/jira/browse/JBSEAM-1522 Project: JBoss Seam Issue Type: Bug Reporter: Christian Bauer Assigned To: Gavin King How do I disable interception now? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-671) Add an inheritance mechanism for themes

by Bill Wallace (JIRA)

Add an inheritance mechanism for themes --------------------------------------- Key: JBSEAM-671 URL: http://jira.jboss.com/jira/browse/JBSEAM-671 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.GA Reporter: Bill Wallace It would be very nice to have an item in a theme that allowed one to indicate which theme to inherit from, eg: default theme - no inheritance: printable.properties: org.jboss.seam.theme.inherit default accessible.properties: org.jboss.seam.theme.inherit default accessible-printable.properties org.jboss.seam.theme.inherit printable accessible ... Thus, the accessible-printable version would inherit first from printable, then from accessible. Assuming they could in fact co-exist, that might work out nicely to produce an accessible-printable version. It would also be nice to allow inheritance from generic property files that are NOT explicit themes - that way, you can put portions of a theme in another file, and just inherit from all the required themes. Note that the Java API makes this relatively easy, just be creating a chain of inheritance. (Note that only accessible would chain to default, a new printable would be needed that only inherited from accessible, not from anything else.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1516) Issuing another request while waiting for AJAX request to return causes concurrent conversation exception

by Robb Greathouse (JIRA)

Issuing another request while waiting for AJAX request to return causes concurrent conversation exception --------------------------------------------------------------------------------------------------------- Key: JBSEAM-1516 URL: http://jira.jboss.com/jira/browse/JBSEAM-1516 Project: JBoss Seam Issue Type: Bug Components: Async Affects Versions: 1.2.1.GA Environment: RichFaces, AJAX and Seam 1.2.1 Reporter: Robb Greathouse Priority: Minor When the user kicks off an AJAX request and then clicks on a link before it responds we get a concurrent conversation exception. Shouldn't a request that would cause this error be held until the request either times out or is completed and then passed through? Thinking that the filter in tomcat that gets the conversation could also prevent consurrency crashes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-911) endAndRedirect() in jBPM pageflow

by Gavin King (JIRA)

endAndRedirect() in jBPM pageflow --------------------------------- Key: JBSEAM-911 URL: http://jira.jboss.com/jira/browse/JBSEAM-911 Project: JBoss Seam Issue Type: Feature Request Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.8 GA Currently all jbpm pageflows and at a specific page. We want to be able to end the flow at the page of the parent conversation, by introducing something like an end-state element. Perhaps we should also have the ability to return to the starting page even when there was no parent conversation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1320) Seam Captcha component: clear response field before redisplaying

by Paul Milner (JIRA)

Seam Captcha component: clear response field before redisplaying ---------------------------------------------------------------- Key: JBSEAM-1320 URL: http://jira.jboss.com/jira/browse/JBSEAM-1320 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Environment: Any Reporter: Paul Milner Priority: Minor As suggested on the Seam Forum, I am submitting this as a feature request: Hi using the captcha provided with Seam (and used as suggested in the Seam documentation), I have the following problem. If I submit a page which contains the captcha, and having filled in the catpcha response field, but validation fails due to a problem in another field on the page, the page is redisplayed but with a NEW captcha image. However the captcha response field is repopulated with what I previously put there, even though the image has now changed. I would like for the response text to be cleared when a new captcha image is generated. Is there a way to do this at the moment? Thanks in advance, Paul -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2007