RE: JSF - Shale transition
What do you mean by inferior if you are interested in performance. Is the overhead of the dialog/navigation processing pretty high? -Original Message- From: Dakota Jack [mailto:[EMAIL PROTECTED] Sent: Thursday, September 08, 2005 4:19 PM To: Struts Users Mailing List Subject: Re: JSF - Shale transition Well, have you considered classic struts? Shale is really meant for people who are trying to change an application from JSF to Struts, and not everyone, including myself, think this is a good idea. Shale is not Struts improved but a transition to something entirely different, and inferior in my opinion, if you are interested in performance. On 9/8/05, Walton, Kaleb (ISS Southfield) [EMAIL PROTECTED] wrote: We're wanting to go from our home-brewed method of interaction using jsps and servlets that are not very consistent in their expression (other than the general jsp/servlet specs) to something that defines interactions more concretely. Our current frustrations include form handling, page transitions, forwarding, etc. Regards, Kaleb -Original Message- From: Dakota Jack [mailto:[EMAIL PROTECTED] Sent: Thursday, September 08, 2005 12:44 AM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: JSF - Shale transition Moving from Struts to JSF is moving to a more defined framework? That is pretty difficult to grasp. Could you explain? On 9/6/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 9/6/05, Walton, Kaleb (ISS Southfield) [EMAIL PROTECTED] wrote: Hey all, As I had mentioned in a previous post, our team is looking to move towards a more well defined web framework. From my limited experience using Shale (ran the shale-use-cases) I'm not feeling very confident that we could use it *right away*. I wanted to ask for opinions on what would be a gradual step for us to take towards the Shale framework (once it's stable enough to use in a production environment). For example, would JSF + Spring be a good combo that would make for an easy transition to Shale? Struts + WebFlow + Spring? Etc.. Do the aforementioned framework combinations even matter? Will Shale just add another layer on top or glue together with what we would have already developed? Although I've been reading up on Shale quite a bit, my understanding is still limited so please excuse me if these questions are easily found through already documented sources. If they are, please share where they can be found :) The key to choosing a transition approach is what you want to use for the front controller part of your architecture durng the interim. If you're starting from Struts, a straightforward path would be to use the integration library to start switching your pages to using JSF components instead of Struts HTML tags (without having to modify your actions), followed by a migration of the back-end logic to using JSF's front controller and request processing lifecycle. If, on the other hand, you decide to commit to JSF's controller early rather than late, you might as well just use Shale along with it from the beginning. Unlike the way that other frameworks deal with JSF, Shale *assumes* you will be using the JSF controller architecture, and it just adds ease of use around problems you'll face anyway. It doesn't try to treat JSF as purely a component architecture. Craig McClanahan Regards, Kaleb -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- You can lead a horse to water but you cannot make it float on its back. ~Dakota Jack~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- You can lead a horse to water but you cannot make it float on its back. ~Dakota Jack~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSF - Shale transition
I should've shut my mouth earlier :). Kaleb -Original Message- From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] Sent: Friday, September 09, 2005 12:18 PM To: Struts Users Mailing List Subject: Re: JSF - Shale transition I prefer to do all my webapps in Assembly running on dedicated hardware with no OS at all. Beat *THAT* performance! ;) Frank Gary VanMatre wrote: What do you mean by inferior if you are interested in performance. Is the overhead of the dialog/navigation processing pretty high? In perspective, vanilla servlet programming is faster than Struts. Isn't it relative to what you *value* in a web framework. Gary -Original Message- From: Dakota Jack [mailto:[EMAIL PROTECTED] Sent: Thursday, September 08, 2005 4:19 PM To: Struts Users Mailing List Subject: Re: JSF - Shale transition Well, have you considered classic struts? Shale is really meant for people who are trying to change an application from JSF to Struts, and not everyone, including myself, think this is a good idea. Shale is not Struts improved but a transition to something entirely different, and inferior in my opinion, if you are interested in performance. On 9/8/05, Walton, Kaleb (ISS Southfield) [EMAIL PROTECTED] wrote: We're wanting to go from our home-brewed method of interaction using jsps and servlets that are not very consistent in their expression (other than the general jsp/servlet specs) to something that defines interactions more concretely. Our current frustrations include form handling, page transitions, forwarding, etc. Regards, Kaleb -Original Message- From: Dakota Jack [mailto:[EMAIL PROTECTED] Sent: Thursday, September 08, 2005 12:44 AM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: JSF - Shale transition Moving from Struts to JSF is moving to a more defined framework? That is pretty difficult to grasp. Could you explain? On 9/6/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 9/6/05, Walton, Kaleb (ISS Southfield) [EMAIL PROTECTED] wrote: Hey all, As I had mentioned in a previous post, our team is looking to move towards a more well defined web framework. From my limited experience using Shale (ran the shale-use-cases) I'm not feeling very confident that we could use it *right away*. I wanted to ask for opinions on what would be a gradual step for us to take towards the Shale framework (once it's stable enough to use in a production environment). For example, would JSF + Spring be a good combo that would make for an easy transition to Shale? Struts + WebFlow + Spring? Etc.. Do the aforementioned framework combinations even matter? Will Shale just add another layer on top or glue together with what we would have already developed? Although I've been reading up on Shale quite a bit, my understanding is still limited so please excuse me if these questions are easily found through already documented sources. If they are, please share where they can be found :) The key to choosing a transition approach is what you want to use for the front controller part of your architecture durng the interim. If you're starting from Struts, a straightforward path would be to use the integration library to start switching your pages to using JSF components instead of Struts HTML tags (without having to modify your actions), followed by a migration of the back-end logic to using JSF's front controller and request processing lifecycle. If, on the other hand, you decide to commit to JSF's controller early rather than late, you might as well just use Shale along with it from the beginning. Unlike the way that other frameworks deal with JSF, Shale *assumes* you will be using the JSF controller architecture, and it just adds ease of use around problems you'll face anyway. It doesn't try to treat JSF as purely a component architecture. Craig McClanahan Regards, Kaleb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSF - Shale transition
We're wanting to go from our home-brewed method of interaction using jsps and servlets that are not very consistent in their expression (other than the general jsp/servlet specs) to something that defines interactions more concretely. Our current frustrations include form handling, page transitions, forwarding, etc. Regards, Kaleb -Original Message- From: Dakota Jack [mailto:[EMAIL PROTECTED] Sent: Thursday, September 08, 2005 12:44 AM To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: JSF - Shale transition Moving from Struts to JSF is moving to a more defined framework? That is pretty difficult to grasp. Could you explain? On 9/6/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 9/6/05, Walton, Kaleb (ISS Southfield) [EMAIL PROTECTED] wrote: Hey all, As I had mentioned in a previous post, our team is looking to move towards a more well defined web framework. From my limited experience using Shale (ran the shale-use-cases) I'm not feeling very confident that we could use it *right away*. I wanted to ask for opinions on what would be a gradual step for us to take towards the Shale framework (once it's stable enough to use in a production environment). For example, would JSF + Spring be a good combo that would make for an easy transition to Shale? Struts + WebFlow + Spring? Etc.. Do the aforementioned framework combinations even matter? Will Shale just add another layer on top or glue together with what we would have already developed? Although I've been reading up on Shale quite a bit, my understanding is still limited so please excuse me if these questions are easily found through already documented sources. If they are, please share where they can be found :) The key to choosing a transition approach is what you want to use for the front controller part of your architecture durng the interim. If you're starting from Struts, a straightforward path would be to use the integration library to start switching your pages to using JSF components instead of Struts HTML tags (without having to modify your actions), followed by a migration of the back-end logic to using JSF's front controller and request processing lifecycle. If, on the other hand, you decide to commit to JSF's controller early rather than late, you might as well just use Shale along with it from the beginning. Unlike the way that other frameworks deal with JSF, Shale *assumes* you will be using the JSF controller architecture, and it just adds ease of use around problems you'll face anyway. It doesn't try to treat JSF as purely a component architecture. Craig McClanahan Regards, Kaleb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- You can lead a horse to water but you cannot make it float on its back. ~Dakota Jack~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSF - Shale transition
Hey all, As I had mentioned in a previous post, our team is looking to move towards a more well defined web framework. From my limited experience using Shale (ran the shale-use-cases) I'm not feeling very confident that we could use it *right away*. I wanted to ask for opinions on what would be a gradual step for us to take towards the Shale framework (once it's stable enough to use in a production environment). For example, would JSF + Spring be a good combo that would make for an easy transition to Shale? Struts + WebFlow + Spring? Etc.. Do the aforementioned framework combinations even matter? Will Shale just add another layer on top or glue together with what we would have already developed? Although I've been reading up on Shale quite a bit, my understanding is still limited so please excuse me if these questions are easily found through already documented sources. If they are, please share where they can be found :) Regards, Kaleb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Shale] Shale with Tiles web app example - was CSS not working with JSF
Geeta, I'd like to get your app up and running, although, I'm having trouble. I keep getting Assertion Failed errors when trying to get to index.faces or index.jsp. Any ideas? :) Thanks! Regards, Kaleb -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 11:54 AM To: Rick Reumann Cc: [EMAIL PROTECTED]; Struts Users Mailing List Subject: Re: [Shale] Shale with Tiles web app example - was CSS not working with JSF Sure thing. I would love to work with you and come up with something useful. I too am currently working on a web app which would demo Shark (the open source workflow engine). I already had written it using Struts, but now am attempting to rewrite that using Shale. Not sure how much success I will have plus may not be of that much interest to the community at large.. I think a simple CRUD app like you are working on will be more useful. So let me know if I can help..:) Geeta Rick Reumann [EMAIL PROTECTED] wrote on 08/26/2005 11:45:53 AM: Cool thanks so much! Probably together we can come up with some good stuff. I'm going to work on a simple CRUD app for demo purposes and I'll end up using tiles also so your app will help me. Thanks again. [EMAIL PROTECTED] wrote the following on 8/26/2005 11:33 AM: Hi Rick, bjester, anyone else who's interested: As promised, I have uploaded a very trivial app which integrates Shale and Tiles using the new code which David Geary committed a couple of days back (btw, I built the jars here using the source from a couple of days back.. so am not sure if they are different from what's available now..): http://www.sightsoftware.com/shale/ Please note that I am a complete newbie at this whole Shale thing so it is perhaps best not to learn any Shale using this app..:) Also, you will doubtless find better ways of doing almost everything I've done. All comments and suggestions will be gratefully received. Thanks! Geeta -- Rick -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. CONFIDENTIALITY NOTICE:This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or protected health information. Any duplication, dissemination, action taken in reliance upon, or other use of this information by persons or entities other than the intended recipient is prohibited and may violate applicable laws. If this email has been received in error, please notify the sender and delete the information from your system. The views expressed in this email are those of the sender and may not necessarily represent the views of IntelliCare. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Shale] Shale with Tiles web app example - was CSS not working with JSF
) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198) at com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChai n.java:99) at org.apache.shale.faces.ShaleApplicationFilter.doFilter(ShaleApplicationF ilter.java:280) at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain. java:70) at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.ja va:163) at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.j ava:208) at com.caucho.server.hmux.HmuxRequest.handleRequest(HmuxRequest.java:388) at com.caucho.server.port.TcpConnection.run(TcpConnection.java:341) at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:467) at com.caucho.util.ThreadPool.run(ThreadPool.java:408) at java.lang.Thread.run(Thread.java:595) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 12:51 PM To: Struts Users Mailing List Subject: RE: [Shale] Shale with Tiles web app example - was CSS not working with JSF Walton, Kaleb \(ISS Southfield\) [EMAIL PROTECTED] wrote on 08/26/2005 12:48:16 PM: Geeta, I'd like to get your app up and running, although, I'm having trouble. I keep getting Assertion Failed errors when trying to get to index.faces or index.jsp. Any ideas? :) Could you post the stack trace? I know I hav eseen that error before, but can't remeber how I solved it. Thanks! Regards, Kaleb Geeta - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Shale] Shale with Tiles web app example - was CSS not working with JSF
Nope - downloaded and deployed. One note though - I'm using Resin 3.0.12 rather than Tomcat. Don't worry about it not working for me - I realize it was a quick test implementation. I'm just trying to learn like the rest of you :) Regards, Kaleb -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 1:08 PM To: Struts Users Mailing List Subject: RE: [Shale] Shale with Tiles web app example - was CSS not working with JSF Walton, Kaleb \(ISS Southfield\) [EMAIL PROTECTED] wrote on 08/26/2005 12:54:19 PM: javax.faces.FacesException: Assertion Failed at com.sun.faces.util.Util.doAssert(Util.java:1302) at com.sun.faces.taglib.jsf_core.ViewTag.getComponentType(ViewTag.java:241) at javax.faces.webapp.UIComponentTag.createComponent(UIComponentTag.java: 10 13) at javax.faces.webapp.UIComponentTag.createChild(UIComponentTag.java:1036) at javax.faces.webapp.UIComponentTag.findComponent(UIComponentTag.java:749) at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:429) at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:105) at _jsp._layout._layout__jsp._jspService(layout/layout.jsp:7) Hmm.. Not that illuminating to me, it isn't!... My version of layout/layout.jsp:7 just says f:view so I am not sure why that would be a problem.. I have currently hosed my application entirely (:( so am in a bit of a mess myself, so am not sure how I can help. Sorry! Hopefully somebody will tell us what this error means..? Btw, you didn't change anything in the war you downloaded, right? ..just grasping for straws here.. Geeta - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Shale/JSF/Java posts
I'd have to respectfully disagree - it doesn't belong as a subproject under MyFaces as it encapsulates and integrates MyFaces along with other prominent frameworks. If anything it will eventually deserve its own Apache project. Regards, Kaleb -Original Message- From: David G. Friedman [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 5:34 PM To: Struts Users Mailing List Subject: RE: Shale/JSF/Java posts From: Craig McClanahan [mailto:[EMAIL PROTECTED] I just need to clarify one detail ... Shale is a Struts sub-project, so such questions *are* on topic for this list. Prefixing the subject with [shale] is certainly appropriate, just like prefixing a Tiles question with [tiles] would be. Although I'm interested in Shale and JSF (MyFaces), I no longer think Shale should be a sub-project under Struts. I feel it belongs as a sub-project under the Apache MyFaces top-level project now that MyFaces is part of the Apache family. Struts-Faces still has a place on this list but I really don't think Shale belongs here anymore. Do I need to take this opinion to the MyFaces and Struts developer lists rather than here? -David, due back in 4+ hours to read any storm of replies P.S. Yes, I do subscribe to the Myfaces User List. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[SHALE] Are we there yet?
A similar question has been asked once since I joined this list - so I apologize in advance if this question has been asked numerous times before. A colleague of mine and I are researching Shale for potential use in a production environment. Our timeline is pretty open - we're looking to implement some set of frameworks within the next year or so. Shale piqued our interest as it integrated and supported many of the frameworks we are looking to introduce (Spring, Spring WebFlow, JSF, JUnit tests, validation, etc). I actually have a few questions: 1) Is Shale development still at full tilt, or has it weaned in leiu of Java conferences coming to an end or not as much developer time available? 2) I've been actively following the development of Shale for the past few months and haven't found many news updates recently (hopefully that means the developers are busy developing and have no time to post updates). Are there any other more frequently updated resources that I may not be aware of? I currently check the Shale Wiki, David Geary's Blog, Craig's Blog, struts.apache.org and general googling. 3) When's the next big regurgitation of code into the trunk ? :) What I have read and seen (just yesterday we built and brought up the use-cases under Resin 3.0.12) I have been very excited about. Although I noticed a bug right off the bat (probably the state bug related to the ViewController as outlined in the wiki), I'm still very interested in using this framework for our product. I think the Shale framework is very promising and I applaud the speed in which it has gone from conceptual to tangible. My only fear is that we'll need to move to a new set of frameworks before Shale becomes dependable for production use :). Thanks! Regards, Kaleb Walton
RE: [SHALE] Are we there yet?
Just subscribed to dev list which should also help me to develop a conception of the speed of development. I would assume I was talking about 35066 since it was related to the dialog state. In my usual trial/error testing I removed an h:outputText tag and replaced it with some straight text and it spat out an error (if you want the stacktrace I can bring up my box and provide it to you). I had to restart resin to be able to continue my poking :). Regarding the statuses within the JavaDocs - excuse me if I am misunderstanding something simple - from what I gather, I should be weary of heavily developing with anything that isn't in Evolving+ state as there might be backwards-incompatible changes? Thanks again for the speedy response! Regards, Kaleb -Original Message- From: Craig McClanahan [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 1:11 PM To: Struts Users Mailing List Subject: Re: [SHALE] Are we there yet? On 8/25/05, Walton, Kaleb (ISS Southfield) [EMAIL PROTECTED] wrote: A similar question has been asked once since I joined this list - so I apologize in advance if this question has been asked numerous times before. A colleague of mine and I are researching Shale for potential use in a production environment. Our timeline is pretty open - we're looking to implement some set of frameworks within the next year or so. Shale piqued our interest as it integrated and supported many of the frameworks we are looking to introduce (Spring, Spring WebFlow, JSF, JUnit tests, validation, etc). I actually have a few questions: 1) Is Shale development still at full tilt, or has it weaned in leiu of Java conferences coming to an end or not as much developer time available? It proceeds apace, subject (as with all open source efforts) to vagaries of day job schedules and travel. There's a roadmap for a 1.0 milestone release posted on the Wiki: http://wiki.apache.org/struts/ShaleRelease100 which I see needs to be updated ... Gary just checked in fixes for a bunch of the Clay issues last night (part of the delay was waiting for his new committer capabilities to be set up on the ASF infrastructure). 2) I've been actively following the development of Shale for the past few months and haven't found many news updates recently (hopefully that means the developers are busy developing and have no time to post updates). Are there any other more frequently updated resources that I may not be aware of? I currently check the Shale Wiki, David Geary's Blog, Craig's Blog, struts.apache.org and general googling. You'll see blog entries occasionally, but the best way to keep track of what's going on is actually to subscribe to the Struts developer list (to subscribe send an empty message to [EMAIL PROTECTED]) and watch the SVN commit messages and Shale-related Bugzilla updates that go by. 3) When's the next big regurgitation of code into the trunk ? :) What I have read and seen (just yesterday we built and brought up the use-cases under Resin 3.0.12) I have been very excited about. Although I noticed a bug right off the bat (probably the state bug related to the ViewController as outlined in the wiki), I'm still very interested in using this framework for our product. Are you talking about issue 35066? If not, which one? For 35066 in particular, I'm thinking that we should defer that to a 1.0.1 milestone, because pretty much everything else has been taken care of. I think the Shale framework is very promising and I applaud the speed in which it has gone from conceptual to tangible. My only fear is that we'll need to move to a new set of frameworks before Shale becomes dependable for production use :). Regarding the API stability of the various packages, you'll definitely want to go to the Core Library javadocs: http://people.apache.org/~craigmcc/shale-core-javadocs/ and scroll down to the API Package Target Audiences and Stability Ratings section. Application developers should use only the APIs in packages targeted to Developer, and the table lists the projected stability of the APIs. For instance, the view controller stuff is marked Evolving, which means we're paying attention to backwards compatibility (for that package) even before a General Availability release. Thanks! Regards, Kaleb Walton Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tiles standalone implementation
I'm in the process of building the Shale trunk and have one dependency left to resolve. The build.properties calls for a build of the Tiles standalone distribution. I have found what seems to be a Tiles distro but cannot seem to build it without the Struts 1.3.0 core libraries (which I cannot find anywhere on apache.org). Can anyone lead me in the right direction? If I'm leaving something crucial out in order to properly get help, please let me know. Thanks! Regards, Kaleb
RE: Tiles standalone implementation
Thanks! I must have been looking around in all the wrong places ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 10:07 AM To: Struts Users Mailing List Subject: Re: Tiles standalone implementation Ah I think I actually found this .. Here it is: http://cvs.apache.org/builds/jakarta-struts/nightly/sandbox/tiles-core/ Regards, Geeta Walton, Kaleb \(ISS Southfield\) [EMAIL PROTECTED] wrote on 08/24/2005 10:02:10 AM: I'm in the process of building the Shale trunk and have one dependency left to resolve. The build.properties calls for a build of the Tiles standalone distribution. I have found what seems to be a Tiles distro but cannot seem to build it without the Struts 1.3.0 core libraries (which I cannot find anywhere on apache.org). Can anyone lead me in the right direction? If I'm leaving something crucial out in order to properly get help, please let me know. Thanks! Regards, Kaleb -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. CONFIDENTIALITY NOTICE:This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or protected health information. Any duplication, dissemination, action taken in reliance upon, or other use of this information by persons or entities other than the intended recipient is prohibited and may violate applicable laws. If this email has been received in error, please notify the sender and delete the information from your system. The views expressed in this email are those of the sender and may not necessarily represent the views of IntelliCare. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem With NOT EMPTY Using the c:when ... Tag
I may be mistaken with the version of EL you're using, but I use syntax
such as:
${!empty logRows}
Less typing and its easier on the eyes ;-)
Regards,
Kaleb
-Original Message-
From: Rahul Akolkar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 24, 2005 2:29 PM
To: Struts Users Mailing List
Subject: Re: Problem With NOT EMPTY Using the c:when ... Tag
On 8/24/05, Caroline Jen [EMAIL PROTECTED] wrote:
I use the NOT EMPTY to do the testing. I have
snip/
javax.servlet.jsp.JspException: An error occurred while evaluating
custom action attribute test with value ${NOT EMPTY log
Rows}: Encountered EMPTY, expected one of [},
snap/
Keywords, in many languages, including JSP 2.0 EL are case sensitive.
Questions purely about JSTL or EL are better addressed to
taglibs-user@jakarta.apache.org
-Rahul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
