December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3571) provide control to destroy a conversation on debug page

by Dan Allen (JIRA)

provide control to destroy a conversation on debug page ------------------------------------------------------- Key: JBSEAM-3571 URL: https://jira.jboss.org/jira/browse/JBSEAM-3571 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.CR1 Reporter: Dan Allen Assignee: Dan Allen Priority: Minor Fix For: 2.1.0.GA It would be convenient to be able to destroy a conversation from the debug page, in addition to inspect it. Also, it would be helpful if a column was added to show if a conversation is nested. I also noticed that on Firefox, when you click on an expanded context node the first time, it does nothing. There is a bug in how the "current style" is read in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3612) examples should demonstrate obtaining entity manager factory from JNDI via persistence unit reference

by Dan Allen (JIRA)

examples should demonstrate obtaining entity manager factory from JNDI via persistence unit reference ----------------------------------------------------------------------------------------------------- Key: JBSEAM-3612 URL: https://jira.jboss.org/jira/browse/JBSEAM-3612 Project: Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.1.0.GA Reporter: Dan Allen Priority: Minor Fix For: 2.1.1.CR1 For any example that is deploying to a standard Java EE 5 environment (for instance the jpa example deploying to GlassFish or JBoss AS 5), the entity manager factory should be obtained through JNDI through a persistence unit reference. 5.3.1 of JPA spec: "Within a Java EE environment, an entity manager factory may be injected using the Persistence-Unit annotation or obtained through JNDI lookup." It would first need to be declared in web.xml: <persistence-unit-ref> <persistence-unit-ref-name>bookingDatabase/emf</persistence-unit-ref-name> <persistence-unit-name>bookingDatabase</persistence-unit-name> </persistence-unit-ref> Then the components.xml would look like this: <persistence:managed-persistence-context name="entityManager" auto-create="true" persistence-unit-jndi-name="java:comp/env/bookingDatabase/emf" /> The reason we should do this is to advocate the Java EE standard approach. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3677) Add logic operator option to Query to set how restrictions are combined (AND or OR)

by Dan Allen (JIRA)

Add logic operator option to Query to set how restrictions are combined (AND or OR) ----------------------------------------------------------------------------------- Key: JBSEAM-3677 URL: https://jira.jboss.org/jira/browse/JBSEAM-3677 Project: Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.1.0.SP1 Reporter: Dan Allen Fix For: 2.1.1.CR1 Folks often request for restrictions to be combined with OR rather than AND. This very much depends on the use case, so it makes sense to give the developer the option. Obviously, there are limits to how the restrictions on Query can be used, but I think this at least opens up a couple more use cases before extension is necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3637) seam-gen should not attempt to download jaxb-api.jar from Maven repository (offline requirement)

by Dan Allen (JIRA)

seam-gen should not attempt to download jaxb-api.jar from Maven repository (offline requirement) ------------------------------------------------------------------------------------------------ Key: JBSEAM-3637 URL: https://jira.jboss.org/jira/browse/JBSEAM-3637 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.0.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.1.0.SP1 Per the offline requirement of seam-gen, the jaxb-api.jar should be available in the dist. Version 2.1 is required and is not to conflict with the version pulled in by Seam. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3643) "Group by" paging failed

by Kenneth Zhang (JIRA)

"Group by" paging failed ------------------------ Key: JBSEAM-3643 URL: https://jira.jboss.org/jira/browse/JBSEAM-3643 Project: Seam Issue Type: Bug Components: Framework Affects Versions: 2.1.0.GA Environment: JBoss 4.2.3GA, Seam 2.1.0GA,JDK 1.5.0_16 Reporter: Kenneth Zhang GroupBy is a new function at seam 2.1.0GA, but it cannot work with paging. This is the test code: @Name("bookStat") public class BookStat extends EntityQuery<Book> { private static final String EJBQL = "select name, count(*) from Book book"; (snip) public BookStat() { setEjbql(EJBQL); setRestrictionExpressionStrings(Arrays.asList(RESTRICTIONS)); setMaxResults(3); setGroupBy("name"); } (snip) } There is the error log: 13:05:09,578 INFO [STDOUT] Hibernate: select count(*) as col_0_0_ from test_seam.dbo.BOOK book0_ group by book0_.name Caused by: javax.persistence.NonUniqueResultException: result returns 21 elements at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:85) at org.jboss.seam.framework.EntityQuery.initResultCount(EntityQuery.java:129) at org.jboss.seam.framework.EntityQuery.getResultCount(EntityQuery.java:120) at org.jboss.seam.framework.Query.getPageCount(Query.java:202) at org.jboss.seam.framework.Query.getLastFirstResult(Query.java:163) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3674) Custom parameter value in <redirect> is not being propagated (regression)

by Dan Allen (JIRA)

Custom parameter value in <redirect> is not being propagated (regression) ------------------------------------------------------------------------- Key: JBSEAM-3674 URL: https://jira.jboss.org/jira/browse/JBSEAM-3674 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.0.SP1 Reporter: Dan Allen Fix For: 2.1.1.CR1 I want to propagate a param so that it survives a redirect. This is what I have done until now. <navigation from-action="myaction"> <redirect view-id="/pages/page.hxtml" > <param name="category" value="#{param.name}"/> </redirect> </navigation> However, since 2.1, this doesn't work anymore. The param is still propagated but not the value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3570) Update the WebSphere reference guide chapter to WebSphere 7.0

by Jay Balunas (JIRA)

Update the WebSphere reference guide chapter to WebSphere 7.0 ------------------------------------------------------------- Key: JBSEAM-3570 URL: https://jira.jboss.org/jira/browse/JBSEAM-3570 Project: Seam Issue Type: Task Components: Platform interoperability Affects Versions: 2.1.0.CR1 Reporter: Jay Balunas Assignee: Marek Novotny Fix For: 2.1.1.CR1 WebSphere 7.0 has gone GA and now fully supports jee5 with out the various issues before. This needs to be investigated, tested, and the reference guide needs to be updated. Search forum, and jira for related issues and notes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3544) Problem sending email in Glassfish v2 in a cluster application

by Rodrigo Saito (JIRA)

Problem sending email in Glassfish v2 in a cluster application -------------------------------------------------------------- Key: JBSEAM-3544 URL: https://jira.jboss.org/jira/browse/JBSEAM-3544 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.CR1 Environment: Glassfish v2 Reporter: Rodrigo Saito Assignee: Pete Muir If an application have a tag <distributable /> in web.xml, application throws exception when trying to send email in Glassfish v2 org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.ui.facelet.mockHttpSession at org.jboss.seam.Component.newInstance(Component.java:2049) at org.jboss.seam.Component.getInstance(Component.java:1931) at org.jboss.seam.Component.getInstance(Component.java:1910) at org.jboss.seam.Component.getInstance(Component.java:1887) at org.jboss.seam.Component.getInstance(Component.java:1882) at org.jboss.seam.ui.facelet.MockHttpSessionManager.instance(MockHttpSessionManager.java:46) at org.jboss.seam.ui.facelet.RendererRequest.init(RendererRequest.java:42) at org.jboss.seam.ui.facelet.RendererRequest.run(RendererRequest.java:81) at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:43) at org.jboss.seam.example.mail.MailExample.send(MailExample.java:40) 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:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.jboss.seam.example.mail.MailExample_$$_javassist_2.send(MailExample_$$_javassist_2.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:597) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:329) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:342) at org.jboss.el.parser.AstPropertySuffix.invoke(AstPropertySuffix.java:58) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) at javax.faces.component.UICommand.broadcast(UICommand.java:383) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:317) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:44) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:198) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:288) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272) at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637) at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568) at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813) at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341) at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263) at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265) at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106) Caused by: java.lang.IllegalArgumentException: PWC2788: setAttribute: Non-serializable attribute at org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1635) at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:163) at com.sun.faces.context.SessionMap.put(ExternalContextImpl.java:972) at org.jboss.seam.contexts.BasicContext.set(BasicContext.java:85) at org.jboss.seam.Component.newInstance(Component.java:2031) I tested with the seam email example application. I will send the application modified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3551) Seam can not convert java.util.Date, it ignores javax.faces.convert.DateTimeConverter

by Francisco Jose Peredo Noguez (JIRA)

Seam can not convert java.util.Date, it ignores javax.faces.convert.DateTimeConverter ------------------------------------------------------------------------------------- Key: JBSEAM-3551 URL: https://jira.jboss.org/jira/browse/JBSEAM-3551 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.SP1 Environment: Jdk 1.5. Tomcat 6.0.18, Jboss Tools 2.1.2 Reporter: Francisco Jose Peredo Noguez Create a Seam project using Jboss Tools 2.1.2. Create a new Seam Form with name "SeamDateForm" Open the file SeamDateForm.java and change the value from Integer to java.util.Date. Right-click seamDateForm.xhtml and click Run As... -> Run On Server. Write something in the form (like for example some random string "dfasdf") You will get the error: Conversion Error setting value 'dfasdf' for 'null Converter'. Now create a Date Converter, as the one included in the attached test case project (BTW it inherits from javax.faces.convert.DateTimeConverter). Stop the application (just to be 100% sure everything gets loaded correctly) Again: Right-click seamDateForm.xhtml and click Run As... -> Run On Server. Write something in the form (like for example some random string "dfasdf") Now you get the right error: value must be a date, eg. 10/13/2008. Of course it not only fails when you write a random string, even if you write a correct date, like 01/01/2001, you will get an error that says: Conversion Error setting value '01/01/2001' for 'null Converter'. But if you write your own converter (for example inheriting from javax.faces.convert.DateTimeConverter) everything works fine. I think Seam should use javax.faces.convert.DateTimeConverter by default, I shouldn't need to create my own converter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3535) don't add parameter to Url if value is null

by Dan Allen (JIRA)

don't add parameter to Url if value is null ------------------------------------------- Key: JBSEAM-3535 URL: https://jira.jboss.org/jira/browse/JBSEAM-3535 Project: Seam Issue Type: Feature Request Components: JSF Controls Affects Versions: 2.1.0.CR1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.1.0.GA When the value of a parameter declared inside of a Seam UI command control using <f:param> is null, then it should not be appended to the URL. Currently, it is appended with a blank value. The problem is that there is a difference between an empty string (blank value) and not being present. Additionally, by setting the value to null (or leaving off the value attribute), it provides a way to suppress a parameter from being added the URL. Assuming the link was defined as follows: <s:link view="/UserEdit.xhtml"> <f:param name="userId"/> </s:link> The URL should be: /UserEdit.seam This might override a page parameter for instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009