October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1930) Improve documentation for @DataModelSelection and @DataModelSelectionIndex

by Jacob Orshalick (JIRA)

Improve documentation for @DataModelSelection and @DataModelSelectionIndex -------------------------------------------------------------------------- Key: JBSEAM-1930 URL: http://jira.jboss.com/jira/browse/JBSEAM-1930 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.BETA1 Reporter: Jacob Orshalick The existing documentation for @DataModelSelection and @DataModelSelectionIndex seems to indicate to developers that you are naming the @DataModelSelection or @DataModelSelectionIndex context variable by specifying the value. I have heard this same question from every new member of my team when they try to use 2 DataModels in one component. The following patch (or something along these lines) is recommended for both @DataModelSelection and @DataModelSelectionIndex: @DataModelSelection Injects the selected value from the JSF DataModel (this is the element of the underlying collection, or the map value) that the DataModelSelection is associated with. If only one @DataModel attribute is defined for a component, the selected value from that DataModel will be injected. Otherwise, the component name of each @DataModel must be specified in the value attribute for each @DataModelSelection. @DataModel(value="list1") private List<String> list2; @DataModelSelection(value="list1") private String focusList1; @DataModel(value="list2") private List<String> list2; @DataModelSelection(value="list2") private String focusList2; Specifies that the attribute focusList1 is to be injected with the DataModelSelection for the component list1, and similarly focusList2 is injected with the DataModelSelection for list2. Note: @DataModelSelection is like @In. If you want to outject a DataModelSelection, you will have to do so explicitly through by annotating the attribute with @Out. * value - name of the @DataModel conversation context variable this @DataModelSelection is associated with. Not needed if there is exactly one @DataModel in the component. -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2103) Tests for quartz example

by Pete Muir (JIRA)

Tests for quartz example ------------------------ Key: JBSEAM-2103 URL: http://jira.jboss.com/jira/browse/JBSEAM-2103 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.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

17 years, 2 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2028) improve test class organization

by Dan Allen (JIRA)

improve test class organization ------------------------------- Key: JBSEAM-2028 URL: http://jira.jboss.com/jira/browse/JBSEAM-2028 Project: JBoss Seam Issue Type: Task Components: Test Harness Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Fix For: 2.0.x I think we can do a little bit better than org.jboss.seam.test.misc for test class organization. I am not talking anything gargantuan here. Let's just organize the classes by the modules they are testing. I am cool with the use of the "test" package prefix. So let's say that ComponentTest goes in org.jboss.seam.test.core -- 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
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1748) Seam remoting stops working with GWT 1.4.10

by Tong Wang (JIRA)

Seam remoting stops working with GWT 1.4.10 ------------------------------------------- Key: JBSEAM-1748 URL: http://jira.jboss.com/jira/browse/JBSEAM-1748 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.0.BETA1 Environment: JBoss Seam 2.0 Beta 1, GWT 1.4.10, JBoss AS 4.2.0 GA Reporter: Tong Wang Assigned To: Shane Bryzak The GWT example shipped with seam 2.0 B1 stops working after GWT is upgraded from 1.3.3 to 1.4.10. Please see the forum thread link for detailed 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 months

5
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2047) NullPointerException in org.jboss.seam.contexts.BusinessProcessContext.getNamesFromContext()

by Jo Geraerts (JIRA)

NullPointerException in org.jboss.seam.contexts.BusinessProcessContext.getNamesFromContext() -------------------------------------------------------------------------------------------- Key: JBSEAM-2047 URL: http://jira.jboss.com/jira/browse/JBSEAM-2047 Project: JBoss Seam Issue Type: Bug Components: BPM, Core Affects Versions: 2.0.0.CR1 Environment: jboss 4.2.1.GA, postgresql db Linux pc0236 2.6.17-12-generic #2 SMP Sun Sep 23 22:56:28 UTC 2007 i686 GNU/Linux Reporter: Jo Geraerts When creating a JBPM Process Instance with @CreateProcess but no Attributes are outjected to the BusinessProcessContext a NullPointerException will be thrown at you. Example Code: @Stateless @Name("inklessProcessManager") public class InklessProcessManagerImpl implements InklessProcessManager { @CreateProcess(definition="inkless") @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) public void startProcess() { } } Stacktrace: Caused by: java.lang.NullPointerException at org.jboss.seam.contexts.BusinessProcessContext.getNamesFromContext(BusinessProcessContext.java:1 15) at org.jboss.seam.contexts.BusinessProcessContext.getNames(BusinessProcessContext.java:97) at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:241) at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:356) Code that works: @Stateless @Name("inklessProcessManager") @Interceptors(SeamInterceptor.class) public class InklessProcessManagerImpl implements InklessProcessManager { @Out(scope=ScopeType.BUSINESS_PROCESS, value="foo") Integer someThing; @CreateProcess(definition="inkless") public void startProcess() { someThing=new Integer(5); } } -- 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
5
0 / 0

[jbossseam-issues] NoSuchMethodError: Google only 2 references!

by David Brown

Hello jboss seam dev, gurus and users. I have a very curious error condition. Google responds with only 2 references for my seam hibernate reverse engineered application. Docjar has nothing and jarscan finds nothing local. The server.log snippet follows with particulars. Thanks in advance and please advise, David. 2007-10-15 14:35:03,902 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/seamap p].[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception java.lang.NoSuchMethodError: javax.faces.application.ViewHandler.initView(Ljavax/faces/context/FacesC ontext;)V at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:208) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:106) OS: Windows XP and Debian JBoss: 4.2.1.GA hibernate: tool 3.1.0beta5 JBoss-seam: 2.0.0CR2 Yet some, not wise, go to the other side of the globe, to barbarous and unhealthy regions, and devote ten or twenty years, in that they may live,-that is, keep comfortably warm,- and die in New England at last. Henry David Thoreau - Walden - 1845 Do you need to diversify your portfolio? Click here for informaton on trading currency. <http://tagline.bidsystem.com/fc/Ioyw36XIh1GVeMDWPSSxCvD9UF3gbqoSykG2m8Z 9lKzZLDIqDwriP1/> _______________________________________________________________ Get the Free email that has everyone talking at <a href=http://www.mail2world.com target=new>http://www.mail2world.com</a> Unlimited Email Storage POP3 Calendar SMS Translator Much More!

17 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2099) Support protection against SQL injection in Query order parameter

by Diego Ballve (JIRA)

Support protection against SQL injection in Query order parameter ----------------------------------------------------------------- Key: JBSEAM-2099 URL: http://jira.jboss.com/jira/browse/JBSEAM-2099 Project: JBoss Seam Issue Type: Patch Components: Framework Affects Versions: 2.0.0.CR2 Reporter: Diego Ballve Attachments: Query.diff >From http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119810 The 'order' parameter gets directly concatenaded to the query.. that would allow anything to get injected in the query, possibly resulting in a security threat. This patch gives the developer extending framework Query the chance to limit the acceptable order properties. -- 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

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2053) Random "session was null" exception while rendering pages

by Matthew Lieder (JIRA)

Random "session was null" exception while rendering pages --------------------------------------------------------- Key: JBSEAM-2053 URL: http://jira.jboss.com/jira/browse/JBSEAM-2053 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR2, 2.0.0.CR1 Environment: JRE 1.5, Tomcat 5.5 Reporter: Matthew Lieder I'm getting the following exception randomly while rendering pages: ERROR SeamPhaseListener - uncaught exception java.lang.IllegalStateException: Could not start transaction at org.jboss.seam.jsf.SeamPhaseListener.begin(SeamPhaseListener.java:571) at org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsBeforePhase(SeamPhaseListener.java:307) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:142) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116) at org.ajax4jsf.resource.ResourceLifecycle.invokePhaseListener(ResourceLifecycle.java:201) at org.ajax4jsf.resource.ResourceLifecycle.processPhaseListeners(ResourceLifecycle.java:177) at org.ajax4jsf.resource.ResourceLifecycle.send(ResourceLifecycle.java:147) at org.ajax4jsf.resource.InternetResourceService.load(InternetResourceService.java:336) at org.ajax4jsf.cache.LRUMapCache.load(LRUMapCache.java:116) at org.ajax4jsf.cache.LRUMapCache.get(LRUMapCache.java:87) at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:198) at org.ajax4jsf.resource.InternetResourceService.serviceResource(InternetResourceService.java:144) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:265) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 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.servlet.SeamFilter.doFilter(SeamFilter.java:150) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215 ) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.fl.nuevo.utils.ResponseHeaderFilter.doFilter(ResponseHeaderFilter.java:42) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215 ) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11Base Protocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalStateException: session was null: #{ourDatabase} at org.jboss.seam.transaction.HibernateTransaction.initSession(HibernateTransaction.java:71) at org.jboss.seam.transaction.HibernateTransaction.begin(HibernateTransaction.java:79) at org.jboss.seam.jsf.SeamPhaseListener.begin(SeamPhaseListener.java:566) ... 34 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, 2 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2108) Incorrect jsf core xml schema path in ./seam new-conversation view

by Adam Warski (JIRA)

Incorrect jsf core xml schema path in ./seam new-conversation view ------------------------------------------------------------------ Key: JBSEAM-2108 URL: http://jira.jboss.com/jira/browse/JBSEAM-2108 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Reporter: Adam Warski Priority: Trivial When generating a new conversation with seam-gen, the generated view has the incorrect path to xml schema for jsf-core: xmlns:f="http://java.sun.com/jsf" instead of: xmlns:f="http://java.sun.com/jsf/core" -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1722) SeamResourceServlet should return 404 if AbstractResource is not found

by Michael Steiner (JIRA)

SeamResourceServlet should return 404 if AbstractResource is not found ---------------------------------------------------------------------- Key: JBSEAM-1722 URL: http://jira.jboss.com/jira/browse/JBSEAM-1722 Project: JBoss Seam Issue Type: Bug Components: Framework Reporter: Michael Steiner Priority: Minor If SeamResourceServlet can't find AbstractResource provider should return 404 Not found. Currently it returns blank page -- 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 October 2007