January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2143) Hotdeployed components can't be configured through components.xml

by Pete Muir (JIRA)

Hotdeployed components can't be configured through components.xml ----------------------------------------------------------------- Key: JBSEAM-2143 URL: http://jira.jboss.com/jira/browse/JBSEAM-2143 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Critical Fix For: 2.0.1.GA he hot deployment scanner is isolated, using a URLClassloader that is not available once that method comes to a close. The only way to make this work would be to keep that classloader alive during the rest of the startup process. I can direct you to the line of code that you need to look at if you are curious about it. Check out lines 540 and 541 or org.jboss.seam.init.Initialiation. The scanForHotDeployableComponents uses the following logic to create a component scanner: URL[] urls = { url }; classLoader = new URLClassLoader(urls, Thread.currentThread().getContextClassLoader()); paths = new File[] { directory }; Once it processes the classes, that classloader is discarded and obviously, since it is a URLclassloader, the classes aren't going to be found later on. -- 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, 8 months

4
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2381) EntityQuery to stop fetching maxResults + 1 rows

by Brian Kalbfus (JIRA)

EntityQuery to stop fetching maxResults + 1 rows ------------------------------------------------ Key: JBSEAM-2381 URL: http://jira.jboss.com/jira/browse/JBSEAM-2381 Project: JBoss Seam Issue Type: Feature Request Components: EJB3 Affects Versions: 2.0.1.CR1, 2.0.0.GA Reporter: Brian Kalbfus In using a hibernate interceptor to audit instantiating entities, I noticed one extra record in excess of getMaxResults() is instantiated that isn't used - thus rendering a false audit. This was because of the following code in EntityQuery (copied from CVS head): <code> protected javax.persistence.Query createQuery() { parseEjbql(); evaluateAllParameters(); joinTransaction(); javax.persistence.Query query = getEntityManager().createQuery( getRenderedEjbql() ); setParameters( query, getQueryParameterValues(), 0 ); setParameters( query, getRestrictionParameterValues(), getQueryParameterValues().size() ); if ( getFirstResult()!=null) query.setFirstResult( getFirstResult() ); if ( getMaxResults()!=null) query.setMaxResults( getMaxResults()+1 ); //add one, so we can tell if there is another page if ( getHints()!=null ) { for ( Map.Entry<String, String> me: getHints().entrySet() ) { query.setHint(me.getKey(), me.getValue()); } } return query; } </code> Specifically: if ( getMaxResults()!=null) query.setMaxResults( getMaxResults()+1 ); //add one, so we can tell if there is another page The code says it is adding one so that it knows if there is another page. I see its use here: <code> public boolean isNextExists() { return resultList!=null && resultList.size() > getMaxResults(); } </code> I propose this for isNextExists(): <code> public boolean isNextExists() { return getResultCount() > (getFirstResult()!=null?getFirstResult():0) + getMaxResults(); } </code> Then we can change that line in createQuery() to: if ( getMaxResults()!=null) query.setMaxResults( getMaxResults() ); I did this in my subclass by overriding these two methods for my project; I had to copy in some of the private members of EntityQuery to do this. Thanks, Brian Kalbfus -- 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, 8 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1909) ajax4jsf:command pageflow action rerender

by Tomislav Jakopec (JIRA)

ajax4jsf:command pageflow action rerender ----------------------------------------- Key: JBSEAM-1909 URL: http://jira.jboss.com/jira/browse/JBSEAM-1909 Project: JBoss Seam Issue Type: Feature Request Reporter: Tomislav Jakopec When I use ajax4jsf:commandButton calling bean action rerender of components is working fine, but when I call pageflow action entire page is reloaded instead of rerender of particular component I created example application to show the problem. You could downloaded from: http://popovac.hr/orka/test.ear I reported this issue on RichFaces JIRA and they said that should be future request on SEAM, so here it is. -- 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, 8 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2035) Better handling of empty extended EL method expressions in pages.xml

by Pete Muir (JIRA)

Better handling of empty extended EL method expressions in pages.xml -------------------------------------------------------------------- Key: JBSEAM-2035 URL: http://jira.jboss.com/jira/browse/JBSEAM-2035 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Fix For: 2.0.x Currently you have to match a call to #{foo.bar()} with an from-action="#{foo.bar()}" - it probably makes sense to relax this restriction -- 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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2254) Wrong behaviour using a4j:include and pages.xml navigation

by Konstantin Grigoriev (JIRA)

Wrong behaviour using a4j:include and pages.xml navigation ---------------------------------------------------------- Key: JBSEAM-2254 URL: http://jira.jboss.com/jira/browse/JBSEAM-2254 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.GA Environment: JBoss Seam 2.0.0.G.A. RichFaces 3.1.2.G.A. JBossAS 4.2.2.G.A. Reporter: Konstantin Grigoriev Parent page includes firstTest.xhtml using a4j:include. firstTest.xhtml contains button: <a4j:commandButton action="next" value="next" /> Navigation in pages.xhtml: <page view-id="firstTest.xhtml"> <navigation> <rule if-outcome="next"> <redirect view-id="secondTest.xhtml" /> </rule> </navigation> </page> After pressing button whole page navigates to secondTest.xhtml, not only "a4j:include" element. In case of using faces-config.xml everything is ok. -- 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, 8 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2283) Seam-gen library usage

by Pete Muir (JIRA)

Seam-gen library usage ---------------------- Key: JBSEAM-2283 URL: http://jira.jboss.com/jira/browse/JBSEAM-2283 Project: JBoss Seam Issue Type: Task Components: Tools Affects Versions: 2.0.0.GA Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.1.GA Seam-gen duplicates a few libraries from /lib - dates from when Seam shipped with a very old hibernate and -all.jars -- 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, 8 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2090) Improve handling of h:selectManyXXX updating the mode with a new list

by Pete Muir (JIRA)

Improve handling of h:selectManyXXX updating the mode with a new list --------------------------------------------------------------------- Key: JBSEAM-2090 URL: http://jira.jboss.com/jira/browse/JBSEAM-2090 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.x Currently JSF sets a new list on the model which causes a load of deletes and inserts. Perhaps we can handle this better (dunno how) -- 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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2525) Split out Spring and microcontainer support into separate jars

by Pete Muir (JIRA)

Split out Spring and microcontainer support into separate jars -------------------------------------------------------------- Key: JBSEAM-2525 URL: http://jira.jboss.com/jira/browse/JBSEAM-2525 Project: JBoss Seam Issue Type: Task Components: Build Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.GA -- 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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2422) Rendering Email from a servlet

by Tim Timson (JIRA)

Rendering Email from a servlet ------------------------------ Key: JBSEAM-2422 URL: http://jira.jboss.com/jira/browse/JBSEAM-2422 Project: JBoss Seam Issue Type: Bug Components: Mail Environment: Windows Glassfish server Reporter: Tim Timson Assigned To: Pete Muir Pete Muir asked me to created this issue when I posted this forum entry: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=126443 -- 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, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1266) Mathematical captcha & Email obfuscator

by Stephan Kleine (JIRA)

Mathematical captcha & Email obfuscator --------------------------------------- Key: JBSEAM-1266 URL: http://jira.jboss.com/jira/browse/JBSEAM-1266 Project: JBoss Seam Issue Type: Patch Affects Versions: 1.3.0.BETA1 Environment: Tested with Seam CVS on JBoss AS 4.2.0CR2 Reporter: Stephan Kleine Hello, I would like to donate some stuff to seam: 1. A component that converts strings into (hexa)decimal html entities. 2. A tag to use this obfuscator (mainly a shortcut for h:outputText escape="false" ...). 3. A mathematical captcha that asks for the solutions of simple equations (like they use at jroller). The equation can be obuscated with the tag described at 2.. 4. A tag to obfuscate email addresses (see [url]http://www.seowebsitepromotion.com/obfuscate_email.asp[/url] for more details). Would be great if you include it in 1.3 ;) Regards Stephan -- 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, 8 months

4
12
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008