Shale + Ajax4jsf
I've been trying to incorporate ajax4jsf into my app. After having troubles, I found some threads on the web indicating that there may be a conflict between the ajax4jsf filter and the Shale filter. Is this the case? Is anyone currently using these two technologies together? My set up is Shale 1.1.0 + myfaces RI 1.1.1 + facelets 1.1.11 E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.
Duplicate Client-id for ShaleViewRoot
Hello Shale + Facelets bretheren, I'm having a weird issue where facelets is reporting a Client-id : _id0 is duplicated in the faces tree error where ShaleViewRoot is supposedly the source of the duplicate id. It seems to be related with commandLinks on my page. If I remove them, the page loads fine. The command links do not have duplicate ids and I have no idea why this would be happening. Any suggestions? E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.
RE: Shale + Facelets + Tomahawk [OT?]
I do have that setting and I should mention that Facelets + Shale are working great together. The problem I'm having is only with the addition of myfaces tomahawk. In the absence of any obvious conflict, I'll run off to bother the myfaces mailing list for a change :) Thanks for the suggestion and have a great day! On 1/26/07, Reynolds, James [EMAIL PROTECTED] wrote: I'm having trouble configuring myfaces tomahawk components to work with Facelets and I'm wondering if there is a conflict with Shale. Is anyone else using this combination successfully? I've seen people say they did, but can't point directly at a mail thread for you. One critical link for Facelets to work is setting the default suffix context init parameter. Did you do that as well? context-param param-namejavax.faces.DEFAULT_SUFFIX/param-name param-value.xhtml/param-value !-- Or whatever your pages use -- /context-param Without this setting, JSF is going to assume the extension is .jsp Craig Based on instructions at the facelets wiki, this is what I've done so far: I've created a file named tomahawk.taglib.xml under /WEB-INF: ?xml version=1.0? !DOCTYPE facelet-taglib PUBLIC -//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN http://java.sun.com/dtd/facelet-taglib_1_0.dtd; facelet-taglib !-- Just in case my email client removes them for me, note that the namespace tags are included below -- namespacehttp://myfaces.apache.org/tomahawk/namespace tag tag-namecommandLink/tag-name component component-typeorg.apache.myfaces.component.html.ext.HtmlCommandLink/c omponent-type renderer-typeorg.apache.myfaces.renderkit.html.HtmlLinkRenderer/rende rer-type /component /tag /facelet-taglib I've registered the file in my web.xml: ... context-param param-namefacelets.LIBRARIES/param-name param-value/WEB-INF/tomahawk.taglib.xml/param-value /context-param ... I've referenced the namespace declared in the taglib file in the root html element of my page as such: xmlns:t=http://myfaces.apache.org/tomahawk; Is there something else I need to do on the Shale side to make this work? Thanks E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized. E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.
JSF 1.1 vs. JSF 1.2
I think I get it now (thanks to help from this list). If I want to use JSF 1.2 with Shale, I must use a J2EE 5 servlet container. However, I may not be able to convince my company to switch from Tomcat 5.5.* If that is the case, I need to decide between the following two setups: 1. JSF 1.2 Facelets or 2. JSF 1.1, Facelets Shale Practically speaking, the main improvements in JSF 1.2 may not offer too much to me since I'm using Facelets. Specifically: 1. EL unification. Since I'm not using JSPs, this isn't a big deal 2. Improved Messages. From what I've read, Shale's info/warn/error methods provide much of the same improvements to 1.1 as there is out of the box in 1.2. Finally, I'll need to consider bug fixes, like the multiple button press issue. In your experience, is developing JSF 1.2 far superior to JSF 1.1? Are there any major tradeoffs that I'm overlooking? Thanks for your time and any advice. E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.
RE: JSF 1.1 vs. JSF 1.2
If you want to run JSF 1.2 on Tomcat, you really want 6.0 not 5.5. It might be technically feasible to hack together a JSF 1.2 implementation that would execute on Tomcat 5.5, but it's hard to see how you could have a completely spec compliant implementation in the absence of JSP 2.1 (which is part of Tomcat 6; Tomcat 5 and 5.5 provide JSP 2.0). You're right, *I* really want Tomcat 6, but my employers are leery of its beta status. They are also concerned about supporting an additional container. Just curious ... is this based on a belief that JSF 1.2 + Facelets + Shale does not work (if it doesn't that is a bug that needs to be fixed), or that Shale does not provide you anything extra if you have JSF 1.2? I confess that I don't recall any details of which Shale features you are looking at from your previous comments ... but there is quite a lot of different things available. I didn't explain myself clearly, I'd prefer to use Shale in either case. My problem is that I may be stuck in Tomcat 5.5.17, which (for me) would necessitate using JSF 1.1. I need to decide if yesterday's setup is good enough, or if it's worth pushing my employers really hard to add a Tomcat 6 setup (and risk being thrown out on my rear). E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.
Swallowed Exceptions?
I have a Shale 1.0.3 + Facelets + JSF 1.1 setup running nicely. However, I observed a disconcerting problem. I neglected to package a necessary library (buisness code, not framework code) with my project and then ran the application. Normally, a bone-headed move like this would be rewarded with a stack trace a mile long. Surprisingly, the only error I saw was a 505 error reported in the browser. Nothing on the console and nothing in the logs. This issue is causing me a lot of anxiety because I tend to commit a large number of bone-headed moves. Is there a debug setting I need to add somewhere to ensure that Exceptions bubble all the way up? E-Mail messages may contain viruses, worms, or other malicious code. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective action against such code. Sender is not liable for any loss or damage arising from this message. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this e-mail by anyone else is unauthorized.
RE: Getting started...again.
That sounds great! Thanks for doing this and letting me know. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthias Wessendorf Sent: Tuesday, January 16, 2007 9:23 AM To: user@shale.apache.org Subject: Re: Getting started...again. James- I am creating a sorta kickstart project, using technologies like Apache MyFaces Facelets Apache Trinidad (formal Oracle ADF Faces) Shale (View and application.manager (test will follow soon)) JPA Toplink Essentials as the container I am using jetty. check here: http://code.google.com/p/facesgoodies/ -M On 1/15/07, Craig McClanahan [EMAIL PROTECTED] wrote: On 1/15/07, Reynolds, James [EMAIL PROTECTED] wrote: Steps 0 1 are complete :) I'm much closer as I can see Tomcat behaving as I'd expect, though I did end up with a couple errors in the log: 1. java.lang.NoClassDefFoundError: javax/el/ExpressionFactory This is supposed to be pulled in by the dependencies for MyFaces (commons-el?) if you're using JSF 1.1. It'll be part of the server if you're using JSF 1.2 (the RI, since MyFaces doesn't support this yet). 2. org.apache.commons.chain.web.ChainListener Make sure commons chain is not *also* in your Tomcat shared or common dirs. Commons-chain is definitely in my project, but I can't locate javax/el/ExpressionFactory in my jsf libs. Should this be in my server or J2EE libs? I'm attempting to use Tomcat 5.5.20 Does the prebuilt war in the 1.0.4 test builds work out of the box? If so, it'd be interesting to do a detailed comparison of JARs in yours versus that one. If not, we've got something else weird, because the out-of-the-box one runs for me. Craig On 1/15/07, Reynolds, James [EMAIL PROTECTED] wrote: I've been on a hiatus from Shale since changing jobs last year; however, my new company is considering it based on my gushing recommendation. Embarrassingly enough, I can't fire up the shale-blank application. When I run the app, I see the output below in the console then - nothing. No errors in tomcat or anything (that I can see). This output has changed since I last ran Shale. Do you see anything that might explain the silent failure? I've never tried it with the Shale libraries or facelets installed in Tomcat's common/lib directory ... FIrst thing I would try is a completely vanilla Tomcat install, with the Shale jars deployed inside the webapp (as they should default when shale-blank builds). Actually, the zeroth thing I would try is the 1.0.4 release instead of 1.0.3:-). Rahul is in the process of getting it out there; his test build is available at http://people.apache.org/~rahul/shale/v104/. Craig Thanks! cmd /c C:\apache-tomcat-5.5.20\bin\catalina.bat run Using CATALINA_BASE: C:\Documents and Settings\jReynolds\.IntelliJIdea60\system\tomcat_Unnamed_5094815 Using CATALINA_HOME: C:\apache-tomcat-5.5.20 Using CATALINA_TMPDIR: C:\apache-tomcat-5.5.20\temp Using JRE_HOME:C:\Java\jdk1.5.0_09 log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.Embedded). log4j:WARN Please initialize the log4j system properly. ContextListener: attributeAdded('org$apache$shale$view$VIEW_CALLBACKS', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.shale.tiger.FACES_CONFIG_CONFIG', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.config.RuntimeConfig', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.webxml.WebXml', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.StartupServletContextListener. FACES_INIT_DONE', 'true') ContextListener: attributeAdded('org$apache$shale$view$VIEW_CALLBACKS', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.shale.tiger.FACES_CONFIG_CONFIG', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.config.RuntimeConfig', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.webxml.WebXml', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.StartupServletContextListener. FACES_INIT_DONE', 'true') ContextListener: attributeRemoved('org.apache.shale.tiger.FACES_CONFIG_CONFIG', '[EMAIL PROTECTED]') ContextListener: attributeRemoved('org.apache.catalina.jsp_classpath', '/C:/apache-tomcat-5.5.20/webapps/servlets-examples/WEB-INF/classes/;/C: /apache-tomcat-5.5.20/common/classes/;/C:/apache-tomcat-5.5.20/common/i1 8n/tomcat-i18n-en.jar;/C:/apache-tomcat-5.5.20/common/i18n/tomcat-i18n-e s.jar;/C:/apache-tomcat-5.5.20/common/i18n/tomcat-i18n-fr.jar;/C:/apache -tomcat-5.5.20/common/i18n/tomcat-i18n-ja.jar;/C:/apache-tomcat-5.5.20/c ommon/lib/commons-beanutils-1.7.0.jar;/C:/apache-tomcat-5.5.20/common/li b/commons
RE: Getting started...again.
Oh, thank you! I'll drop my Tomcat version and go again. :) -Original Message- From: Hermod Opstvedt [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 11:01 AM To: user@shale.apache.org Subject: SV: Getting started...again. Hi Just don't attempt to use Shale with 5.5.20 and jdk5. It works with any version below 5.5.20 and jdk5. If your stuck to 5.5.20 you need to be running jdk1.4 Hermod -Opprinnelig melding- Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] På vegne av Matthias Wessendorf Sendt: 16. januar 2007 17:23 Til: user@shale.apache.org Emne: Re: Getting started...again. James- I am creating a sorta kickstart project, using technologies like Apache MyFaces Facelets Apache Trinidad (formal Oracle ADF Faces) Shale (View and application.manager (test will follow soon)) JPA Toplink Essentials as the container I am using jetty. check here: http://code.google.com/p/facesgoodies/ -M On 1/15/07, Craig McClanahan [EMAIL PROTECTED] wrote: On 1/15/07, Reynolds, James [EMAIL PROTECTED] wrote: Steps 0 1 are complete :) I'm much closer as I can see Tomcat behaving as I'd expect, though I did end up with a couple errors in the log: 1. java.lang.NoClassDefFoundError: javax/el/ExpressionFactory This is supposed to be pulled in by the dependencies for MyFaces (commons-el?) if you're using JSF 1.1. It'll be part of the server if you're using JSF 1.2 (the RI, since MyFaces doesn't support this yet). 2. org.apache.commons.chain.web.ChainListener Make sure commons chain is not *also* in your Tomcat shared or common dirs. Commons-chain is definitely in my project, but I can't locate javax/el/ExpressionFactory in my jsf libs. Should this be in my server or J2EE libs? I'm attempting to use Tomcat 5.5.20 Does the prebuilt war in the 1.0.4 test builds work out of the box? If so, it'd be interesting to do a detailed comparison of JARs in yours versus that one. If not, we've got something else weird, because the out-of-the-box one runs for me. Craig On 1/15/07, Reynolds, James [EMAIL PROTECTED] wrote: I've been on a hiatus from Shale since changing jobs last year; however, my new company is considering it based on my gushing recommendation. Embarrassingly enough, I can't fire up the shale-blank application. When I run the app, I see the output below in the console then - nothing. No errors in tomcat or anything (that I can see). This output has changed since I last ran Shale. Do you see anything that might explain the silent failure? I've never tried it with the Shale libraries or facelets installed in Tomcat's common/lib directory ... FIrst thing I would try is a completely vanilla Tomcat install, with the Shale jars deployed inside the webapp (as they should default when shale-blank builds). Actually, the zeroth thing I would try is the 1.0.4 release instead of 1.0.3:-). Rahul is in the process of getting it out there; his test build is available at http://people.apache.org/~rahul/shale/v104/. Craig Thanks! cmd /c C:\apache-tomcat-5.5.20\bin\catalina.bat run Using CATALINA_BASE: C:\Documents and Settings\jReynolds\.IntelliJIdea60\system\tomcat_Unnamed_5094815 Using CATALINA_HOME: C:\apache-tomcat-5.5.20 Using CATALINA_TMPDIR: C:\apache-tomcat-5.5.20\temp Using JRE_HOME:C:\Java\jdk1.5.0_09 log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.Embedded). log4j:WARN Please initialize the log4j system properly. ContextListener: attributeAdded('org$apache$shale$view$VIEW_CALLBACKS', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.shale.tiger.FACES_CONFIG_CONFIG', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.config.RuntimeConfig', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.webxml.WebXml', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.StartupServletContextListener. FACES_INIT_DONE', 'true') ContextListener: attributeAdded('org$apache$shale$view$VIEW_CALLBACKS', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.shale.tiger.FACES_CONFIG_CONFIG', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.config.RuntimeConfig', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.webxml.WebXml', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.StartupServletContextListener. FACES_INIT_DONE', 'true') ContextListener: attributeRemoved('org.apache.shale.tiger.FACES_CONFIG_CONFIG', '[EMAIL PROTECTED]') ContextListener: attributeRemoved('org.apache.catalina.jsp_classpath', '/C:/apache-tomcat-5.5.20/webapps/servlets-examples/WEB-INF/classes/;/C: /apache-tomcat-5.5.20/common/classes/;/C:/apache-tomcat-5.5.20
RE: Getting started...again.
I've been setting it up from scratch, since (oh the shame) I haven't used Maven yet. This is yet another reason why I'd better hop on the bandwagon and set it up. I'll check out that project too. Thanks so much! -Original Message- From: Hermod Opstvedt [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 12:46 PM To: user@shale.apache.org Subject: SV: Getting started...again. Hi How are you creating it? As a complete Maven2 project, or as Maven2 archetype? Reason for asking, is that I recently submitted Shale/Clay kickstart project (The first of more to come with other faces libs included). Take a look in the shale sandbox under maven Hermod -Opprinnelig melding- Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] På vegne av Matthias Wessendorf Sendt: 16. januar 2007 17:23 Til: user@shale.apache.org Emne: Re: Getting started...again. James- I am creating a sorta kickstart project, using technologies like Apache MyFaces Facelets Apache Trinidad (formal Oracle ADF Faces) Shale (View and application.manager (test will follow soon)) JPA Toplink Essentials as the container I am using jetty. check here: http://code.google.com/p/facesgoodies/ -M On 1/15/07, Craig McClanahan [EMAIL PROTECTED] wrote: On 1/15/07, Reynolds, James [EMAIL PROTECTED] wrote: Steps 0 1 are complete :) I'm much closer as I can see Tomcat behaving as I'd expect, though I did end up with a couple errors in the log: 1. java.lang.NoClassDefFoundError: javax/el/ExpressionFactory This is supposed to be pulled in by the dependencies for MyFaces (commons-el?) if you're using JSF 1.1. It'll be part of the server if you're using JSF 1.2 (the RI, since MyFaces doesn't support this yet). 2. org.apache.commons.chain.web.ChainListener Make sure commons chain is not *also* in your Tomcat shared or common dirs. Commons-chain is definitely in my project, but I can't locate javax/el/ExpressionFactory in my jsf libs. Should this be in my server or J2EE libs? I'm attempting to use Tomcat 5.5.20 Does the prebuilt war in the 1.0.4 test builds work out of the box? If so, it'd be interesting to do a detailed comparison of JARs in yours versus that one. If not, we've got something else weird, because the out-of-the-box one runs for me. Craig On 1/15/07, Reynolds, James [EMAIL PROTECTED] wrote: I've been on a hiatus from Shale since changing jobs last year; however, my new company is considering it based on my gushing recommendation. Embarrassingly enough, I can't fire up the shale-blank application. When I run the app, I see the output below in the console then - nothing. No errors in tomcat or anything (that I can see). This output has changed since I last ran Shale. Do you see anything that might explain the silent failure? I've never tried it with the Shale libraries or facelets installed in Tomcat's common/lib directory ... FIrst thing I would try is a completely vanilla Tomcat install, with the Shale jars deployed inside the webapp (as they should default when shale-blank builds). Actually, the zeroth thing I would try is the 1.0.4 release instead of 1.0.3:-). Rahul is in the process of getting it out there; his test build is available at http://people.apache.org/~rahul/shale/v104/. Craig Thanks! cmd /c C:\apache-tomcat-5.5.20\bin\catalina.bat run Using CATALINA_BASE: C:\Documents and Settings\jReynolds\.IntelliJIdea60\system\tomcat_Unnamed_5094815 Using CATALINA_HOME: C:\apache-tomcat-5.5.20 Using CATALINA_TMPDIR: C:\apache-tomcat-5.5.20\temp Using JRE_HOME:C:\Java\jdk1.5.0_09 log4j:WARN No appenders could be found for logger (org.apache.catalina.startup.Embedded). log4j:WARN Please initialize the log4j system properly. ContextListener: attributeAdded('org$apache$shale$view$VIEW_CALLBACKS', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.shale.tiger.FACES_CONFIG_CONFIG', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.config.RuntimeConfig', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.webxml.WebXml', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.StartupServletContextListener. FACES_INIT_DONE', 'true') ContextListener: attributeAdded('org$apache$shale$view$VIEW_CALLBACKS', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.shale.tiger.FACES_CONFIG_CONFIG', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.config.RuntimeConfig', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.webxml.WebXml', '[EMAIL PROTECTED]') ContextListener: attributeAdded('org.apache.myfaces.webapp.StartupServletContextListener. FACES_INIT_DONE', 'true') ContextListener: attributeRemoved