November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2216) build.xml from seam-gen tries copying janino with bad pattern

by Leo Baschy (JIRA)

build.xml from seam-gen tries copying janino with bad pattern ------------------------------------------------------------- Key: JBSEAM-2216 URL: http://jira.jboss.com/jira/browse/JBSEAM-2216 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: any Reporter: Leo Baschy >From seam-gen (for an .ear project) the build.xml where it is trying to copy lib/janino.jar instead it incorrectly says <include name="lib/janino-*.jar"/> which doesn't work because of the "-". -- 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, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2218) Re-evaluation of filter parameters for persistence contexts

by Christian Bauer (JIRA)

Re-evaluation of filter parameters for persistence contexts ----------------------------------------------------------- Key: JBSEAM-2218 URL: http://jira.jboss.com/jira/browse/JBSEAM-2218 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Minor I use a filter with a Seam-managed persistence context, the filter parameter is #{currentAccessLevel}. This expression is evaluated when the managed PC is created, in ManagedPersistenceContext.initEntityManager(). There is currently no way to re-evaluate that filter condition after the SMPC has been created. This leads to problems in the following scenario: - #{currentAccessLevel} = 0 when no user is logged in - #{currentAccessLevel} = 1000 when a user logs in (which requires database queries, so the SMPC is created) - certain backing beans observe the postAuthenticate event and refresh their state from the database, supposedly with the new #{currentAccessLevel} permission The backing beans that are called in postAuthenticate get the SMPC that was instantiated with #{currentAccesslevel} = 0. A relatively easy solution would be a new @Observer method on ManagedPersistenceContext and a new "org.jboss.seam.resetPersistenceContextFilterParameter" event I could call manually after authentication. -- 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, 2 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1987) <restrict> in pages.xml has no effect

by Samuel Mendenhall (JIRA)

<restrict> in pages.xml has no effect ------------------------------------- Key: JBSEAM-1987 URL: http://jira.jboss.com/jira/browse/JBSEAM-1987 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.0.CR1 Reporter: Samuel Mendenhall Assigned To: Shane Bryzak Priority: Critical Default seam-gen'd project Create a page called restricted.xhtml Add to pages.xml: <page view-id="/restricted.xhtml" login-required="true"> <restrict>#{s:hasRole('doesNotExist')}</restrict> </page> Logging in will by default give the user the 'admin' role, but the user can still access the page even without the doesNotExist role. -- 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, 2 months

4
4
0 / 0

[jbossseam-issues] seam-gen generate-entities and mysql

by Morten Matras

I'm trying to reverse engineer an application using seam-gen generate-entities from a mysql database and get some errors that's related to the column types. The database is generated from a Hibernate based webapplication or EJB3 based application. (I'm trying two different applications). I get errors like: "Wrong column type: description, expected: varchar(65535)" if the property is a string with type = "text" So what is mapped like this in the original hibernate project: @Type(type="text") can't be reverse engineered back to the same type. Any ideas on how to proceed / avoid these column type problems. -- Morten Matras Udviklingschef GAMP media og Blob Communication ApS Vindegade 99-103 5000 Odense C Tlf: 61711103 E: morten(a)gampmedia.dk T: 76 654321 W: www.blobcom.com E: morten(a)blobcom.com

17 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1589) Add s:selectItems itemValue attribute

by Sergey Koshcheyev (JIRA)

Add s:selectItems itemValue attribute ------------------------------------- Key: JBSEAM-1589 URL: http://jira.jboss.com/jira/browse/JBSEAM-1589 Project: JBoss Seam Issue Type: Patch Components: JSF Reporter: Sergey Koshcheyev Attachments: selectItems-itemValue.patch I have implemented itemValue attribute for s:selectItems, to be used like this: <h:selectOneMenu value="#{entityId}" required="false"> <s:selectItems value="#{listOfEntities}" var="entity" label="#{entity.name}" itemValue="#{entity.id}" /> </h:selectOneMenu> -- 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, 2 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-188) s:constant

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-188?page=all ] Pete Muir closed JBSEAM-188. ---------------------------- Resolution: Out of Date We now have extended EL so this is no longer an issue > s:constant > ---------- > > Key: JBSEAM-188 > URL: http://jira.jboss.com/jira/browse/JBSEAM-188 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > > It's useful to be able to pass a constant value to an action, ie: > <s:constant value="#{foo.bar}" constantValue="100"/> > <h:commandButton action="#{foo.execute}" value="Do something"/> -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2176) Typo in Chapter 13.8. : ending slash in empty tag missing

by Mark Schmatz (JIRA)

Typo in Chapter 13.8. : ending slash in empty tag missing --------------------------------------------------------- Key: JBSEAM-2176 URL: http://jira.jboss.com/jira/browse/JBSEAM-2176 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 2.0.0.CR3 Reporter: Mark Schmatz Priority: Trivial The first code box: <page view-id="/login.xhtml" scheme="https"> doesn't have the ending slash. -- 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, 2 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2213) Add framework/annotations to expose component properties via JMX

by Allon Rauer (JIRA)

Add framework/annotations to expose component properties via JMX ---------------------------------------------------------------- Key: JBSEAM-2213 URL: http://jira.jboss.com/jira/browse/JBSEAM-2213 Project: JBoss Seam Issue Type: Feature Request Reporter: Allon Rauer I often find myself wanting to change component state, in particular configuration settings. i'm forced to either whip up some one-off xhtml to accomplish the task, or modify config files and redeploy. it would be very nice, however, to be able to accomplish this via JMX. seems like it would be a convenient and easy-to-do feature for application-scoped components. -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1140) javassist in Seam 1.2.1 GA duplicate method error

by Luiz Augusto Ruiz (JIRA)

javassist in Seam 1.2.1 GA duplicate method error ------------------------------------------------- Key: JBSEAM-1140 URL: http://jira.jboss.com/jira/browse/JBSEAM-1140 Project: JBoss Seam Issue Type: Bug Reporter: Luiz Augusto Ruiz -- 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, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2208) actions unresolved as a parameter, is an error?

by Francisco Philip (JIRA)

actions unresolved as a parameter, is an error? ----------------------------------------------- Key: JBSEAM-2208 URL: http://jira.jboss.com/jira/browse/JBSEAM-2208 Project: JBoss Seam Issue Type: Feature Request Reporter: Francisco Philip LoginForm.java .... public String login(){ identity.login(); } .... login.xhtml ... <ui:include src="/incl/command-panel.xhtml"> <ui:param name="actionId" value="loginButton"/> <ui:param name="actionMessage" value="Login"/> <ui:param name="actionCommand" value="#{login.login}"/> </ui:include> ... command-panel.xhtml .... <h:commandButton id="#{actionId}" action="#{actionCommand}" value="#{actionMessage}"/> .... and the error is : Property 'login' not found on type package....LoginForm_$$_javassist_?? -- 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, 2 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007