June 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1818) Patch proposed to LocaleSelector

by Marco Pancotti (JIRA)

Patch proposed to LocaleSelector -------------------------------- Key: JBSEAM-1818 URL: http://jira.jboss.com/jira/browse/JBSEAM-1818 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Marco Pancotti Priority: Minor org.jboss.seam.international.LocaleSelector does not implement a getDefaultLocale method. I think it can be useful in a multi-language application. So I propose to apply the following patch in the LocaleSelector class adding the following methods (it can be more complex if you want orthogonal returns respect the return of the specified locale): public Locale getDefaultLocale(){ return FacesContext.getCurrentInstance().getApplication().getDefaultLocale() ; } public String getDefaultLocaleLanguage(){ return FacesContext.getCurrentInstance().getApplication().getDefaultLocale() .getLanguage(); } Marco Pancotti -- 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, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2675) Search superclasses of components for @Interceptor

by Clint Popetz (JIRA)

Search superclasses of components for @Interceptor -------------------------------------------------- Key: JBSEAM-2675 URL: http://jira.jboss.com/jira/browse/JBSEAM-2675 Project: JBoss Seam Issue Type: Feature Request Reporter: Clint Popetz Attachments: component-superclass-interceptors.diff Currently Component.initInterceptors doesn't search superclasses of the bean class for an @Interceptors annotation. This patch adds that functionality. -- 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, 8 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3106) Enable "@In QuartzTriggerHandle timer" in currently running Job.

by Cloves Almeida (JIRA)

Enable "@In QuartzTriggerHandle timer" in currently running Job. ---------------------------------------------------------------- Key: JBSEAM-3106 URL: http://jira.jboss.com/jira/browse/JBSEAM-3106 Project: Seam Issue Type: Patch Components: Async Affects Versions: 2.0.2.GA Environment: Any Reporter: Cloves Almeida When using EJB Timer, the "timer" event context variable is accessible during the currently executing job, returning a javax.ejb.Timer. This enables the executing timer to cancel itself. This patch does the equivalent for Quartz, populating the variable with a QuartzTriggerHandle. -- 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, 8 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3120) SeamCollectionModel in Seam-Trinidad example is not handling the sorting in the most efficient way

by Alex Savitsky (JIRA)

SeamCollectionModel in Seam-Trinidad example is not handling the sorting in the most efficient way -------------------------------------------------------------------------------------------------- Key: JBSEAM-3120 URL: http://jira.jboss.com/jira/browse/JBSEAM-3120 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.3.CR1 Reporter: Alex Savitsky Priority: Optional The way the sorting is handled in SeamCollectionModel, is not anywhere near optimal. I undernstand that this is only an example, but since people often just paste this into the real apps, it might as well be a little more polished. The way the setSortCriteria is coded up, a new query will be issued every time this method is called, as Query.setOrder triggers an automatic refresh(), which wipes out the data model in the process - thus forcing the creation of a new one, which won't have the criteria property set. -- 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, 8 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3008) Page fragment caching impossible with coarse-grained rendered attribute evaluation in JSF

by Christian Bauer (JIRA)

Page fragment caching impossible with coarse-grained rendered attribute evaluation in JSF ----------------------------------------------------------------------------------------- Key: JBSEAM-3008 URL: http://jira.jboss.com/jira/browse/JBSEAM-3008 Project: Seam Issue Type: Task Components: JSF Controls, JSF Integration Reporter: Christian Bauer The evaluation of the JSF rendered="true|false" attribute conflicts with the Seam page fragment cache. <s:cache region="test" key="foo123"> <h:outputText value="FOO" rendered="#{foo.bar}"/> </s:cache> The rendered attribute of the child components is ALWAYS evaluated, in potentially any JSF phase (especially APPLY REQUEST VALUES and RENDER RESPONSE of course). No switch or combination of JSF component settings and renderers is able to stop that evaluation; you can not say "Do not call isRendered() on any child component of <s:cache>". So any rendered-attribute expression that is costly (e.g. rendered="#{not empty myBackingBean.resultList}") will not be cached. This also means that there is a disconnect between what is finally rendered by s:cache (some HTML from the cache) and what the evaluation of the rendered attribute might produce. This is extremely difficult to work around. One approach is to only use lightweight rendered="#{foo}" expressions that can be evaluated many times without much cost. I don't see any way to fix this unless the JSF specification is changed and a more sane model of rendering/non-rendering switches is introduced. The rendered attribute is used for all kinds of purposes inside the JSF engine, most of them have nothing to do with rendering (e.g. it is used in APPLY REQUEST VALUES to detect which bindings need to be evaluated back onto the model). -- 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, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2341) Some corrections for a Portal Compability.

by Alexander Smirnov (JIRA)

Some corrections for a Portal Compability. ------------------------------------------ Key: JBSEAM-2341 URL: http://jira.jboss.com/jira/browse/JBSEAM-2341 Project: JBoss Seam Issue Type: Patch Affects Versions: 2.0.0.GA Environment: Jboss AS 4.2.0 , Jboss Portal 2.6.2, Seam 2.0.1-SNAPSHOT Reporter: Alexander Smirnov Assigned To: Pete Muir Fix For: 2.0.1.GA Fixes : - remove URL decoding from parameters, to avoid double encoding. - Fix PhaseListener for a portal lifecycle -- 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, 8 months

4
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2987) HibernateEntityQuery fails when using a Collection as a parameter in an restriction

by Scott Olcott (JIRA)

HibernateEntityQuery fails when using a Collection as a parameter in an restriction ----------------------------------------------------------------------------------- Key: JBSEAM-2987 URL: http://jira.jboss.com/jira/browse/JBSEAM-2987 Project: Seam Issue Type: Bug Components: Framework Affects Versions: 2.1.0.A1, 2.0.2.CR2 Environment: hibernate/tomcat Reporter: Scott Olcott HibernateEntityQuery fails when using a Collection object as a parameter in an restriction. The private setParameters method in HibernateEntityQuery does not check to see if the parameter is a Collection before calling query.setParameter(name,value). In plain hibernate it needs to call the query.setParameterList method instead of the setParameter method. When passing a List as a parameter to a restriction a ClassCastException is thrown. This is not an issue when using EntityQuery, because in JPA the setParameter method on org.hibernate.ejb.QueryImpl takes care of this for you. -- 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, 8 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1623) Problems with rendering emails with seam-email and IceFaces 1.6

by Karol Oslowski (JIRA)

Problems with rendering emails with seam-email and IceFaces 1.6 --------------------------------------------------------------- Key: JBSEAM-1623 URL: http://jira.jboss.com/jira/browse/JBSEAM-1623 Project: JBoss Seam Issue Type: Bug Components: ICE Faces Integration Affects Versions: 1.2.1.GA Environment: JBoss AS 4.0.5 GA with EJB3 installed (1.2.0.GA), project with Seam 1.2.1 GA, Reporter: Karol Oslowski Assigned To: Gregory Dick Bug is quite simple to replicate. All u have to do is install jboss with ejb3 from the net installer http://labs.jboss.com/jemsinstaller/downloads version 1.2.0.GA. You also have to get the example applications from seam 1.2.1 GA, You have to configure the mail example as described in jboss forum linked to this bug and when trying to send an email there will be such exception: 04:18:32,140 INFO [MailSession] Creating JavaMail Session (l***:) 04:18:32,156 INFO [MailSession] connected to mail server 04:18:32,250 ERROR [MailExample] Error sending mail java.lang.NullPointerException at org.jboss.seam.mail.ui.UIMessage.getCharset(UIMessage.java:242) at org.jboss.seam.mail.ui.AddressComponent.getInternetAddress(AddressComponent.java:29) at org.jboss.seam.mail.ui.UIFrom.encodeBegin(UIFrom.java:27) at org.jboss.seam.ui.JSF.renderChild(JSF.java:171) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.mail.ui.UIMessage.encodeChildren(UIMessage.java:159) at org.jboss.seam.ui.JSF.renderChild(JSF.java:174) at org.jboss.seam.ui.JSF.renderChildren(JSF.java:162) at org.jboss.seam.ui.facelet.FaceletsRenderer.renderFacelet(FaceletsRenderer.java:150) at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:112) at org.jboss.seam.example.mail.MailExample.send(MailExample.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 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:20) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:57) at org.jboss.seam.interceptors.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:47) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:37) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:34) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:27) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:103) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:151) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:87) at org.jboss.seam.example.mail.MailExample_$$_javassist_19.send(MailExample_$$_javassist_19.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.el.parser.AstValue.invoke(AstValue.java:174) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:286) at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69) at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:63) at javax.faces.component.UICommand.broadcast(UICommand.java:106) at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168) at org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86) at com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.renderCycle(ReceiveSendUpdates.java:57) at com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.service(ReceiveSendUpdates.java:45) at com.icesoft.faces.webapp.http.core.IDVerifier.service(IDVerifier.java:25) at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16) at com.icesoft.faces.webapp.http.servlet.ViewBoundAdaptingServlet.service(ViewBoundAdaptingServlet.java:44) at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) at com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet.service(MainSessionBoundServlet.java:97) at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:35) at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52) at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29) at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:359) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:54) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) -- 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, 8 months

2
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1146) Include optional Ant build-${profile}.xml in seam-gen/build-scripts

by Stephan Heffner (JIRA)

Include optional Ant build-${profile}.xml in seam-gen/build-scripts ------------------------------------------------------------------- Key: JBSEAM-1146 URL: http://jira.jboss.com/jira/browse/JBSEAM-1146 Project: JBoss Seam Issue Type: Patch Affects Versions: 1.2.1.GA Reporter: Stephan Heffner Attachments: build.xml  <import file="build-${profile}.xml" optional="true"/> -- 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, 8 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2773) JPA example on Tomcat 6.X throws a NoClassDefFoundError: org/objectweb/asm/Type

by Jay Balunas (JIRA)

JPA example on Tomcat 6.X throws a NoClassDefFoundError: org/objectweb/asm/Type ------------------------------------------------------------------------------- Key: JBSEAM-2773 URL: http://jira.jboss.com/jira/browse/JBSEAM-2773 Project: JBoss Seam Issue Type: Bug Components: Examples, Platform interoperability Affects Versions: 2.0.2.GA Environment: Tomcat 6.0.16 Java 1.5 Linux fedora 8 x86 Reporter: Jay Balunas Assigned To: Jay Balunas Fix For: 2.0.2.GA, 2.1.0.BETA1 Follow the instructions for the JPA example deploying to tomcat 6.0. When deploying the JPA example you will see the exception below. Caused by: java.lang.NoClassDefFoundError: org/objectweb/asm/Type at net.sf.cglib.core.TypeUtils.parseType(TypeUtils.java:180) at net.sf.cglib.core.KeyFactory.<clinit>(KeyFactory.java:66) at net.sf.cglib.proxy.Enhancer.<clinit>(Enhancer.java:69) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:117) at org.hibernate.proxy.pojo.cglib.CGLIBProxyFactory.postInstantiate(CGLIBProxyFactory.java:43) at org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:162) at org.hibernate.tuple.entity.AbstractEntityTuplizer.<init>(AbstractEntityTuplizer.java:135) at org.hibernate.tuple.entity.PojoEntityTuplizer.<init>(PojoEntityTuplizer.java:55) at org.hibernate.tuple.entity.EntityEntityModeToTuplizerMapping.<init>(EntityEntityModeToTuplizerMapping.java:56) at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:295) at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434) at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:109) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:730) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:121) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60) at org.jboss.seam.persistence.EntityManagerFactory.createEntityManagerFactory(EntityManagerFactory.java:81) at org.jboss.seam.persistence.EntityManagerFactory.startup(EntityManagerFactory.java:50) ... 38 more -- 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, 8 months

3
5
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 June 2008