June 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1550) The new public method Exceptions.addHandler needs to add handlers to be head of the exceptionHandlers list.

by Chris Rudd (JIRA)

The new public method Exceptions.addHandler needs to add handlers to be head of the exceptionHandlers list. ----------------------------------------------------------------------------------------------------------- Key: JBSEAM-1550 URL: http://jira.jboss.com/jira/browse/JBSEAM-1550 Project: JBoss Seam Issue Type: Bug Reporter: Chris Rudd With the new addHandler method it makes it possible to register handlers programatically. But all the handlers are added at the end. This causes a problem when the DebugPageHandler or an "anyexception" handler is registerd via pages.xml. Handlers added programatically need to be added at the front of the list, or at least before the "anyexception" /DebugPageHandler handlers. -- 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, 6 months

2
1
0 / 0

Re: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1000) Propagation of conversations with pageflow in testing environment.

by juergen melzer

Im am really overwhelmed that I already got 3 messages from You! Thanks for working that hard on my issue!!! If I knew, that I would resolve the problem 20 minutes later, I would'nt have bothered you. Means: I found the solution to that problem already: You fix it by adding the following to the web.xml (if using the JSF RI): <listener> <listener-class>com.sun.faces.config.ConfigureListener</listener-class> </listener> This listener seems to be a must for Tomcat 5.5.+ (Tomcat 5.0 did'nt need that at all.) You fix it also by using MyFaces and uncommenting the following: <listener> <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> </listener> Thank's a lot. Keep going. Best regards, Juergen Melzer ----- Original Message ---- From: Gavin King (JIRA) <jira-events(a)lists.jboss.org> To: jbossseam-issues(a)lists.jboss.org Sent: Monday, June 25, 2007 6:08:21 PM Subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1000) Propagation of conversations with pageflow in testing environment. [ http://jira.jboss.com/jira/browse/JBSEAM-1000?page=comments#action_12366684 ] Gavin King commented on JBSEAM-1000: ------------------------------------ Would you please test this again, with current CVS, I believe it should work... > Propagation of conversations with pageflow in testing environment. > ------------------------------------------------------------------ > > Key: JBSEAM-1000 > URL: http://jira.jboss.com/jira/browse/JBSEAM-1000 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.2.0.GA > Environment: windows 2000 jboss-4.0.5.GA > Reporter: Denis Karpov > > I think there is bug in testing environment (propagation of conversations with pageflow does not work) > In this test there is 2 requests . > In the first I start conversation and pageflow > In the second conversation is lost. > If I do not start pageflow then conversation propagates. > Code: > public class TOrdTest extends SeamTest{ > private static final Log log = LogFactory.getLog( TOrdTest.class ); > > @Test > public void Test1() throws Exception > { > String id = new FacesRequest(){ > @Override > protected void invokeApplication() throws Exception { > Conversation.instance().begin(); > Pageflow.instance().begin("val_buy"); // uses start-state > setOutcome("browse"); > log.info("##### 1 Conversation_ID "+ Conversation.instance().getId()); > assert isLongRunningConversation(); > } > @Override > protected void renderResponse() throws Exception { > } > }.run(); > id = new FacesRequest("/exchange/buy_readonly.xhtml",id){ > @Override > protected void beforeRequest() > { > log.info("#####beforeRequest Conversation_ID "+ getConversationId()); > } > @Override > protected void applyRequestValues() throws Exception { > log.info("##### 2 Conversation_ID "+ Conversation.instance().getId()+" "+getConversationId()); > } > @Override > protected void invokeApplication() throws Exception { > //Conversation.instance().beginNested(); > log.info("##### 3 Conversation_ID "+ Conversation.instance().getId()+" "+getConversationId()); > assert isLongRunningConversation(); > } > }.run(); > } > } > -- 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 _______________________________________________ jbossseam-issues mailing list jbossseam-issues(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossseam-issues ____________________________________________________________________________________ Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. http://new.toolbar.yahoo.com/toolbar/features/norton/index.php

17 years, 6 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1544) Extend @Restrict annotation to allow specifying the "actionthe "args" parameter fro hasPermission a valuebinding for the instance instead of always passing null.

by Chris Rudd (JIRA)

Extend @Restrict annotation to allow specifying the "actionthe "args" parameter fro hasPermission a valuebinding for the instance instead of always passing null. ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1544 URL: http://jira.jboss.com/jira/browse/JBSEAM-1544 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.3.0.ALPHA Reporter: Chris Rudd I'm currently using a decendant of the Home objects that uses the specifis @Restrict on the update/persist and remove methods. The different Home objects are defined via configuration. This all works great, except that there isnt a way to get at the particular instance that the Home object is operating on. One could provide additional attributes to the @Restrict annotation such that one can specify the instance parameter of thte default s:hasPermission() that gets generated. Additionally the "root" object (the component that the interceptor is running against) would need to be exposed so that it can be accessed genericly (this would be due to the defining of the Home object via configuration, where the annotation has to be the same for every instance). I suggest "component" as the name to bind it to : i.e. @Restruct(instance=#{componet.instance}) . This would expose the current component as "component" then the createDefaultExpr would produce "#{s:hasPermission(<component name>, <method name>, compoent.instance)}" Additionally it would be nice to ve able to override the "action" to use (instead of always using the method name). -- 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, 6 months

2
3
0 / 0

[jbossseam-issues] Tomcat 5.5 integration issue

by juergen melzer

Dear all, Reading the book from Michael Yuan, I tried to deploy a seam project to Tomcat. Just exactly as written in his book, I used Ant to pack the book examples: "tomcatjpa" and "tomcatejb3" to tomcatjpa.war (and tomcatejb3.war) and deployed it on a fresh installed Tomcat 5.5.23 (by copying the war-file into the Tomcat webapps-folder and restarting Tomcat) I can't attach the war-file, because it takes more than 10MB, but I used exactly the sources which are available under: http://www.michaelyuan.com/blog/seam-next-gen-web-framework/#SeamDownload (Sample projects for JBoss AS 4.2.0 GA) I got Java 6 and Ant 1.7 (stable version) on my system. When I call "http://servername:8080/tomcatjpa/hello.seam" from Browser, I get an error message, that the FacesContextFactory cannot be found. This error is the same for tomcatjpa and tomcatejb3 My Stacktrace is: type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: Servlet.init() for servlet Faces Servlet threw exception org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) java.lang.Thread.run(Thread.java:619) root cause java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.context.FacesContextFactory javax.faces.FactoryFinder.getFactory(FactoryFinder.java:263) javax.faces.webapp.FacesServlet.init(FacesServlet.java:142) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) java.lang.Thread.run(Thread.java:619) Please help me, finding the solution to that problem. I am planning to set up a seam project running on Tomcat 5.5 (I am not allowed to use JBoss; I know, this is bad), beginning soon, so I really appreciate any comment on my little problem. Thank you so much for your kind help in advance, J. Melzer ____________________________________________________________________________________ Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. http://new.toolbar.yahoo.com/toolbar/features/mail/index.php

17 years, 6 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1540) Ant tasks to validate XML configuration files as part of test targets

by Pete Muir (JIRA)

Ant tasks to validate XML configuration files as part of test targets --------------------------------------------------------------------- Key: JBSEAM-1540 URL: http://jira.jboss.com/jira/browse/JBSEAM-1540 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.3.0.ALPHA Reporter: Pete Muir Assigned To: Pete Muir Priority: Critical Fix For: 1.3.0.BETA1 -- 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, 6 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1546) Should there be an event "org.jboss.seam.exceptionRaied" that fires immediatly prior to the handler being called?

by Chris Rudd (JIRA)

Should there be an event "org.jboss.seam.exceptionRaied" that fires immediatly prior to the handler being called? ----------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1546 URL: http://jira.jboss.com/jira/browse/JBSEAM-1546 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.3.0.ALPHA Reporter: Chris Rudd Priority: Minor The new events raised by the Exceptions component are nice, but would it be beneficial to raise and event before the handler is called so that one can interrogate the state of the request before its modified by the handler. (see JBSEAM-1285 - I would like to get the view that was being processed when the exeption occured.) I propose adding the follwing lines to Exceptions.handle Exceptions.java line 52: public void handle(Exception e) throws Exception { if ( Contexts.isConversationContextActive() ) { Contexts.getConversationContext().set("org.jboss.seam.exception", e); } + Events.instance().raiseEvent("org.jboss.seam.exceptionRaised." + cause.getClass().getName(), cause); + Events.instance().raiseEvent("org.jboss.seam.exceptionRaised", cause); -- 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, 6 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-505) Seam/WS

by Gavin King (JIRA)

Seam/WS ------- Key: JBSEAM-505 URL: http://jira.jboss.com/jira/browse/JBSEAM-505 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Blocker Fix For: 1.2.0.BETA1 Seam/WS will allow Seam components to receive WS calls and: * participate in a WS conversation which is * orchestrated by jBPM * recoverable, when services come back online -- 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, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1468) GWT documentation

by Gavin King (JIRA)

GWT documentation ----------------- Key: JBSEAM-1468 URL: http://jira.jboss.com/jira/browse/JBSEAM-1468 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.3.0.BETA1 Need to document it. -- 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, 6 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1547) #{conversationContext['entityManager']}, etc

by Gavin King (JIRA)

#{conversationContext['entityManager']}, etc -------------------------------------------- Key: JBSEAM-1547 URL: http://jira.jboss.com/jira/browse/JBSEAM-1547 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.BETA1 Even JSP has this! Easy with the ELResolver. -- 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, 6 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1533) web.xml is invalid per xsd (generated by seam-gen and in examples)

by Mikhail Grushinskiy (JIRA)

web.xml is invalid per xsd (generated by seam-gen and in examples) ------------------------------------------------------------------ Key: JBSEAM-1533 URL: http://jira.jboss.com/jira/browse/JBSEAM-1533 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.3.0.ALPHA, 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA, 1.3.1.GA Reporter: Mikhail Grushinskiy web.xml is invalid per xsd (generated by seam-gen and in examples) -- 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, 6 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2007