May 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2969) Deprecate or remove StyleResource, UILoadStyle, HtmlLoadStyle

by Christian Bauer (JIRA)

Deprecate or remove StyleResource, UILoadStyle, HtmlLoadStyle ------------------------------------------------------------- Key: JBSEAM-2969 URL: http://jira.jboss.com/jira/browse/JBSEAM-2969 Project: Seam Issue Type: Task Components: ICE Faces Integration Reporter: Christian Bauer Assigned To: Gregory Dick Priority: Minor If I'm the only user of these classes, they can now be removed because I include a simplified (and heavily customized version for my plugins) in the Wiki codebase. -- 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

17 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2517) Id Attribute does not render on s:graphicImage

by nathan dennis (JIRA)

Id Attribute does not render on s:graphicImage ---------------------------------------------- Key: JBSEAM-2517 URL: http://jira.jboss.com/jira/browse/JBSEAM-2517 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.1.CR1 Environment: jboss 4.2.1 Reporter: nathan dennis id attribute will not render on a s:graphicImage. Code: <s:graphicImage id="phototoedit" value="#{modeditAction.outpic}" style="border:0px;" rendered="#{modeditAction.outpic != null}"/> renders as Code: <img src="/picture/seam/resource/graphicImage/org.jboss.seam.ui.GraphicImageStore.-4aa1b80-11799ac64d4--7fee.p ng" style="border:0px;" /> -- 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

17 years, 10 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3055) UISeamCommandBase adds conversation request parameters when not needed

by Dan Allen (JIRA)

UISeamCommandBase adds conversation request parameters when not needed ---------------------------------------------------------------------- Key: JBSEAM-3055 URL: http://jira.jboss.com/jira/browse/JBSEAM-3055 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.1.0.A1, 2.0.2.SP1 Reporter: Dan Allen Priority: Minor Fix For: 2.1.0.GA The base class for s:link and s:button, UISeamCommandBase, is not very smart about the conversation id and propagation parameters, adding them even when they have no purpose. Here are the two correct behaviors that are being violated: - conversation id parameter shouldn't be appended if conversation is temporary (no conversation to pass on) - conversation propagation parameter shouldn't be appended if its value is "end" and the conversation is temporary (no conversation to end) To ensure theses parameters aren't appended, folks are having to append propagation="none" all over the place. While on the one hand, this is just an annoyance, it really throws a wrench into urlrewriting. -- 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

17 years, 10 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3049) javax.persistence.EntityNotFoundException on activating passivated entities that have been deleted

by Alex Savitsky (JIRA)

javax.persistence.EntityNotFoundException on activating passivated entities that have been deleted -------------------------------------------------------------------------------------------------- Key: JBSEAM-3049 URL: http://jira.jboss.com/jira/browse/JBSEAM-3049 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.SP1, 2.0.2.GA Environment: Tomcat 5.5 Reporter: Alex Savitsky Basically, as of 2.0.2, whenever Seam attempts to activate a passivated entity (say, via the ManagedEntityIdentityInterceptor) that has been deleted during the last action, it throws a javax.persistence.EntityNotFoundException. Previously (2.0.1), these cases have been handled correctly. The culprit is the HibernatePersistenceProvider.getClassMetadata - it was using Seam.getEntityClass, but switched to its own getEntityClass in 2.0.2, which uses Hibernate.getClass, that apparently doesn't like to encounter deleted entities... -- 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

17 years, 10 months

2
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1296) Add <propagation type="?"/> as a child to <rule> or <redirect/> / <render/> in pages.xml

by Chris Rudd (JIRA)

Add <propagation type="?"/> as a child to <rule> or <redirect/> / <render/> in pages.xml ---------------------------------------------------------------------------------------- Key: JBSEAM-1296 URL: http://jira.jboss.com/jira/browse/JBSEAM-1296 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA, 1.2.0.GA Reporter: Chris Rudd While you can add a the propagation via a parameter its a bit verbose and cluttered (due to the value binding string literal) <page view-id="/editDocument.xhtml"> <navigation from-action="#{documentEditor.update}"> <rule if="#{documentEditor.errors.empty}"> <end-conversation/> <redirect view-id="/viewDocument.xhtml"> <param name="conversationPropagation" value="#{'none'}"/> </redirect> </rule> </navigation> </page> Adding a <propagation type="?"/> would be much cleaer. <page view-id="/editDocument.xhtml"> <navigation> <rule if-outcome="done"> <end-conversation/> <redirect view-id="/viewDocument.xhtml"> <propagation type="none"/> </redirect> </rule> </navigation> </page> Side note : The reason for needing to control the propagation in the circumstance above is so that the target view (/viewDocument.xhtml) can start with a new clean conversation. The redirect mechanism delays the end of the conversation untill it gets to the redirected to view, but I dont want that conv to be used. The before-redirect attribute doesnt work in this case as the redirect url needs to include data from the existing conversation (page parameters). I use the same scenario in other places via s:link/s:button but I cannot do this here as its dependent on the outcome not what link/button I pressed -- 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

17 years, 10 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3051) Properties file translated to Brazilian Portuguese (pt_BR)

by Petterson Paula (JIRA)

Properties file translated to Brazilian Portuguese (pt_BR) ---------------------------------------------------------- Key: JBSEAM-3051 URL: http://jira.jboss.com/jira/browse/JBSEAM-3051 Project: Seam Issue Type: Patch Reporter: Petterson Paula Properties file translated to Brazilian Portuguese (pt_BR) -- 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

17 years, 10 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3050) Move Seam scanner code into Seam Core

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-3050?page=all ] Pete Muir closed JBSEAM-3050. ----------------------------- Resolution: Done Done > Move Seam scanner code into Seam Core > ------------------------------------- > > Key: JBSEAM-3050 > URL: http://jira.jboss.com/jira/browse/JBSEAM-3050 > Project: Seam > Issue Type: Task > Components: Platform interoperability > Reporter: Stan Silvert > Assigned To: Pete Muir > Fix For: 2.0.x, 2.1.0.BETA1 > > > We need to move the Seam scanner code that Ales wrote into AS5 so that you don't have to deploy jboss-seam-jbas5.jar in your Seam project. > Discussion thus far: > ALES: > How are you planning on solving the classloading issue there? > e.g. > if the custom Seam/AS5 scanning code is in AS5, but still references some Seam code, which is deployed as part of Seam app > PETE: > Hmm, we discussed splitting out the Scanner interface into an SPI, but I'm not sure that is a great idea as it will result in a proliferation of jars and confusion. > ALES: > I'm always in favor of this. > More jars or not, having proper spi is always better then some tight integration. > But then this means that people have to either > - put this spi + plugins into some top level CL space > - include it with every Seam app > Which doesn't sound that bad - since all deployments should be automatic anyway (ant, maven2, ...). > PETE: > Any other ideas? We could merge this into seam core and select the scanner as needed... > ALES: > OK, this simplifies things. > You do this via reflection - catching the first one that works. > It's the criteria of what we need that it's the problem. > At least I remember we had some issues determining weather we're running in AS5 or Embedded. > But yeah, we can give it another shot. -- 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

17 years, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3050) Move Seam scanner code into Seam Core

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-3050?page=all ] Pete Muir updated JBSEAM-3050: ------------------------------ Summary: Move Seam scanner code into Seam Core (was: Move Seam scanner code into AS) Component/s: Platform interoperability > Move Seam scanner code into Seam Core > ------------------------------------- > > Key: JBSEAM-3050 > URL: http://jira.jboss.com/jira/browse/JBSEAM-3050 > Project: Seam > Issue Type: Task > Components: Platform interoperability > Reporter: Stan Silvert > Assigned To: Pete Muir > Fix For: 2.1.0.BETA1, 2.0.x > > > We need to move the Seam scanner code that Ales wrote into AS5 so that you don't have to deploy jboss-seam-jbas5.jar in your Seam project. > Discussion thus far: > ALES: > How are you planning on solving the classloading issue there? > e.g. > if the custom Seam/AS5 scanning code is in AS5, but still references some Seam code, which is deployed as part of Seam app > PETE: > Hmm, we discussed splitting out the Scanner interface into an SPI, but I'm not sure that is a great idea as it will result in a proliferation of jars and confusion. > ALES: > I'm always in favor of this. > More jars or not, having proper spi is always better then some tight integration. > But then this means that people have to either > - put this spi + plugins into some top level CL space > - include it with every Seam app > Which doesn't sound that bad - since all deployments should be automatic anyway (ant, maven2, ...). > PETE: > Any other ideas? We could merge this into seam core and select the scanner as needed... > ALES: > OK, this simplifies things. > You do this via reflection - catching the first one that works. > It's the criteria of what we need that it's the problem. > At least I remember we had some issues determining weather we're running in AS5 or Embedded. > But yeah, we can give it another shot. -- 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

17 years, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Moved: (JBSEAM-3050) Move Seam scanner code into AS

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-3050?page=all ] Pete Muir moved JBAS-5561 to JBSEAM-3050: ----------------------------------------- Project: Seam (was: JBoss Application Server) Key: JBSEAM-3050 (was: JBAS-5561) Fix Version/s: 2.0.x 2.1.0.BETA1 (was: JBossAS-5.1.0.CR1) > Move Seam scanner code into AS > ------------------------------ > > Key: JBSEAM-3050 > URL: http://jira.jboss.com/jira/browse/JBSEAM-3050 > Project: Seam > Issue Type: Task > Components: Platform interoperability > Reporter: Stan Silvert > Assigned To: Pete Muir > Fix For: 2.0.x, 2.1.0.BETA1 > > > We need to move the Seam scanner code that Ales wrote into AS5 so that you don't have to deploy jboss-seam-jbas5.jar in your Seam project. > Discussion thus far: > ALES: > How are you planning on solving the classloading issue there? > e.g. > if the custom Seam/AS5 scanning code is in AS5, but still references some Seam code, which is deployed as part of Seam app > PETE: > Hmm, we discussed splitting out the Scanner interface into an SPI, but I'm not sure that is a great idea as it will result in a proliferation of jars and confusion. > ALES: > I'm always in favor of this. > More jars or not, having proper spi is always better then some tight integration. > But then this means that people have to either > - put this spi + plugins into some top level CL space > - include it with every Seam app > Which doesn't sound that bad - since all deployments should be automatic anyway (ant, maven2, ...). > PETE: > Any other ideas? We could merge this into seam core and select the scanner as needed... > ALES: > OK, this simplifies things. > You do this via reflection - catching the first one that works. > It's the criteria of what we need that it's the problem. > At least I remember we had some issues determining weather we're running in AS5 or Embedded. > But yeah, we can give it another shot. -- 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

17 years, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2779) Support for a single namespace across multiple packages

by Shane Bryzak (JIRA)

Support for a single namespace across multiple packages ------------------------------------------------------- Key: JBSEAM-2779 URL: http://jira.jboss.com/jira/browse/JBSEAM-2779 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Assigned To: Pete Muir Fix For: 2.1.0.BETA1 Within the Security API we currently have 3 different packages/namespaces: security, security/management and security/permission. This is starting to clutter up components.xml with all the additional required namespace definitions, so it would be nice if we could consolidate them all into a single namespace (org.jboss.seam.security). -- 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

17 years, 10 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2008