January 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4756) Update Seam drools libraries to Drools 5.1

by Alessandro Lazarotti (JIRA)

Update Seam drools libraries to Drools 5.1 ------------------------------------------ Key: JBSEAM-4756 URL: https://issues.jboss.org/browse/JBSEAM-4756 Project: Seam Issue Type: Feature Request Environment: fedora 12, jdk 1.6, Seam 2.2, Guvnor 5.1 and drools-expert 5.1 Reporter: Alessandro Lazarotti Is necessary update drools libs to be compatible with Guvnor 5.1 serialization process -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (SEAMFACES-5) ContextualHttpServletRequest

by Nicklas Karlsson (JIRA)

ContextualHttpServletRequest ---------------------------- Key: SEAMFACES-5 URL: https://jira.jboss.org/jira/browse/SEAMFACES-5 Project: Seam Faces Issue Type: Feature Request Reporter: Nicklas Karlsson Assignee: Lincoln Baxter III (actually a Seam Servlet thing) A similar construct to the Seam 2 ContextualHttpServletRequest that can be used for running contextual stuff where the contexts are not automatically available (work already started) -- 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

12 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBSEAM-4722) Build seam2.5

by he youlin (JIRA)

Build seam2.5 ------------- Key: JBSEAM-4722 URL: https://jira.jboss.org/browse/JBSEAM-4722 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.1.CR2 Reporter: he youlin Priority: Optional I think seam team should consider building seam 2.5 version so we can upgrade our old project to jsf2.0,ejb3.1,hibernate 3.6,beanvalidation,glassfish3 or jboss6 and get rid of hibernate3.2 validation and richfaces3 dependcy. I have upgraded my old project a few months ago from seam2.2 to use jsf2.1,hibernate 3.6,beanvalidation,granite-seam21,spring3.05 under tomcat 7.0.5-dev and used in the production environment.I test it on glassfish v3.1 and jboss6 but not test ejb. If considered i can provide my patch to seam team as a reference or push full source code to github with your team permission. Please consider. heyoulin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

6
16
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-26) Make caught exception available as named bean

by Dan Allen (JIRA)

Make caught exception available as named bean --------------------------------------------- Key: SEAMCATCH-26 URL: https://issues.jboss.org/browse/SEAMCATCH-26 Project: Seam Catch Issue Type: Feature Request Components: Core Implementation Reporter: Dan Allen Assignee: Jason Porter Priority: Minor As we get into error pages, it's going to be useful to have the caught exception available via a named bean. I think this is just a matter of adding a dependent-scoped producer that reads the value of the current CaughtException from a field in the exception dispatcher. In Seam 2, the following two variables were available: org.jboss.seam.caughtException - the original exception that was caught org.jboss.seam.handledException - the exception cause currently being handled I think we could just map org.jboss.seam.caughtException to CaughtException...that way all the info is available, including the exception being handled, the original exception and the unwrapped stack. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3848) Seam fails to create and inject components when multiple ajax-requests are fired from a commandLink or commandButton, using ajax4jsf.

by etirk etirk (JIRA)

Seam fails to create and inject components when multiple ajax-requests are fired from a commandLink or commandButton, using ajax4jsf. ------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3848 URL: https://jira.jboss.org/jira/browse/JBSEAM-3848 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Environment: windows vista / rhel4 sun jdk5, jdk6 latest versions jboss as 4.2.2 and 4.2.3 firefox2 and 3, ie 6 and 7. Reporter: etirk etirk Fix For: 2.1.2.GA Seam fails to create and inject components when multiple ajax-requests are fired from a commandLink or commandButton, using ajax4jsf. Replication found using seam-booking in examples, trunk as of 081216. Rewrite the find-method in the HotelSearchAction-class, in the seam booking example application. It should look like this. public void find() { page = 0; queryHotels(); try { Thread.sleep(1000 * 5); } catch (InterruptedException ignore) { } } Now, start the application, register a user and enter main.html. Click multiple times on the search hotel button. Depending upon how fast your computer is, you might need to do more than a double-click. Sometimes you may need to klick fast up to 5-8 times. But it will occur. You will end up with an exception that says: Caused by javax.servlet.ServletException with message: javax.el.ELException: /main.xhtml @74,130 rendered=#{hotelSearch.nextPageAvailable}: Error reading nextPageAvailable on type org.javassist.tmp.java.lang.Object_$$_javassist_4 Which in turn comes from a synchronization problem. Caused by org.jboss.seam.core.LockTimeoutException with message: could not acquire lock on @Synchronized component: hotelSearch This is in a way funny, since the hotelSearch-component is not annotated with synchronized. Anyway, our application does not throw an exception like this, but we to have tried synchronizing our involved components, with no luck. Our exception is mostly this Caused by javax.servlet.ServletException with message: javax.el.ELException: /layout/template.xhtml @18,59 rendered=#{authenticator.inSpecialMode}: Error reading inSpecialMode on type se.session.Authenticator_$$_javassist_4 Which in turn comes from the failed injections Caused by org.jboss.seam.RequiredException with message: @In attribute requires non-null value: authenticator.entityManager This problem occurs all over the application, always when an ajax request is double-clicked and seam tries to recreate seam components and runs out of time. In 99% of the case it is the first read property of our authenticator-component that fails, and most often it is that seam cannot create a entityManager to inject, and the system fails due to that the annotation is set to only inject, without create. Removing the entityManager from the component will only result in that seam cannot inject another component instead, until you have no injections left in authenticator, and it still fails! Similar behaviour has been noticed using non-ajax calls, using standard h:commandButton/Link. This is however much more rare. -- 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

12 years, 2 months

6
15
0 / 0

[JBoss JIRA] Created: (JBSEAM-4500) Seam 2.2.0 based application fails to run if hibernate 4.0.2 GA used

by Ilya Shaikovsky (JIRA)

Seam 2.2.0 based application fails to run if hibernate 4.0.2 GA used -------------------------------------------------------------------- Key: JBSEAM-4500 URL: https://jira.jboss.org/jira/browse/JBSEAM-4500 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Environment: tomcat 6 Reporter: Ilya Shaikovsky https://forum.hibernate.org/viewtopic.php?f=9&t=1001094 I tried to update RF demo dependencies to use JSR-303. Exception on server start just as posted at forum. It seems component just should not be instantiated if misses required dependency. -- 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

12 years, 3 months

6
9
0 / 0

[JBoss JIRA] Created: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>

by Adrian Mitev (JIRA)

s:defaultAction blocks new lines in <textArea> ---------------------------------------------- Key: JBSEAM-4648 URL: https://jira.jboss.org/jira/browse/JBSEAM-4648 Project: Seam Issue Type: Bug Components: JSF Controls Reporter: Adrian Mitev s:defaultAction shouldn't work if the enter button is presses inside textarea element. To fix the issue wrap the javascript that s:convertEntity generates inside this code: var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() != 'textarea') { <original javascript 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

12 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBSEAM-4637) Seam does not work with JSF 2.0 faces-config.xml

by Ryan Nideffer (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBSEAM-4637 URL: https://jira.jboss.org/jira/browse/JBSEAM-4637 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.2.1.CR1 Reporter: Ryan Nideffer I am attempting to use JSF 2.0 in my Seam application for, among other benefits, composite components. I am able to upgrade the jsf-api.jar and jsf-impl.jar, remove jsf-facelets.jar and my application functions fine, however I am still running in JSF 1.2 mode due to this faces-config.xml: <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"> <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> According to thread comments from a Mojarra developer and the Release Notes for Mojarra 2, all thats needed is to remove the view-handler and reference v2.0 in faces-config. http://forums.java.net/jive/message.jspa?messageID=373539 https://javaserverfaces.dev.java.net/nonav/rlnotes/2.0.1/releasenotes.html As soon as I do this though, I get the following exception when my application is deployed: 2010-04-16 11:24:18,249 INFO [javax.enterprise.resource.webcontainer.jsf.config] (Thread-2) Unsanitized stacktrace from failed start... javax.faces.view.facelets.FaceletException: Must have a Constructor that takes in a ComponentConfig at com.sun.faces.facelets.tag.AbstractTagLibrary$UserComponentHandlerFactory.<init>(AbstractTagLibrary.java:289) ... Caused by: java.lang.NoSuchMethodException: org.jboss.seam.ui.handler.CommandButtonParameterComponentHandler.<init>(javax.faces.view.facelets.ComponentConfig) at java.lang.Class.getConstructor0(Class.java:2706) According to Dan Allen, Seam 2 and JSF 2 work together beautifully: http://seamframework.org/Documentation/DoesSeamWorkWithJSF2 -- 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

12 years, 3 months

7
17
0 / 0

[JBoss JIRA] Created: (JBSEAM-4667) Using JSF 2 And Seam - conversation Id

by varun shaji (JIRA)

Using JSF 2 And Seam - conversation Id -------------------------------------- Key: JBSEAM-4667 URL: https://jira.jboss.org/browse/JBSEAM-4667 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR1 Environment: JBoss-6.0 M2 , Seam 2.2.0 & Seam 2.2.1 CR1, JSF 2(Mojarro - 2.0.2) Reporter: varun shaji During Postback from a JSF page , the conversation id cannot be retored. The debug logs that i obtained for JSF 1.2 and JSF 2.0 are as shown for the same postback in a pageflow are as shown JSF 1.2 ******************************************************************************************************************** 06-15@23:18:50 (JbpmContextInfo.java:145) DEBUG - creating jbpm context with service factories '[]' 06-15@23:18:50 (JbpmContext.java:124) DEBUG - creating org.jbpm.JbpmContext@7b3555 06-15@23:18:50 (Pageflow.java:470) DEBUG - new pageflow instance for definition: hello 06-15@23:18:50 (GraphElement.java:170) DEBUG - event 'process-start' on 'ProcessDefinition(hello)' for 'Token(/)' 06-15@23:18:50 (JbpmContext.java:133) DEBUG - closing jbpmContext org.jbpm.JbpmContext@7b3555 ******************************************************************************************************* JSF 2.0 ********************************************************************************************** 06-15@22:38:27 (Pageflow.java:470) DEBUG - new pageflow instance for definition: hello ********************************************************************************************** I debuged and found the FacesPage from which the conversation Id is returning..Is returning null in JSF2 ..ConversationId is returning null in FacesPage returned by Seam when Using JSF2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3020) Links to seam and gsg of jbosstools

by Svetlana mukhina (JIRA)

Links to seam and gsg of jbosstools ----------------------------------- Key: JBSEAM-3020 URL: http://jira.jboss.com/jira/browse/JBSEAM-3020 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: Svetlana mukhina Assigned To: Michael Yuan Priority: Optional Looking through the guide http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/index.html I've found a chapter http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/gettingstartedwi... that overlapping with some of our guides - http://docs.jboss.org/tools/2.1.0.CR1/en/seam/publish/en-US/html/index.html and http://docs.jboss.org/tools/2.1.0.CR1/en/GettingStartedGuide/publish/en-U..., maybe it will be good to add links in the chapter referring to these 2 guides where a user could find more information on the topic? -- 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

12 years, 4 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2011