January 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Assigned: (SEAMFORGE-25) Forge should inform users when they are attempting to run on an unsupported JRE version

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-25?page=com.atlassian.jira.plug... ] Lincoln Baxter III reassigned SEAMFORGE-25: ------------------------------------------- Assignee: Lincoln Baxter III > Forge should inform users when they are attempting to run on an unsupported JRE version > --------------------------------------------------------------------------------------- > > Key: SEAMFORGE-25 > URL: https://issues.jboss.org/browse/SEAMFORGE-25 > Project: Seam Forge > Issue Type: Feature Request > Components: Init Scripts > Affects Versions: 1.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Alpha2 > > > *nix: > #------------------------- > JAVAVER=`$JAVACMD -version 2>&1` > case $JAVAVER in > *1.[6-9]*) ;; > *1.[1-5]*) > echo " Error: a Java 1.6 or higher JRE is required to run Forge; found [$JAVACMD -version == $JAVAVER]." > exit 1 > ;; > esac > *windoze > #----------------------- > ???? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Work started: (SEAMFORGE-25) Forge should inform users when they are attempting to run on an unsupported JRE version

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-25?page=com.atlassian.jira.plug... ] Work on SEAMFORGE-25 started by Lincoln Baxter III. > Forge should inform users when they are attempting to run on an unsupported JRE version > --------------------------------------------------------------------------------------- > > Key: SEAMFORGE-25 > URL: https://issues.jboss.org/browse/SEAMFORGE-25 > Project: Seam Forge > Issue Type: Feature Request > Components: Init Scripts > Affects Versions: 1.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 1.0.0.Alpha2 > > > *nix: > #------------------------- > JAVAVER=`$JAVACMD -version 2>&1` > case $JAVAVER in > *1.[6-9]*) ;; > *1.[1-5]*) > echo " Error: a Java 1.6 or higher JRE is required to run Forge; found [$JAVACMD -version == $JAVAVER]." > exit 1 > ;; > esac > *windoze > #----------------------- > ???? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-25) Forge should inform users when they are attempting to run on an unsupported JRE version

by Lincoln Baxter III (JIRA)

Forge should inform users when they are attempting to run on an unsupported JRE version --------------------------------------------------------------------------------------- Key: SEAMFORGE-25 URL: https://issues.jboss.org/browse/SEAMFORGE-25 Project: Seam Forge Issue Type: Feature Request Components: Init Scripts Affects Versions: 1.0.0.Alpha1 Reporter: Lincoln Baxter III Fix For: 1.0.0.Alpha2 *nix: #------------------------- JAVAVER=`$JAVACMD -version 2>&1` case $JAVAVER in *1.[6-9]*) ;; *1.[1-5]*) echo " Error: a Java 1.6 or higher JRE is required to run Forge; found [$JAVACMD -version == $JAVAVER]." exit 1 ;; esac *windoze #----------------------- ???? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMREST-9) Add support for @Valid

by Jozef Hartinger (JIRA)

Add support for @Valid ---------------------- Key: SEAMREST-9 URL: https://issues.jboss.org/browse/SEAMREST-9 Project: Seam REST Issue Type: Feature Request Components: Bean Validation Affects Versions: Alpha1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Allow users to explicitly mark which parameters should be validated using @Valid annotation. This requires changes in the validation logic and validation metadata. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3347) change column width in tables of pdf doc in security chapter

by Carsten Hoehne (JIRA)

change column width in tables of pdf doc in security chapter ------------------------------------------------------------ Key: JBSEAM-3347 URL: https://jira.jboss.org/jira/browse/JBSEAM-3347 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.BETA1 Reporter: Carsten Hoehne Please try to adapt the column width of tables in the security chapter. As an example see table 15.4 Identity Management API in chapter 15.4.6 Please make the columnb Description a little bit wider and try to not overwrite strings in column Returns with strings in column Method Thanks in advance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4589) ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans

by Sebastien Boutte (JIRA)

ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans -------------------------------------------------------------------------------- Key: JBSEAM-4589 URL: https://jira.jboss.org/jira/browse/JBSEAM-4589 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.2.GA Reporter: Sebastien Boutte As it is said in documentation (Part : EJB Passivation and the ManagedEntityInterceptor) ; seam is capable of passivate SMPC (EntityManager with @In) and reattach all instances loaded at activation. For simple fields (Entities, Lists, Maps ...) , it works perfectly. For user defined fields (Wrapper with entity object, or more complex structure), this is not the case and cause a lazy exception later after activation. In class ManagedEntityWrapper, methods wrap and deserialize are not able to do in depth operations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4375) ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation

by Darryl Smith (JIRA)

ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4375 URL: https://jira.jboss.org/jira/browse/JBSEAM-4375 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Reporter: Darryl Smith setup: Parent (cid1) -> First Nested (cid2) ----> Second Nested (cid3) cid3: conversation.endAndRedirect(true); which calls setLongRunningConversation(false); FacesManager's redirect method tries to encode the page parameters of the parent view, which accesses a component created in cid2 the conversation we are returning to. This triggers ManagedEntityWrapper's switchToConversationContextOfComponent which switches the current conversation to cid2 after ManagedEntityWrapper wraps the component ManagedEntityWrapper's restorePreviousConversationContextIfNecessary method is called with oldCid = cid3 which triggers Contexts.getConversationContext().flush(); When flush is invoke the conversation (cid2) isn't long running, so flush removes all components created in cid2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-24) Ability to "switch themes" in generated applications

by Lincoln Baxter III (JIRA)

Ability to "switch themes" in generated applications ---------------------------------------------------- Key: SEAMFORGE-24 URL: https://issues.jboss.org/browse/SEAMFORGE-24 Project: Seam Forge Issue Type: Feature Request Components: Brainstorming Reporter: Lincoln Baxter III In the CSS Zengarden style, it would be cool if Forge could "switch" themes of scaffolded or generated applications, using a standard CSS template format. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-4754) Documentation broken links

by Ondrej Skutka (JIRA)

Documentation broken links --------------------------- Key: JBSEAM-4754 URL: https://issues.jboss.org/browse/JBSEAM-4754 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.2.1.CR3 Reporter: Ondrej Skutka Here is the list of broken links in Seam Reference Guide PDF: http://jexcelapi.sourceforge.net/resources/javadocs/current/docs/jxl/form... http://jexcelapi.sourceforge.net/resources/javadocs/current/docs/jxl/writ... http://labs.jboss.com/jemsinstaller/downloads http://www.hibernate.org/hib_docs/search/reference/en/html_single/ http://www.nwnetworks.com/iezones.htm/ Please search through the documentation for occurrences of these links, since they are on multiple places throughout the document. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
5
0 / 0

[JBoss JIRA] Commented: (SEAMCATCH-4) Include the ability to filter stack traces

by Jason Porter (JIRA)

[ https://issues.jboss.org/browse/SEAMCATCH-4?page=com.atlassian.jira.plugi... ] Jason Porter commented on SEAMCATCH-4: -------------------------------------- I may be able to use the ExceptionStack object, but it has some odd things going on because it's mutable. I still may be able to use it, but I need another object that will contain the corrected stack trace and indexes where the exception is wrapped and re-thrown. I should be able to find those indexes with either their size minus two (which seems to be right, but more testing is needed) or I can iterate through both traces (the current exception and the next wrapped) and find out where they're equal, once I have that I'll know the stack index where they diverge slightly for the wrap. > Include the ability to filter stack traces > ------------------------------------------ > > Key: SEAMCATCH-4 > URL: https://issues.jboss.org/browse/SEAMCATCH-4 > Project: Seam Catch > Issue Type: Feature Request > Reporter: Jason Porter > Assignee: Jason Porter > Fix For: 3.0.0.Alpha4 > > > Catch should draw from ideas such as: > - http://www.docjar.org/html/api/org/apache/commons/lang/exception/Nestable... > - http://stackoverflow.com/questions/2504647/bash-how-to-filter-java-except... > - http://squirrelsewer.blogspot.com/2010/03/filter-your-stack-traces.html > - http://pastebin.com/p8aCSeuu -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 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 January 2011