[JBoss Seam] - Re: Facelets does not submit
by paul＠xfact.nl
This is the logfile when loading the page, and clicking the button.
There is a line:
| 11:02:39,758 ERROR [STDERR] 12-okt-2006 11:02:39 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
|
but from what I have read on forums it's completely harmless.
|
| 11:02:18,679 INFO [Component] Component: browseProducts, scope: STATELESS, type: STATELESS_SESSION_BEAN, class: buyabike.ejb.session.BrowseProductsBean, JNDI: SeamBuyABike/BrowseProductsBean/local
| 11:02:18,679 INFO [Initialization] done initializing Seam
| 11:02:18,710 INFO [EARDeployer] Started J2EE application: file:/C:/jboss-seam/server/default/deploy/SeamBuyABike.ear
| 11:02:39,399 INFO [STDOUT] BeforePhase: RESTORE_VIEW(1)
| 11:02:39,430 INFO [[/SeamBuyABike]] No state saving method defined, assuming default server state saving
| 11:02:39,430 INFO [STDOUT] AfterPhase: RESTORE_VIEW(1)
| 11:02:39,461 INFO [Pages] reading pages.xml
| 11:02:39,461 INFO [STDOUT] BeforePhase: RENDER_RESPONSE(6)
| 11:02:39,758 ERROR [STDERR] 12-okt-2006 11:02:39 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/C:/jboss-seam/server/default/tmp/deploy/tmp57786SeamBuyABike.ear-contents/SeamBuyABike-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
| 11:02:39,789 ERROR [STDERR] 12-okt-2006 11:02:39 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/C:/jboss-seam/server/default/tmp/deploy/tmp57786SeamBuyABike.ear-contents/SeamBuyABike-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
| 11:02:39,805 ERROR [STDERR] 12-okt-2006 11:02:39 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/C:/jboss-seam/server/default/tmp/deploy/tmp57786SeamBuyABike.ear-contents/SeamBuyABike-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
| 11:02:39,805 ERROR [STDERR] 12-okt-2006 11:02:39 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/C:/jboss-seam/server/default/tmp/deploy/tmp57786SeamBuyABike.ear-contents/SeamBuyABike-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
| 11:02:39,805 ERROR [STDERR] 12-okt-2006 11:02:39 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/C:/jboss-seam/server/default/tmp/deploy/tmp57786SeamBuyABike.ear-contents/SeamBuyABike-exp.war/WEB-INF/lib/jboss-seam-ui.jar!/META-INF/seam.taglib.xml
| 11:02:39,820 ERROR [STDERR] 12-okt-2006 11:02:39 com.sun.facelets.compiler.TagLibraryConfig loadImplicit
| INFO: Added Library from: jar:file:/C:/jboss-seam/server/default/tmp/deploy/tmp57786SeamBuyABike.ear-contents/SeamBuyABike-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
| 11:02:39,961 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.PRETTY_HTML' found, using default value true
| 11:02:39,961 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT' found, using default value true
| 11:02:39,961 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.DETECT_JAVASCRIPT' found, using default value false
| 11:02:39,961 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.AUTO_SCROLL' found, using default value false
| 11:02:39,961 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS' found, using default value org.apache.myfaces.renderkit.html.util.DefaultAddResource
| 11:02:39,961 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default value true
| 11:02:39,992 INFO [STDOUT] AfterPhase: RENDER_RESPONSE(6)
| 11:02:40,008 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.PRETTY_HTML' found, using default value true
| 11:02:40,008 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT' found, using default value true
| 11:02:40,008 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.DETECT_JAVASCRIPT' found, using default value false
| 11:02:40,008 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.AUTO_SCROLL' found, using default value false
| 11:02:40,008 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS' found, using default value org.apache.myfaces.renderkit.html.util.DefaultAddResource
| 11:02:40,008 INFO [MyfacesConfig] No context init parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER' found, using default value true
| 11:03:37,395 INFO [STDOUT] BeforePhase: RESTORE_VIEW(1)
| 11:03:37,411 INFO [STDOUT] AfterPhase: RESTORE_VIEW(1)
| 11:03:37,411 INFO [STDOUT] BeforePhase: RENDER_RESPONSE(6)
| 11:03:37,411 INFO [STDOUT] AfterPhase: RENDER_RESPONSE(6)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977808#3977808
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977808
19 years, 7 months
[JBossWS] - Re: WS-Eventing - sending notification
by palin
"artem_spector" wrote : Something is unclear to me after reading the user guide:
|
| 1. Notification payload:
| The example shows the payload creation via parsing some xml string - is there a better way to do it?
I think you can create that xml string the way you prefer, it doesn't matter how you do it as long as what you get is in compliance with the schema you provided in you wsdl; for example, we create it on the fly using jdom.
"artem_spector" wrote : 2. The notification endpoint definition:
| It should be described by some wsdl?
| Should the notification endpoint wsdl and the event source wsdl share the same data type definition of the payload?
| Should the notification enpoint port definition be same as the event source port definition?
As far as I understood from ws-eventing specs (http://www.w3.org/Submission/WS-Eventing) no specific wsdl is required for the notification endpoint since all you need to know is already written in the eventing wsdl (i.e. sysmon.wsdl in jbossws eventing examples). The notification endpoint has to be able to process a soap message containing an xml in compliance with the data type schema defined in the wsdl, nothing more (see chapter 4 of w3c specifications).
Alessio Soldano
http://www.javalinux.it/blogs
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977804#3977804
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977804
19 years, 7 months