December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2414) Render swing components to PDF

by Norman Richards (JIRA)

Render swing components to PDF ------------------------------ Key: JBSEAM-2414 URL: http://jira.jboss.com/jira/browse/JBSEAM-2414 Project: JBoss Seam Issue Type: Feature Request Reporter: Norman Richards Assigned To: Norman Richards Fix For: 2.0.1.GA Implementation at http://chiralsoftware.com/blog/JBoss-Seam-iText-PDF-custom-JSF-4642a90cb4... -- 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

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1974) NPE in Tomcat parseParameters()

by Christian Bauer (JIRA)

NPE in Tomcat parseParameters() ------------------------------- Key: JBSEAM-1974 URL: http://jira.jboss.com/jira/browse/JBSEAM-1974 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor This is still a mystery, only occurs from time to time on the production site. Google says that this might be related to the 64 bit VM, others say that the lifecycle of the request object usage is wrong. The crazy part is that the Authenticator component doesn't even have any @RequestParameter anymore, so no idea why Seam wants to inject it. Caused by: java.lang.NullPointerException at org.apache.catalina.connector.Request.parseParameters(Request.java:2409) at org.apache.catalina.connector.Request.getParameterNames(Request.java:1073) at org.apache.catalina.connector.Request.getParameterMap(Request.java:1053) at org.apache.catalina.connector.RequestFacade.getParameterMap(RequestFacade.java:414) at org.jboss.seam.mock.MockExternalContext.getRequestParameterValuesMap(MockExternalContext.java:301) at org.jboss.seam.faces.Parameters.getRequestParameters(Parameters.java:61) at org.jboss.seam.Component.injectParameters(Component.java:1449) at org.jboss.seam.Component.inject(Component.java:1419) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:45) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91) at org.jboss.seam.wiki.core.action.Authenticator_$$_javassist_12.getGuestAccessLevel(Authenticator_$$_javassist_12.java) at sun.reflect.GeneratedMethodAccessor233.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2083) at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1927) at org.jboss.seam.Component.getInstance(Component.java:1864) at org.jboss.seam.Component.getInstance(Component.java:1841) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50) at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166) at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:112) at org.jboss.seam.persistence.HibernatePersistenceProvider.enableFilter(HibernatePersistenceProvider.java:149) at org.jboss.seam.persistence.ManagedPersistenceContext.initEntityManager(ManagedPersistenceContext.java:88) at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManager(ManagedPersistenceContext.java:108) at sun.reflect.GeneratedMethodAccessor98.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2083) at org.jboss.seam.Component.unwrap(Component.java:2109) at org.jboss.seam.Component.getInstance(Component.java:1888) at org.jboss.seam.Component.getInstance(Component.java:1841) at org.jboss.seam.Component.getInstanceInAllNamespaces(Component.java:2183) at org.jboss.seam.Component.getValueToInject(Component.java:2135) at org.jboss.seam.Component.injectAttributes(Component.java:1599) at org.jboss.seam.Component.inject(Component.java:1417) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:45) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91) at org.jboss.seam.wiki.core.dao.FeedDAO_$$_javassist_10.findFeed(FeedDAO_$$_javassist_10.java) at org.jboss.seam.wiki.core.ui.FeedServlet.doGet(FeedServlet.java:56) -- 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

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1256) Interactive preview is killing conversation and throws ERRORs on the log

by Christian Bauer (JIRA)

Interactive preview is killing conversation and throws ERRORs on the log ------------------------------------------------------------------------ Key: JBSEAM-1256 URL: http://jira.jboss.com/jira/browse/JBSEAM-1256 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Two issues with document editing and the interactive preview feature: - Sometimes I get kicked out of the editor with "No conversation or concurrent request", luckily I can still switch back to the editor after that. Gavins guess is that ajax4jsf doesn't queue the events and that the key press event is sometimes processed concurrently. Need to test that, hard to reproduce. - The wiki text parser writes anything it doesn't like to STDERR, which fills up the log when you type. -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1475) Incorporate IceFaces in Seam Gen

by Michael Yuan (JIRA)

Incorporate IceFaces in Seam Gen -------------------------------- Key: JBSEAM-1475 URL: http://jira.jboss.com/jira/browse/JBSEAM-1475 Project: JBoss Seam Issue Type: Feature Request Components: ICE Faces Integration Reporter: Michael Yuan Assigned To: Michael Yuan Fix For: 1.3.0.BETA1 I am contacted by Ted Goddard from IceFaces to incorporate icefaces into Seam gen. What they did was to add a "icefaces" directory in seam-gen, which contains the icefaces build scripts and view templates. We then need to patch the seam-gen/build.xml file to ask icefaces related setup questions and invoke the icefaces scripts. Here are the icefaces directory and the modified build.xml they have. If no one objects, I will incorporate it into Seam CVS: http://anonsvn.icefaces.org/repo/projects/icefaces-seam-gen/trunk/seam-ge... http://anonsvn.icefaces.org/repo/projects/icefaces-seam-gen/trunk/seam-ge... Thanks. -- 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

6
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2439) Exception rules in pages.xml redirect to a 404 page if redirect destination isn't in web root.

by Fijai Cairo (JIRA)

Exception rules in pages.xml redirect to a 404 page if redirect destination isn't in web root. ---------------------------------------------------------------------------------------------- Key: JBSEAM-2439 URL: http://jira.jboss.com/jira/browse/JBSEAM-2439 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.GA Environment: JBoss 4.20 GA/ JBoss 4.22 GA, OSX 10.5.1, JRE 1.5.0_13 Reporter: Fijai Cairo Exception redirections rules in pages.xml to error pages that reside anywhere besides the web root always yield a 404 page. This rule in pages.xml works. When the exception is raised, the user is redirected to the correct error page <exception class="com.myApp.exception.GatewayException"> <redirect view-id="/gatewayerror.xhtml"> <message>GatewayException.</message> </redirect> </exception> This rule doesn't work. I have the error file in a directory named "errors". When the exception is raised, the user is directed to a 404 page even though the Url reflects the right path. <exception class="com.myApp.exception.GatewayException"> <redirect view-id="/errors/gatewayerror.xhtml"> <message>GatewayException.</message> </redirect> </exception> -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2376) eclipseclasspath task broken for windows

by Matt Drees (JIRA)

eclipseclasspath task broken for windows ----------------------------------------- Key: JBSEAM-2376 URL: http://jira.jboss.com/jira/browse/JBSEAM-2376 Project: JBoss Seam Issue Type: Bug Components: Build Affects Versions: 2.0.0.GA Reporter: Matt Drees Priority: Minor The eclipseclasspath task in Seam's build.xml file creates an invalid .classpath file on windows. For example, a generated classpath line looks like this: <classpathentry kind="lib" path="C:Documents and Settingsmatthew.drees.m2repositoryjavaxjmsjms1.1jms-1.1.jar"/> I did some debugging, and the removal of forward slashes occurs here: (EclipseClasspathTask.java line 77) line = line.replaceFirst("@" + filterProperty + "@", eclipsepaths); It turns out String.replaceFirst treats forward slashes in the second argument as escape characters. (see http://forum.java.sun.com/thread.jspa?threadID=626091&messageID=3574350 and http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Matcher.html#appe... ) An easy solution is to use String.replace instead of String.replaceFirst. -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2316) EntityHome#getEntityClass() returns EntityManager.class rather than entity class

by Dan Allen (JIRA)

EntityHome#getEntityClass() returns EntityManager.class rather than entity class -------------------------------------------------------------------------------- Key: JBSEAM-2316 URL: http://jira.jboss.com/jira/browse/JBSEAM-2316 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Dan Allen Priority: Minor Fix For: 2.0.1.GA This is a strange one. The getEntityClass() is returning the wrong type parameter. It should be returning the first but it is instead returning the second. You will discover that this assertion fails. assert new EntityHome<SimpleEntity>().getEntityClass() == SimpleEntity.class; -- 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

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2391) s:link Enhanced EL support issue

by Samuel Mendenhall (JIRA)

s:link Enhanced EL support issue -------------------------------- Key: JBSEAM-2391 URL: http://jira.jboss.com/jira/browse/JBSEAM-2391 Project: JBoss Seam Issue Type: Bug Components: EL Reporter: Samuel Mendenhall Using: <h:commandLink id="someId" value="Some Action" action="#{someBean.execute(thisObject)}" /> and <s:link id="someId" value="Some Action" action="#{someBean.execute(thisObject)}" /> s:link always passes null to the execute method instead of the thisObject value while h:commandLink always has the correct non-null value of the object. My testing was done with s:link and h:commandLink in a column in a dataTable with the thisObject being the var and the execute method being on the backing bean that also hosted the dataTable information. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1734) Document behavior of s:link and @DataModel

by Christian Bauer (JIRA)

Document behavior of s:link and @DataModel ------------------------------------------ Key: JBSEAM-1734 URL: http://jira.jboss.com/jira/browse/JBSEAM-1734 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Christian Bauer Priority: Blocker This behavior in the Hotel Booking example: @DataModel private List<Hotel> hotels; <h:dataTable id="hotels" value="#{hotels}" var="hot" rendered="#{hotels.rowCount>0}"> <s:link id="viewHotel" value="View Hotel" action="#{hotelBooking.selectHotel(hot)}"/> is becoming an FAQ. To counter that, explain in the documentation section about s:link that it can detect if it is rendered in a datatable, and that the URL for the resulting GET request (no form, no POST, no tree) contains a magic token that is used to pull the value out of the datamodel in the next INVOKE_APPLICATION phase. The whole procedure, from rendering, to request, to processing, needs to be explained in detail. Explain why it doesn't work in general and why you can't pass "objects as arguments" in EL across requests. Add this explanation also to the section in the "EL Enhancements" chapter, which already mentions this issue. Since this is the most important master/detail navigation concept, this is a blocker. -- 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

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2442) Event notification of conversation-timeout

by Jacob Orshalick (JIRA)

Event notification of conversation-timeout ------------------------------------------ Key: JBSEAM-2442 URL: http://jira.jboss.com/jira/browse/JBSEAM-2442 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Jacob Orshalick Priority: Trivial Currently events are provided for both beginning and ending of a conversation, but there is no way to know when a conversation times out. It would be nice to have an event: org.jboss.seam.timeoutConversation which sends the conversationId along the way. Thanks. -- 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
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007