October 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3506) @AutoCreate overrides @Observer(create = false) when it shouldn't

by Pete Muir (JIRA)

@AutoCreate overrides @Observer(create = false) when it shouldn't ----------------------------------------------------------------- Key: JBSEAM-3506 URL: https://jira.jboss.org/jira/browse/JBSEAM-3506 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: Christian Bauer I'm not even sure this is semantically correct but a component with @AutoCreate is always instantiated when it is referenced. The documentation only mentions the "when @In does not specify create=true" case. However, if you have an @AutoCreate component and it has an @Observer method, setting @Observer(create = false) has no effect, the component will be instantiated when the event occurs. We definitely need to document this or discuss it further. -- 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, 3 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3302) Suquery not working correctly with <framework:restrictions>

by Tim Timson (JIRA)

Suquery not working correctly with <framework:restrictions> ----------------------------------------------------------- Key: JBSEAM-3302 URL: https://jira.jboss.org/jira/browse/JBSEAM-3302 Project: Seam Issue Type: Feature Request Components: Framework Environment: Windows XP Reporter: Tim Timson I have created a query in components xml and added a restriction using the <framework:restrictions> tag. The restriction should add a where clause, but instead it is adding an "and", thinking the "where" is already in place. I assume this is because there is a "where" statement in a subquery contained in the ejbql. Here is the entry in components.xml which causes the error. <framework:entity-query name="eventPricedItemsQuery" ejbql="select pricedItem, (select sum(cartEntries.amountCharged) from Cart as cart join cart.entries as cartEntries join cartEntries.item as item where pricedItem.id = item.id) from PricedItem pricedItem"> <framework:restrictions> <value>pricedItem.event = #{currentEvent}</value> </framework:restrictions> </framework:entity-query> I can work around it by removing the restriction and adding a where clause to the ejbql, but have reasons for wanting to use the <framework:restrictions> tag instead. Here is some of the stack trace I used to determine that an "and" was being placed into the query by Seam when a "where" should have been created: Caused by: javax.el.ELException: /events/registration-report.xhtml @29,71 value="#{eventItems}": java.lang.IllegalArgumentException: org.hibernate.hql.ast.QuerySyntaxException: unexpected token: and near line 1, column 879 [select pricedItem, (select sum(cartEntries.amountCharged) from com.el.sbo.model.user.Cart as cart join cart.entries as cartEntries join cartEntries.item as item where pricedItem.id = item.id) ,(select count(cartEntries.amountCharged) from com.el.sbo.model.user.Cart as cart join cart.entries as cartEntries join cartEntries.item as item where pricedItem.id = item.id) from com.el.sbo.model.event.PricedItem pricedItem and pricedItem.event = :el1] at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:76) at javax.faces.component.UIData.getValue(UIData.java:582) ... 68 more Caused by: java.lang.IllegalArgumentException: org.hibernate.hql.ast.QuerySyntaxException: unexpected token: and near line 1, column 879 [select pricedItem, (select sum(cartEntries.amountCharged) from com.el.sbo.model.user.Cart as cart join cart.entries as cartEntries join cartEntries.item as item where pricedItem.id = item.id) ,(select count(cartEntries.amountCharged) from com.el.sbo.model.user.Cart as cart join cart.entries as cartEntries join cartEntries.item as item where pricedItem.id = item.id) from com.el.sbo.model.event.PricedItem pricedItem and pricedItem.event = :el1] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:617) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:96) at org.jboss.seam.persistence.EntityManagerProxy.createQuery(EntityManagerProxy.java:79) at org.hibernate.search.jpa.impl.FullTextEntityManagerImpl.createQuery(FullTextEntityManagerImpl.java:130) at org.jboss.seam.persistence.EntityManagerProxy.createQuery(EntityManagerProxy.java:79) at org.jboss.seam.framework.EntityQuery.createQuery(EntityQuery.java:175) -- 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, 3 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3543) Add example of using token-based remember-me

by Mikko Lehtinen (JIRA)

Add example of using token-based remember-me -------------------------------------------- Key: JBSEAM-3543 URL: https://jira.jboss.org/jira/browse/JBSEAM-3543 Project: Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.1.0.CR1 Reporter: Mikko Lehtinen Add support for token-based remember-me to one of the examples. This would make it easier to understand what configuration etc. is needed for it. At least I couldn't get it working by following the documentation. -- 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, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3536) Start time cannot be null

by Bernard Labno (JIRA)

Start time cannot be null ------------------------- Key: JBSEAM-3536 URL: https://jira.jboss.org/jira/browse/JBSEAM-3536 Project: Seam Issue Type: Bug Components: Async Affects Versions: 2.1.0.CR1 Environment: linux, jboss as 4.2.2.GA Reporter: Bernard Labno Method with such signature : @Asynchronous public void start(@IntervalDuration java.lang.Long interval); Triggers : Caused by: java.lang.IllegalArgumentException: Start time cannot be null at org.quartz.SimpleTrigger.setStartTime(SimpleTrigger.java:323) at org.quartz.SimpleTrigger.<init>(SimpleTrigger.java:260) at org.jboss.seam.async.QuartzDispatcher.scheduleWithQuartzService(QuartzDispatcher.java:179) at org.jboss.seam.async.QuartzDispatcher.scheduleWithQuartzServiceAndWrapExceptions(QuartzDispatcher.java:115) at org.jboss.seam.async.QuartzDispatcher.scheduleInvocation(QuartzDispatcher.java:101) at org.jboss.seam.async.QuartzDispatcher.scheduleInvocation(QuartzDispatcher.java:44) at org.jboss.seam.async.AsynchronousInterceptor.aroundInvoke(AsynchronousInterceptor.java:38) 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.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54) at org.javassist.tmp.java.lang.Object_$$_javassist_1.start(Object_$$_javassist_1.java) As I inspected the problem lies at QuartsDispatcher in line 179 where new SimpleTrigger is created with null startTime which is forbidden. -- 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, 3 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3140) s:span does not support title attribute

by Samuel Doyle (JIRA)

s:span does not support title attribute --------------------------------------- Key: JBSEAM-3140 URL: http://jira.jboss.com/jira/browse/JBSEAM-3140 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.0.2.GA Reporter: Samuel Doyle t doesn't appear that s:span supports the title attribute is this a bug? I was trying to do something like the following: <s:span styleClass="someClass" title="#{someExpression}"> ... </s:span> In the above scenario the title is always empty even though it shouldn't be. Replacing it with a normal span behaves as expected. -- 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, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3454) Recursive Entity causes strange behavior with EntityHome Id when trying to add child Entities

by Francisco Jose Peredo Noguez (JIRA)

Recursive Entity causes strange behavior with EntityHome Id when trying to add child Entities --------------------------------------------------------------------------------------------- Key: JBSEAM-3454 URL: https://jira.jboss.org/jira/browse/JBSEAM-3454 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.SP1 Environment: Jdk 1.6u6, JBoss AS 4.2.1 Reporter: Francisco Jose Peredo Noguez Create a Seam 2 project using JBossTools, create an @Entity with a recursive relationship (lets name it Category), run Seam Generate Entities, run the application. Create a category using the generated UI. Save it with name "category 1" Edit it. If in Category.xhtml you click "Add category" instead of presenting a clean form for adding the new children, it will present a form with currently selected category: "category 1"). This is a bug, but it is not the one I am reporting here. So, you decide you want to fix it, and for starters you change the code in the Add category button to this: <s:button value="Add category" view="/CategoryEdit.xhtml"> <f:param name="categoryId" value=""/> <f:param name="categoryFrom" value="Category"/> </s:button> note that the value for the categoryId is now empty (it used to have the #{categoryHome.instance.id} value). After making that change you run the application again and: Edit "category1" in Category.xhtml you click "Add category" and you get what you would expect, an empty form to add the child category (of course many more changes are needed to make it possible to really add a child category, but that is not the issue here) In layout/menu.xhtml you have a link to the CategoryList that looks like this: <s:link view="/CategoryList.xhtml" value="Category List" propagation="none"/> well, lets say you decide to add another one (just for the sake of experimenting) that looks like this: <s:link view="/CategoryList.xhtml" value="Category List Propagation Begin" propagation="begin"/> And then you Edit "category1" in Category.xhtml you click "Add category" and.... here comes the bug... the form is not empty, the <f:param name="categoryId" value=""/> plain just gets ignored. Why? I think it that the fact that now everything is running a long running conversation shouldn't screw up this... that is the bug I am reporting here. -- 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, 3 months

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (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 updated JBSEAM-3268: --------------------------------- Fix Version/s: 2.1.1.CR1 Assignee: Shane Bryzak > 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, 3 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-903) @Bidirectional to combine @In and @Out

by Andrew (JIRA)

@Bidirectional to combine @In and @Out -------------------------------------- Key: JBSEAM-903 URL: http://jira.jboss.com/jira/browse/JBSEAM-903 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.6.GA Reporter: Andrew Priority: Minor IMO, it would be great to have an InOut annotation that can combine In and Out to avoid excessive typing. Examples: Now: @In(required=false, value="someString", scope=ScopeType.EVENT) @Out(required=false, value="someString", scope=ScopeType.EVENT) private String localVariableName; Easier as: @Bidirectional(required=false, value="someString", scope=ScopeType.EVENT) private String localVariableName; -- 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, 3 months

7
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3497) ConcurrentModificationException

by Cesar Acuna (JIRA)

ConcurrentModificationException ------------------------------- Key: JBSEAM-3497 URL: https://jira.jboss.org/jira/browse/JBSEAM-3497 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.CR1 Environment: Glassfish 9.1, Trinidad 1.2.9 Reporter: Cesar Acuna Priority: Blocker I have an application running with jboss-seam-2.0.1.GA, and everything works fine. I upgraded to seam 2.1.0.CR1 and now I am getting the following exception: (It seems it cannot retrieve one of my seam components "svcFilter", due to a concurrency problem) @Entity @Table(name = "service") @Name("svcFilter") @Scope(ScopeType.CONVERSATION) @AutoCreate [#|2008-10-02T16:47:36.175-0500|INFO|sun-appserver9.1|javax.enterprise.system.stream.out|_ThreadID=22;_ThreadName=httpSSLWorkerThread-80-4;|16:47:36,172 WARN SeamPhaseListener:199 - uncaught exception, passing to exception handler java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) at java.util.HashMap$EntryIterator.next(HashMap.java:834) at java.util.HashMap$EntryIterator.next(HashMap.java:832) . . . . . . Caused by: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'svcFilter' resolved to null at com.sun.el.parser.AstValue.getTarget(AstValue.java:84) at com.sun.el.parser.AstValue.isReadOnly(AstValue.java:149) at com.sun.el.ValueExpressionImpl.isReadOnly(ValueExpressionImpl.java:248) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.EditableValueRenderer.getReadOnly(EditableValueRenderer.java:244) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.FormElementRenderer.renderAsElement(FormElementRenderer.java:217) at org.apache.myfaces.trinidadinternal.renderkit.core.xhtml.InputLabelAndMessageRenderer.getLabelFor(InputLabelAndMessageRenderer.java:78) -- 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, 3 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3395) GWT Example not working

by Dan Mihai Ile (JIRA)

GWT Example not working ----------------------- Key: JBSEAM-3395 URL: https://jira.jboss.org/jira/browse/JBSEAM-3395 Project: Seam Issue Type: Bug Components: GWT Affects Versions: 2.1.0.BETA1, 2.0.3.CR1, 2.0.2.SP1 Environment: Windows XP, Java 5, jboss-4.2.3.GA, apache-ant-1.7.1 Reporter: Dan Mihai Ile I am trying to deploy the examples/remote/gwt example using ant, but jboss AS gives an error on deploying. I understand that GWT support is porr in seam but at least make sure that the example works out of the box. Note that I didn't recompile anything, just deployed using "ant.bat deploy" Maybe there is an easy fix for this, if someone could check I would appreciate. Thank you. Begining of error log: 15:50:39,531 INFO [EARDeployer] Init J2EE application: file:/C:/Tools/programe/ jboss-4.2.3.GA/server/default/deploy/jboss-seam-gwt.ear 15:51:12,796 WARN [ServiceController] Problem creating service jboss.j2ee:servi ce=EJB3,module=jboss-seam-gwt.jar java.lang.NullPointerException at org.jboss.ejb3.security.JaccHelper.initialiseJacc(JaccHelper.java:73) at org.jboss.ejb3.Ejb3JmxDeployment.createPolicyConfiguration(Ejb3JmxDep loyment.java:53) ... -- 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, 3 months

3
4
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