October 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3276) Alter Seam deployment SPI to allow delegating metadata discovery to runtime

by Pete Muir (JIRA)

Alter Seam deployment SPI to allow delegating metadata discovery to runtime --------------------------------------------------------------------------- Key: JBSEAM-3276 URL: https://jira.jboss.org/jira/browse/JBSEAM-3276 Project: Seam Issue Type: Feature Request Components: Platform interoperability Reporter: Pete Muir Assignee: Ales Justin Priority: Blocker Fix For: 2.1.0.BETA1 -- 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

17 years, 5 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3596) Add @SelectItems for exporting a list or hash to a List<SelectItem> context variable

by Dan Allen (JIRA)

Add @SelectItems for exporting a list or hash to a List<SelectItem> context variable ------------------------------------------------------------------------------------ Key: JBSEAM-3596 URL: https://jira.jboss.org/jira/browse/JBSEAM-3596 Project: Seam Issue Type: Feature Request Components: Core Reporter: Dan Allen Priority: Minor Fix For: 2.1.0.GA There are times when the UI needs a collection of SelectItem objects, yet the business logic does not need to be aware of this requirement. Thus, we have a similar situation as with JSF data models. It would be helpful to have an annotation counterpart to @DataModel named @SelectItems that outjects a list or hash as a list of SelectItem objects. If the property's type is a list, the label is assumed to be the same as the value. If the property's type is a hash, the entry's key is the option value and the entry's value is the option label. @SelectItems List<String> options; @SelectItems Hash<String, String> options; In the case of a list, we could allow a label to be defined using path notation in an annotation property named labelPath. @SelectItems(labelPath = "name") List<User> users; -- 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

17 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3601) wrapper component for current jbpm ExecutionContext

by Michael Brackx (JIRA)

wrapper component for current jbpm ExecutionContext --------------------------------------------------- Key: JBSEAM-3601 URL: https://jira.jboss.org/jira/browse/JBSEAM-3601 Project: Seam Issue Type: Feature Request Components: BPM Affects Versions: 2.0.2.SP1 Reporter: Michael Brackx wrapper component for current jbpm ExecutionContext to allow for injection into actions -- 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

17 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3600) Support for Enums in layout/sort.xhtml in seam-gen.

by Timothy Whitehead (JIRA)

Support for Enums in layout/sort.xhtml in seam-gen. --------------------------------------------------- Key: JBSEAM-3600 URL: https://jira.jboss.org/jira/browse/JBSEAM-3600 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.CR1 Reporter: Timothy Whitehead The new layout/sort.xhtml in seam-gen does not support enum columns. It would be nice if it could support enums. -- 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

17 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3268) Calling AuctionService webservice gives marshalling error

by Shane Bryzak (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-3268?page=com.atlassian.jira.pl... ] Shane Bryzak closed JBSEAM-3268. -------------------------------- Resolution: Done Fixed, and also added the findAuctions call to the test page. Thanks! > Calling AuctionService webservice gives marshalling error > --------------------------------------------------------- > > Key: JBSEAM-3268 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3268 > Project: Seam > Issue Type: Patch > Components: Examples > Affects Versions: 2.0.2.SP1 > Environment: WinXP > JBoss 4.2.0.GA > JDK 1.5.0_01 > Reporter: Jan Hoeve > Assignee: Shane Bryzak > Fix For: 2.1.1.CR1 > > Attachments: patch.txt > > > After deploying the seambay example in Jboss, I encountered the following error while invoking the webservice AuctionService from soapUI: > [com.sun.istack.SAXException2: A cycle is detected in the object graph. This will cause infinitely deep XML: org.jboss.seam.example.seambay.Auction@1df2b92 -> org.jboss.seam.example.seambay.AuctionImage@1d90a6e -> org.jboss.seam.example.seambay.Auction@1df2b92] > at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:295) > at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:221) > at org.jboss.ws.core.jaxws.JAXBSerializer.serialize(JAXBSerializer.java:83) > After looking at the annotations in Auction and AuctionImage it just is very clear: the association between the two classes is bidirectional; and thus causing the Marshaller to throw this error. (Because it cannot find out when to stop following references). > After googling/thinking I added an @XmlTransient annotation to AuctionImage#getAuction (see patch) , and thus breaking the loop when marshalling. > Now the webserive produces some result and is not giving errors anymore! > The problem-yet-to-solve (curious how you guys would solve): With this XmlTransient, xml2object unmarshalling is not fully supported anymore (I broke the loop...). -- 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

17 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3590) itext example shows 404 not found when accessed

by Jay Balunas (JIRA)

itext example shows 404 not found when accessed ----------------------------------------------- Key: JBSEAM-3590 URL: https://jira.jboss.org/jira/browse/JBSEAM-3590 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.CR1 Environment: JDK 5/6 JBoss AS 4.2.3 / AS 5 CR2 Reporter: Jay Balunas Fix For: 2.1.1.CR1 This was seen with both JDK 5 and 6 and on JBoss As 4.2.3 and 5 CR2. The example appears to deploy fine, but when first accessed you see a 404 not found exception. Note that the JBoss log does show activity so that request is reaching the application. The log does not show any exceptions or errors though. -- 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

17 years, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3489) postInitialization event is being called on hot deploy

by Pete Muir (JIRA)

postInitialization event is being called on hot deploy ------------------------------------------------------ Key: JBSEAM-3489 URL: https://jira.jboss.org/jira/browse/JBSEAM-3489 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.CR1 Reporter: Pete Muir Fix For: 2.0.3.GA -- 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

17 years, 5 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3577) Seam Context not working in Servlets

by Sean Burns (JIRA)

Seam Context not working in Servlets ------------------------------------- Key: JBSEAM-3577 URL: https://jira.jboss.org/jira/browse/JBSEAM-3577 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.CR1, 2.1.0.GA Environment: JBoss 4.2.3, Seam 2.1.0 GA Reporter: Sean Burns I used to able to look up components with Component.getInstance(...) inside a servlet by adding <web:context-filter url-pattern="/m/*" /> to the components.xml (in Seam 2.0.X). This has stopped working and now gives "java.lang.IllegalStateException: No event context active" This post relates http://www.seamframework.org/Community/GettingAStatelessComponentFromASer... and this one http://www.seamframework.org/Community/210CR1ThrowsJavalangIllegalStateEx... -- 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

17 years, 5 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3481) components.xml is read twice if the jboss-seam.jar is declared in application.xml as well as in manifest classpath

by Jay Balunas (JIRA)

components.xml is read twice if the jboss-seam.jar is declared in application.xml as well as in manifest classpath ------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-3481 URL: https://jira.jboss.org/jira/browse/JBSEAM-3481 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Assignee: Pete Muir Fix For: 2.1.0.GA This issue was exposed while working on JBSEAM-3363, and using patched jsf jars from Ryan Lubke which fixes the initial problem (see note below on using Ryan's patch). We do not see the duplicate seam phase listener issue any longer, but we continue to see this error. 08:50:53,573 ERROR [[/Stantest]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml) at org.jboss.seam.core.Init.checkDuplicateFactoryExpressions(Init.java:222) at org.jboss.seam.core.Init.checkDuplicateFactory(Init.java:215) at org.jboss.seam.core.Init.addFactoryValueExpression(Init.java:278) This is because we are reading in the components.xml file from the jboss-seam.jar twice as this log shows: 2008-09-30 10:21:08,245 INFO [org.jboss.seam.init.Initialization] reading /WEB-INF/components.xml 2008-09-30 10:21:08,396 INFO [org.jboss.seam.init.Initialization] reading jar:file:/jboss/apps/jboss-4.2.3.GA/server/default/deploy/Stantest.ear/jboss-seam.jar!/META-INF/components.xml 2008-09-30 10:21:08,400 INFO [org.jboss.seam.init.Initialization] reading jar:file:/jboss/apps/jboss-4.2.3.GA/server/default/tmp/deploy/tmp3645jboss-seam.jar!/META-INF/components.xml To use Ryan's patch: ---------------------- Use the attached jsf jars in the jsf-libs directory, and update JBOSS_HOME/server/default/deploy/jboss-web.deployer/conf/web.xml to include the following context param: <context-param> <param-name>com.sun.faces.duplicateJARPattern</param-name> <param-value>^tmp\d+(\S*\.jar)</param-value> </context-param> -- 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

17 years, 5 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3330) ICEfaces edit page in seam-gen application updates without save

by Valerie Griffin (JIRA)

ICEfaces edit page in seam-gen application updates without save --------------------------------------------------------------- Key: JBSEAM-3330 URL: https://jira.jboss.org/jira/browse/JBSEAM-3330 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.3.CR1 Environment: ICEfaces Reporter: Valerie Griffin The generated code includes partial submit. Whenever a field is changed, the database is updated without requiring the Save button. I've reported this problem to ICEfaces. The fix they propose requires the use of manual flush, which I understand is not universally supported. (The fix is to use manual flush and to override update, persist, and remove to invoke the manual flush.) I'm changing my seam-gen files to use that fix but am not including them here because I don't think that's necessarily the best fix. -- 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

17 years, 5 months

4
6
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 October 2008