From issues at jboss.org Wed Apr 2 03:57:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 03:57:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-1000) Propagation of conversations with pageflow in testing environment. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-1000. --------------------------------- Fix Version/s: (was: The future) Resolution: Out of Date > Propagation of conversations with pageflow in testing environment. > ------------------------------------------------------------------ > > Key: JBSEAM-1000 > URL: https://issues.jboss.org/browse/JBSEAM-1000 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 1.2.0.GA > Environment: windows 2000 jboss-4.0.5.GA > Reporter: Denis Karpov > Assignee: Pete Muir > > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 04:23:14 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 04:23:14 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-2250) Listing returns no records found if current page number is higher than expected results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-2250. --------------------------------- Fix Version/s: (was: The future) Resolution: Out of Date > Listing returns no records found if current page number is higher than expected results > --------------------------------------------------------------------------------------- > > Key: JBSEAM-2250 > URL: https://issues.jboss.org/browse/JBSEAM-2250 > Project: Seam 2 > Issue Type: Bug > Components: Framework > Affects Versions: 1.2.1.GA > Environment: Win XP, JDK 6, JBoss AS 4.2.2. > Reporter: terryb > Priority: Minor > > When browsing search results based on EntityQuery, and current results page number is higher than results based on further search criteria entered. Then seam returns no records found. See Forum issue for further details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 04:37:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 04:37:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-1388) s:fileUpload doesn't work in Portlet In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-1388. --------------------------------- Resolution: Out of Date > s:fileUpload doesn't work in Portlet > ------------------------------------ > > Key: JBSEAM-1388 > URL: https://issues.jboss.org/browse/JBSEAM-1388 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration, Portal > Affects Versions: 1.2.1.GA > Reporter: Jarkko Lietolahti > Assignee: Shane Bryzak > > From UIFileUpload.java: > @Override > public void decode(FacesContext context) > { > super.decode(context); > > ServletRequest request = (ServletRequest) context.getExternalContext().getRequest(); > } > In portal/portlet, one gets ActionRequest (which extends PortalRequest) instead of ServletRequest. > > > Nested Exception is > java.lang.ClassCastException: com.liferay.portlet.ActionRequestImpl cannot be cast to javax.servlet.ServletRequest > at org.jboss.seam.ui.UIFileUpload.decode(UIFileUpload.java:35) > at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:606) > at javax.faces.component.UIForm.processDecodes(UIForm.java:53) > at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:602) > at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:135) > at org.apache.myfaces.lifecycle.LifecycleImpl.applyRequestValues(LifecycleImpl.java:219) > at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:71) > at org.apache.myfaces.portlet.MyFacesGenericPortlet.processAction(MyFacesGenericPortlet.java:220) > at com.liferay.portal.kernel.servlet.PortletServlet.service(PortletServlet.java:88) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) > at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) > at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) > at com.liferay.portlet.CachePortlet._invoke(CachePortlet.java:333) > at com.liferay.portlet.CachePortlet.processAction(CachePortlet.java:157) > at com.liferay.portal.action.LayoutAction._processPortletRequest(LayoutAction.java:269) > at com.liferay.portal.action.LayoutAction._processActionRequest(LayoutAction.java:290) > at com.liferay.portal.action.LayoutAction.execute(LayoutAction.java:113) > at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) > at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) > at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:156) > at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) > at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at com.liferay.portal.servlet.MainServlet.callParentService(MainServlet.java:479) > at com.liferay.portal.servlet.MainServlet.service(MainServlet.java:877) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:94) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at com.liferay.filters.secure.SecureFilter.doFilter(SecureFilter.java:143) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:115) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter.doFilter(LayoutCacheFilter.java:197) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at com.liferay.portal.servlet.filters.autologin.AutoLoginFilter.doFilter(AutoLoginFilter.java:117) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:169) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at net.hyperic.hq.product.servlet.filter.JMXFilter.doFilter(JMXFilter.java:277) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) > at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 05:51:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 05:51:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4881) Verify Seam-gen works with maven build structure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4881. --------------------------------- Fix Version/s: (was: The future) Resolution: Rejected rejected due not investing time to migrate seam-gen to maven > Verify Seam-gen works with maven build structure > ------------------------------------------------ > > Key: JBSEAM-4881 > URL: https://issues.jboss.org/browse/JBSEAM-4881 > Project: Seam 2 > Issue Type: Task > Reporter: Pete Muir > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > * Run seam-gen against distribution of Seam 2.3 and report and resolve any issues -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 05:51:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 05:51:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4882) Verify JBDS "seam-gen" works with new Maven structure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4882. --------------------------------- Resolution: Rejected rejecting due not investing time to migrate seam-gen to maven > Verify JBDS "seam-gen" works with new Maven structure > ----------------------------------------------------- > > Key: JBSEAM-4882 > URL: https://issues.jboss.org/browse/JBSEAM-4882 > Project: Seam 2 > Issue Type: Task > Reporter: Pete Muir > Fix For: The future > > Original Estimate: 5 hours > Remaining Estimate: 5 hours > > Generate Seam projects using JBDS "New Seam Project" and verify outcome. Identify and report any issues to JBDS team. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 05:53:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 05:53:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-2525) Split out Spring and microcontainer support into separate jars In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-2525. --------------------------------- Resolution: Won't Fix > Split out Spring and microcontainer support into separate jars > -------------------------------------------------------------- > > Key: JBSEAM-2525 > URL: https://issues.jboss.org/browse/JBSEAM-2525 > Project: Seam 2 > Issue Type: Task > Components: Build, Spring > Affects Versions: 2.0.1.CR1 > Reporter: Pete Muir > Fix For: The future > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 05:53:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 05:53:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-3525) Analyse JNDI lookups in an EJB app (Booking) and a EntityHome based app (seam-gen) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-3525. --------------------------------- Resolution: Out of Date > Analyse JNDI lookups in an EJB app (Booking) and a EntityHome based app (seam-gen) > ---------------------------------------------------------------------------------- > > Key: JBSEAM-3525 > URL: https://issues.jboss.org/browse/JBSEAM-3525 > Project: Seam 2 > Issue Type: Task > Components: Performance and Scalability > Affects Versions: 2.1.0.BETA1 > Reporter: Pete Muir > Assignee: Ondrej Skutka > Fix For: The future > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 06:11:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 06:11:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-2805) Reference guide XHTML formatting in PDF does not seem to be working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-2805. --------------------------------- Resolution: Out of Date > Reference guide XHTML formatting in PDF does not seem to be working > ------------------------------------------------------------------- > > Key: JBSEAM-2805 > URL: https://issues.jboss.org/browse/JBSEAM-2805 > Project: Seam 2 > Issue Type: Task > Components: Documentation Issues > Affects Versions: 2.0.2.CR1 > Reporter: Jay Balunas > Priority: Minor > Fix For: The future > > > See chapters 16 and 28. There are many xhtml code samples with their role set, but in PDF it is not formatted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 06:13:15 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 06:13:15 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-2069) itext example tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-2069. --------------------------------- Resolution: Out of Date > itext example tests > ------------------- > > Key: JBSEAM-2069 > URL: https://issues.jboss.org/browse/JBSEAM-2069 > Project: Seam 2 > Issue Type: Task > Components: Examples, Test Harness > Reporter: Norman Richards > Priority: Minor > Fix For: The future > > > I've added a stub itext test, but we can't truly test the example without a method of rendering the view. I'm going to revisit this in 2.0.1 as a solution for this would also allow me to solve the redirect problem we have now. That's something I hope to get to in 2.0.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 07:09:12 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 07:09:12 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-3136) Consider Remvoing Client State Saving Suggestion In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-3136. --------------------------------- Assignee: Marek Novotny Fix Version/s: 2.3.2.CR1 Resolution: Done recommendation was removed > Consider Remvoing Client State Saving Suggestion > ------------------------------------------------ > > Key: JBSEAM-3136 > URL: https://issues.jboss.org/browse/JBSEAM-3136 > Project: Seam 2 > Issue Type: Task > Components: Documentation Issues > Affects Versions: 2.0.2.GA > Reporter: Steve Roy > Assignee: Marek Novotny > Fix For: 2.3.2.CR1 > > > The Reference Guide has the following information: > Some JSF implementations have a broken implementation of server-side state saving that > interferes with Seam's conversation propagation. If you have problems with conversation > propagation during form submissions, try switching to client-side state saving. You'll need this in > web.xml: > > javax.faces.STATE_SAVING_METHOD > client > > per the forum thread, http://www.seamframework.org/Community/StateSavingMethod, this information appears to be out of date. > Although we found no server-side state issues in our application, we found this statement concerning with regard to our application since moving to client state changed the size of some rendered pages significantly. > It may be helpful to remove this out of date information to reduce confusion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 07:11:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 07:11:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-2922) Replace meldware with simple alternative In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-2922. --------------------------------- Resolution: Out of Date functional tests uses local mail smtp simulation provided by subethasmtp-wiser > Replace meldware with simple alternative > ---------------------------------------- > > Key: JBSEAM-2922 > URL: https://issues.jboss.org/browse/JBSEAM-2922 > Project: Seam 2 > Issue Type: Task > Components: Mail > Affects Versions: 2.0.2.CR1, 2.1.0.A1 > Reporter: Pete Muir > Assignee: Pete Muir > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 07:13:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 07:13:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-2920) Investigate using Maven version ranges with POMs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-2920. --------------------------------- Resolution: Rejected version ranges in Maven are very buggy > Investigate using Maven version ranges with POMs > ------------------------------------------------ > > Key: JBSEAM-2920 > URL: https://issues.jboss.org/browse/JBSEAM-2920 > Project: Seam 2 > Issue Type: Task > Components: Build > Affects Versions: 2.0.2.CR1 > Reporter: Pete Muir > Assignee: Pete Muir > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 07:53:14 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 07:53:14 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5129) Remove remote jquery link from seamdiscs example In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-5129. --------------------------------- Assignee: Marek Novotny Fix Version/s: 2.3.2.CR1 Resolution: Done done > Remove remote jquery link from seamdiscs example > ------------------------------------------------ > > Key: JBSEAM-5129 > URL: https://issues.jboss.org/browse/JBSEAM-5129 > Project: Seam 2 > Issue Type: Task > Components: Examples > Affects Versions: 2.3.1.Final > Reporter: Marek Novotny > Assignee: Marek Novotny > Fix For: 2.3.2.CR1 > > > Seamdiscs template.xhtml has got link to jquery javascript file and this effectively rely on online access to get it at least once. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 09:13:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 09:13:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4377) seam is not logging exceptions on failures of outjection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4377. --------------------------------- Resolution: Out of Date > seam is not logging exceptions on failures of outjection > -------------------------------------------------------- > > Key: JBSEAM-4377 > URL: https://issues.jboss.org/browse/JBSEAM-4377 > Project: Seam 2 > Issue Type: Bug > Components: Exception Handling > Affects Versions: 2.1.0.GA > Environment: jboss 5.0.1 and tomcat6.0.16 as well and seam version above > Reporter: deanhiller > > If @Out is required and is not there, seam correctly fails and logs nothing. In our QA environment, debug is false of course, so I can't see what went wrong on the server with a nice stack trace. Instead it is swallowed. When I run in debug mode, the correct seam debug comes up, but it is still not logged in the logs like all the other exceptions. This needs to be logged just in case I can't reproduce it in development so that I have some data on what happened instead of having no data at all on the exception that occurred in test or production. Please add a simple log to log these exceptions!!!! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 09:47:14 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 09:47:14 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5114) Seam applications can't deploy on Wildfly 8.0.0.Alph In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny updated JBSEAM-5114: ---------------------------------- Summary: Seam applications can't deploy on Wildfly 8.0.0.Alph (was: Seam applications can't deploy on Wildfly 8.0.0.Alpha1) > Seam applications can't deploy on Wildfly 8.0.0.Alph > ---------------------------------------------------- > > Key: JBSEAM-5114 > URL: https://issues.jboss.org/browse/JBSEAM-5114 > Project: Seam 2 > Issue Type: Bug > Components: Platform interoperability > Affects Versions: 2.3.1.CR1 > Reporter: Ron ?meral > Fix For: The future > > > Seam applications currently can't be deployed to WildFly due to errors in deployment scanning. > {noformat} > 08:51:55,656 INFO [javax.servlet.ServletContextListener] (MSC service thread 1-10) Welcome to Seam 2.3.1.CR1 > 08:51:55,673 WARN [org.jboss.seam.util.Resources] (MSC service thread 1-10) Unable to determine real path from servlet context for "/WEB-INF/dev" path does not exist. > 08:51:55,688 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/jboss-seam.jar (No such file or directory) > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:158) [rt.jar:1.7.0_17] > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 08:51:55,690 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/blog-ejb.jar (No such file or directory) > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:158) [rt.jar:1.7.0_17] > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 08:51:55,692 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/blog-web.war/WEB-INF/lib/jboss-seam-ui-2.3.1.CR1.jar (No such file or directory) > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:158) [rt.jar:1.7.0_17] > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 08:51:55,694 INFO [org.jboss.seam.init.Initialization] (MSC service thread 1-10) reading /WEB-INF/components.xml > 08:51:55,727 INFO [org.jboss.seam.init.Initialization] (MSC service thread 1-10) reading properties from: /seam.properties > 08:51:55,749 INFO [org.jboss.seam.Component] (MSC service thread 1-10) Component: org.jboss.seam.core.init, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Init > 08:51:55,766 INFO [org.jboss.seam.Component] (MSC service thread 1-10) Component: org.jboss.seam.async.dispatcher, scope: STATELESS, type: STATELESS_SESSION_BEAN, class: org.jboss.seam.async.TimerServiceDispatcher, JNDI: java:app/jboss-seam/TimerServiceDispatcher > 08:51:55,789 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC000001: Failed to start service jboss.undertow.deployment.default-host./seam-blog: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.NullPointerException > at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:145) > at org.jboss.seam.init.Initialization.init(Initialization.java:813) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > 08:51:55,798 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014613: Operation ("deploy") failed - address: ({"deployment" => "seam-blog.ear"}) - failure description: { > "JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./seam-blog" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > Caused by: java.lang.NullPointerException"}, > "JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.deployment.unit.\"seam-blog.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"seam-blog.ear\".\"jboss-seam.jar\".deploymentCompleteService]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]" > ] > } > 08:51:55,810 ERROR [org.jboss.as.server] (management-handler-thread - 1) JBAS015870: Deploy of deployment "seam-blog.ear" was rolled back with the following failure message: > { > "JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./seam-blog" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > Caused by: java.lang.NullPointerException"}, > "JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.deployment.unit.\"seam-blog.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"seam-blog.ear\".\"jboss-seam.jar\".deploymentCompleteService]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]" > ] > } > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 09:49:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 09:49:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5114) Seam applications can't deploy on Wildfly 8.0.0.Alpha1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny updated JBSEAM-5114: ---------------------------------- Summary: Seam applications can't deploy on Wildfly 8.0.0.Alpha1 (was: Seam applications can't deploy on Wildfly 8.0.0.Alph) > Seam applications can't deploy on Wildfly 8.0.0.Alpha1 > ------------------------------------------------------ > > Key: JBSEAM-5114 > URL: https://issues.jboss.org/browse/JBSEAM-5114 > Project: Seam 2 > Issue Type: Bug > Components: Platform interoperability > Affects Versions: 2.3.1.CR1 > Reporter: Ron ?meral > Fix For: The future > > > Seam applications currently can't be deployed to WildFly due to errors in deployment scanning. > {noformat} > 08:51:55,656 INFO [javax.servlet.ServletContextListener] (MSC service thread 1-10) Welcome to Seam 2.3.1.CR1 > 08:51:55,673 WARN [org.jboss.seam.util.Resources] (MSC service thread 1-10) Unable to determine real path from servlet context for "/WEB-INF/dev" path does not exist. > 08:51:55,688 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/jboss-seam.jar (No such file or directory) > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:158) [rt.jar:1.7.0_17] > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 08:51:55,690 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/blog-ejb.jar (No such file or directory) > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:158) [rt.jar:1.7.0_17] > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 08:51:55,692 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/blog-web.war/WEB-INF/lib/jboss-seam-ui-2.3.1.CR1.jar (No such file or directory) > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:158) [rt.jar:1.7.0_17] > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 08:51:55,694 INFO [org.jboss.seam.init.Initialization] (MSC service thread 1-10) reading /WEB-INF/components.xml > 08:51:55,727 INFO [org.jboss.seam.init.Initialization] (MSC service thread 1-10) reading properties from: /seam.properties > 08:51:55,749 INFO [org.jboss.seam.Component] (MSC service thread 1-10) Component: org.jboss.seam.core.init, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Init > 08:51:55,766 INFO [org.jboss.seam.Component] (MSC service thread 1-10) Component: org.jboss.seam.async.dispatcher, scope: STATELESS, type: STATELESS_SESSION_BEAN, class: org.jboss.seam.async.TimerServiceDispatcher, JNDI: java:app/jboss-seam/TimerServiceDispatcher > 08:51:55,789 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC000001: Failed to start service jboss.undertow.deployment.default-host./seam-blog: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.NullPointerException > at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:145) > at org.jboss.seam.init.Initialization.init(Initialization.java:813) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > 08:51:55,798 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014613: Operation ("deploy") failed - address: ({"deployment" => "seam-blog.ear"}) - failure description: { > "JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./seam-blog" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > Caused by: java.lang.NullPointerException"}, > "JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.deployment.unit.\"seam-blog.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"seam-blog.ear\".\"jboss-seam.jar\".deploymentCompleteService]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]" > ] > } > 08:51:55,810 ERROR [org.jboss.as.server] (management-handler-thread - 1) JBAS015870: Deploy of deployment "seam-blog.ear" was rolled back with the following failure message: > { > "JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./seam-blog" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > Caused by: java.lang.NullPointerException"}, > "JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.deployment.unit.\"seam-blog.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"seam-blog.ear\".\"jboss-seam.jar\".deploymentCompleteService]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]" > ] > } > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 09:49:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 09:49:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5114) Seam applications can't deploy on Wildfly 8.0.0.Alpha1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-5114. --------------------------------- Fix Version/s: (was: The future) Resolution: Out of Date This was fixed in Wildfly 8.0.0.Final > Seam applications can't deploy on Wildfly 8.0.0.Alpha1 > ------------------------------------------------------ > > Key: JBSEAM-5114 > URL: https://issues.jboss.org/browse/JBSEAM-5114 > Project: Seam 2 > Issue Type: Bug > Components: Platform interoperability > Affects Versions: 2.3.1.CR1 > Reporter: Ron ?meral > > Seam applications currently can't be deployed to WildFly due to errors in deployment scanning. > {noformat} > 08:51:55,656 INFO [javax.servlet.ServletContextListener] (MSC service thread 1-10) Welcome to Seam 2.3.1.CR1 > 08:51:55,673 WARN [org.jboss.seam.util.Resources] (MSC service thread 1-10) Unable to determine real path from servlet context for "/WEB-INF/dev" path does not exist. > 08:51:55,688 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/jboss-seam.jar (No such file or directory) > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:158) [rt.jar:1.7.0_17] > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 08:51:55,690 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/blog-ejb.jar (No such file or directory) > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:158) [rt.jar:1.7.0_17] > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 08:51:55,692 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/blog-web.war/WEB-INF/lib/jboss-seam-ui-2.3.1.CR1.jar (No such file or directory) > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_17] > at java.util.zip.ZipFile.(ZipFile.java:158) [rt.jar:1.7.0_17] > at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 08:51:55,694 INFO [org.jboss.seam.init.Initialization] (MSC service thread 1-10) reading /WEB-INF/components.xml > 08:51:55,727 INFO [org.jboss.seam.init.Initialization] (MSC service thread 1-10) reading properties from: /seam.properties > 08:51:55,749 INFO [org.jboss.seam.Component] (MSC service thread 1-10) Component: org.jboss.seam.core.init, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Init > 08:51:55,766 INFO [org.jboss.seam.Component] (MSC service thread 1-10) Component: org.jboss.seam.async.dispatcher, scope: STATELESS, type: STATELESS_SESSION_BEAN, class: org.jboss.seam.async.TimerServiceDispatcher, JNDI: java:app/jboss-seam/TimerServiceDispatcher > 08:51:55,789 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC000001: Failed to start service jboss.undertow.deployment.default-host./seam-blog: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.NullPointerException > at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:145) > at org.jboss.seam.init.Initialization.init(Initialization.java:813) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > 08:51:55,798 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014613: Operation ("deploy") failed - address: ({"deployment" => "seam-blog.ear"}) - failure description: { > "JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./seam-blog" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > Caused by: java.lang.NullPointerException"}, > "JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.deployment.unit.\"seam-blog.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"seam-blog.ear\".\"jboss-seam.jar\".deploymentCompleteService]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]" > ] > } > 08:51:55,810 ERROR [org.jboss.as.server] (management-handler-thread - 1) JBAS015870: Deploy of deployment "seam-blog.ear" was rolled back with the following failure message: > { > "JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./seam-blog" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > Caused by: java.lang.NullPointerException"}, > "JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.deployment.unit.\"seam-blog.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"seam-blog.ear\".\"jboss-seam.jar\".deploymentCompleteService]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]", > "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]" > ] > } > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 09:55:15 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 09:55:15 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4178) Seam 2.1.1GA on Glassfish generates an exception depending on where the end-conversation is placed in a pages.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4178. --------------------------------- Resolution: Out of Date > Seam 2.1.1GA on Glassfish generates an exception depending on where the end-conversation is placed in a pages.xml > ----------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-4178 > URL: https://issues.jboss.org/browse/JBSEAM-4178 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Environment: JD 1.6 Seam 2.1.1.GA Glassfish 2.1 > Reporter: Arshad Mahmood > > I have an application with an edit page named edit.xhtml, it has a form and submit buttion which executes the following action #{currencyAction.save}. The currencyAction is an EJB Stateful session bean. I am coming across a weird error when the action is execute:- > If my pages.xml is as follows, everything works as expected (i.e. the bean is saved and I get redirected to the view page). > > > > > > > > > > > > > > > > ** BUT **, if I change the end-conversation to be within the if-outcome then I get an exception. I.e. if the pages,xml is changed to > > > > *** CHANGE HERE **** > > > > > > The exception is as follows:- > [#|2009-05-15T10:08:58.045+0100|INFO|sun-appserver2.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=TP-Processor12;| > javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; nested exception is: java.lang.IllegalArgumentException: EntityManagerFactory not found in JNDI : java:comp/env/smartkidsBSEMF > java.lang.IllegalArgumentException: EntityManagerFactory not found in JNDI : java:comp/env/smartkidsBSEMF > at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManagerFactoryFromJndiOrValueBinding(ManagedPersistenceContext.java:245) > at org.jboss.seam.persistence.ManagedPersistenceContext.initEntityManager(ManagedPersistenceContext.java:78) > at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManager(ManagedPersistenceContext.java:107) > at sun.reflect.GeneratedMethodAccessor423.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > The bean values are persisted to the database, but then this exception is raised. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 09:55:15 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 09:55:15 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4163) Nullpointerexception from s:selectItems when noSelectionLabel is present and converter of selectOneMenu evaluates to null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4163. --------------------------------- Resolution: Rejected > Nullpointerexception from s:selectItems when noSelectionLabel is present and converter of selectOneMenu evaluates to null > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-4163 > URL: https://issues.jboss.org/browse/JBSEAM-4163 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Affects Versions: 2.1.1.GA > Reporter: Jakub Janczak > > The problem is that when you have the noSelectionLabel in s:selectItems it installs a converter chain in the h:selectOneMenu. > > > > So when the #{conv} evaluates to null it blows. The problem is in the PrioritizableConverter as it has the constructor: > public PrioritizableConverter(ValueExpression vb, int priority) > { > this.valueExpression = vb; > this.priority = priority; > } > and then > public String getAsString(FacesContext context, UIComponent component, Object value) > throws ConverterException > { > return getDelegate().getAsString(context, component, value); > } > public Converter getDelegate() > { > if (valueExpression != null) > { > return (Converter) valueExpression.getValue(FacesContext.getCurrentInstance().getELContext()); > } > else > { > return delegate; > } > } > so if getDelegate returns null it's not able to convert. > The solution would be to disable adding the PrioritizableConverter to the chain when the #{conv} evaluates to null (ConverterChain.java : 73) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 09:57:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 09:57:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5130) Add security warning to seam logging docs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny resolved JBSEAM-5130. ----------------------------------- Assignee: Marek Novotny Fix Version/s: 2.3.2.CR1 Resolution: Done > Add security warning to seam logging docs > ----------------------------------------- > > Key: JBSEAM-5130 > URL: https://issues.jboss.org/browse/JBSEAM-5130 > Project: Seam 2 > Issue Type: Bug > Components: Documentation Issues > Affects Versions: 2.2.2.Final, 2.3.0.Final, 2.3.1.Final > Reporter: David Jorm > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.2.CR1 > > > It has been reported that seam parses expression language (EL) statements in log messages. This is safe if used as intended - all user-provided input is supposed to be bound to a variable in the EL, conceptually similar to bound parameters in SQL. If an application did not use the Seam logging facility as intended, and included user-provided strings in log messages directly via string concatenation, then a remote attacker could use this flaw to execute arbitrary code in the context of the application server. The documentation does not highlight this issue at all, and it seems to be highly likely that some seam-based application developers would have used string concatenation with user-provided strings in log messages. > This needs to be addressed in all seam docs as a priority: > http://docs.jboss.org/seam/2.3.1.Final/reference/html_single/#d0e4185 > http://docs.jboss.org/seam/2.3.0.Final/reference/en-US/html_single/#d0e4185 > http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html_single/#d0e4254 > I suggest adding a big red warning admonition such as: > Title: > SECURITY WARNING: Do not use string concatenation to construct log messages > Body: > Seam logging evaluates expression language (EL) statements in log messages. This is safe if used as intended, because all user-provided input is bound to a parameter in the EL statement. If an application does not use the Seam logging facility as intended, and includes user-provided strings in log messages directly via string concatenation, then a remote attacker could inject EL statements directly into the log messages, which would be evaluated on the server. This could lead to a variety of security impacts. To protect against this issue, ensure that all user-provided input in log messages is bound to a parameter, and not included directly in log messages using string concatenation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 09:59:14 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 09:59:14 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4110) Ability to use jbpm jta mode with seam In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4110. --------------------------------- Fix Version/s: (was: The future) Resolution: Out of Date > Ability to use jbpm jta mode with seam > -------------------------------------- > > Key: JBSEAM-4110 > URL: https://issues.jboss.org/browse/JBSEAM-4110 > Project: Seam 2 > Issue Type: Bug > Components: BPM > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 09:59:14 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 09:59:14 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4025) Page actions do not work without Facelets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4025. --------------------------------- Resolution: Out of Date > Page actions do not work without Facelets > ----------------------------------------- > > Key: JBSEAM-4025 > URL: https://issues.jboss.org/browse/JBSEAM-4025 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.1.1.GA > Reporter: Hideyuki Suzumi > > I updated seam 2.0.2.SP1 to 2.1.1.GA. > I updated .page.xml to refer to the 2.1 XSD. > However, page actions did not work. > .page.xml is ignored. > I debugged and found the cause. > org.jboss.seam.navigation.Pages [line: 158] > String viewId = "/" + fileName.substring(0,fileName.length()-".page.xml".length()) + ".xhtml"; // needs more here > I am using not facelets but jsp. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 10:07:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 10:07:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4081) Seam Dev Tools Ref Guide 3.0.1.GA Chapter 5 Seam Wizards Not working according to tutorial. Server errors. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4081. --------------------------------- Resolution: Out of Date > Seam Dev Tools Ref Guide 3.0.1.GA Chapter 5 Seam Wizards Not working according to tutorial. Server errors. > ---------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-4081 > URL: https://issues.jboss.org/browse/JBSEAM-4081 > Project: Seam 2 > Issue Type: Bug > Components: Seam Text > Affects Versions: 2.1.1.GA, 2.1.2.CR2 > Environment: JBossAS 5.0.1.GA, Windows Server 2003, localhost:8080, seam 2.1.2.CR2, Eclipse 3.4.2 with JbossTools 3.0.1.GA, PostgreSQL 8.3 > Reporter: Jeffrey Wexler > Assignee: Dan Allen > > Going through tutorial. Chapter 5 encountering server errors. > 5.2 New Seam Form & 5.3 New Seam Conversation. > After creating the new form, when enter a value in the text field and click on FormMethod get Jboss Seam Debug Page. > Also get a Jboss Seam debug page after creating a seam conversation and then clicking on the Begin button. > Also get a Jboss Seam debug page after creating an Action (5.1) and clicking on the button. > Below is the exception for the case of entering a value in th text field of the created Form. > Exception during request processing: > Please see comment that I just added (below) for the exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 10:09:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 10:09:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4022) ComponentScanner fails with classes in WEB-INF/classes on websphere In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4022. --------------------------------- Resolution: Rejected > ComponentScanner fails with classes in WEB-INF/classes on websphere > ------------------------------------------------------------------- > > Key: JBSEAM-4022 > URL: https://issues.jboss.org/browse/JBSEAM-4022 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.1.1.GA > Environment: Websphere 7.0 (also reported on Websphere 6.1) > Reporter: John Eckhart > Attachments: classdescriptor.patch > > > This bug is a follow-on to 2347 which was rejected. Since it doesn't appear possible to request a bug be "reopened", I've created a new bug to track the problem. > The problem: When a Seam annotated class is included in a WAR file, the filename of the class will be "WEB-INF/classes/com/mycompany/MyClass.class". Theoretically, this IS the filename as the classes are packaged under WEB-INF/classes, however, the classloader does not recognize/ignore "WEB-INF/classes/" as part of the name (which is logical, since the classpath includes everything under this directory). This causes ComponentScanner to throw the following exception: java.lang.NoClassDefFoundError: WEB-INF.classes.com.mycompany.Myclass > The previous issue was rejected with the following rationale: "This turned out to be a user error, not a websphere issues. The classpath was correct, but the user put a META-INF/components.xml in the WAR which causes the scanning error." > However: > Where would the components.xml go if a project is broken into WAR, JAR (for JPA), JAR (for EJB), and finally EAR (containing the mentioned components)? > Based on the examples I've read for WebSphere , the recommended place for components.xml is in the WAR file. Moreover, it would stand to reason that including seam components in the WAR would be beneficial (ie POJO components as backing beans for jsf pages). > I ran into this issue recently in Websphere 7.0 where I had a Seam managed POJO as a backing bean to a JSF page. The bean wouldn't load because of the NoClassDefFoundError. I patched seam to work-around this issue as I didn't see any other solution (JSF backing beans don't belong in my JPA or EJB layers). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 10:21:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 10:21:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4006) Setting transaction.auto_close_session=true creates "Session is closed" warnings In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4006. --------------------------------- Resolution: Rejected > Setting transaction.auto_close_session=true creates "Session is closed" warnings > -------------------------------------------------------------------------------- > > Key: JBSEAM-4006 > URL: https://issues.jboss.org/browse/JBSEAM-4006 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.1.0.SP1 > Environment: Seam 2.1.0.SP1 > Spring 2.5.5 > Seam Managed Persistence Context enabled > JTA transaction Manager declared in Spring used. > Persistence unit property :"hibernate.transaction.auto_close_session=true" set to true > Reporter: Luc DEW > > Setting the hibernate.transaction.auto_close_session property to true cause "Session is closed!;" warnings in Seam with Seam Managed Persistence Context. > Because for instance, in the SeamPhaseListener's afterServletPhase(PhaseEvent event) the following code is executed: > handleTransactionsAfterPhase(event); > if ( event.getPhaseId() == RENDER_RESPONSE ) > { > afterRenderResponse(facesContext); > } > else if ( facesContext.getResponseComplete() ) > { > afterResponseComplete(facesContext); > } > If the current JSF phase is "after RENDER_RESPONSE" transaction is terminated (commited or rollbacked) by the handleTransactionsAfterPhaseMethod(event) method. If auto_close_session mode is set to true, the session is closed. But the afterRenderResponse(facesContext) is then executed. This method tries to change session's flush mode. Therefore, a "session is already closed" warning appears ! > It should be documented that setting this parameter to true can cause this kind of errors in Seam. But not setting this parameter to true can cause Hibernate sessions leakage if the persistence context not handled by Seam. Also, i am not sure that in any Seam use cases, the managed persistence context is closed properly. Some examples a method annotated @Observer("org.jboss.seam.postInitialization") with or @Async... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 10:23:14 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 10:23:14 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-3862) http://www.seamframework.org/Community/SeamGenToolBug In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-3862. --------------------------------- Resolution: Rejected > http://www.seamframework.org/Community/SeamGenToolBug > ----------------------------------------------------- > > Key: JBSEAM-3862 > URL: https://issues.jboss.org/browse/JBSEAM-3862 > Project: Seam 2 > Issue Type: Bug > Components: Tools > Environment: all version > Reporter: huix jan > > http://www.seamframework.org/Community/SeamGenToolBug -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 10:25:14 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 10:25:14 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-3826) Error Deploying Seam wiki example. HTTP 404: The requested resource docDisplay_d.seam is not available. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-3826. --------------------------------- Resolution: Won't Fix > Error Deploying Seam wiki example. HTTP 404: The requested resource docDisplay_d.seam is not available. > ------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-3826 > URL: https://issues.jboss.org/browse/JBSEAM-3826 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.1.0.SP1 > Reporter: Andre Salvati > > http://seamframework.org/Community/ErrorDeployingSeamWikiExampleHTTP404TheRequestedResourceDocDisplaydseamIsNotAvailable -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 10:27:13 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 2 Apr 2014 10:27:13 -0400 (EDT) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4634) International characters not rendered in PDF output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-4634. --------------------------------- Resolution: Won't Fix > International characters not rendered in PDF output > --------------------------------------------------- > > Key: JBSEAM-4634 > URL: https://issues.jboss.org/browse/JBSEAM-4634 > Project: Seam 2 > Issue Type: Bug > Components: PDF > Affects Versions: 2.2.1.CR1 > Reporter: Jozef Hartinger > > Internation characters are not rendered in the testing PDF document. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira