[OS-webwork] Request attributes not passed to JSP
Hi, Is it known and intentional that some request attributes (such as queryString and pathInfo) are not passed to the JSP? I can do getParameters().isEmpty() but not getQueryString() != null. Thanks, Mathias --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] Single Quote in value
Hey all, Using WW 1.3. I have a label tag as such, ww:label label='Comments' name=comment/ the property comment resolves to frank's first comment and appearantly (from the stack trace below) the ValueStack/Query mechanism cannot deal with that. Is there something I can do to make up for this? It seems unreasonable to not allow our users to use a single quote. how have the rest of you avoided this problem? java.lang.IllegalArgumentException: missing matching end quote for query: frank's first comment at webwork.util.Query.throwIllegalArgumentException(Query.java:369) at webwork.util.Query.init(Query.java:260) at webwork.util.Query.getQuery(Query.java:32) at webwork.util.ValueStack.findValue(ValueStack.java:162) at webwork.view.taglib.WebWorkBodyTagSupport.findValue(WebWorkBodyTagSupport.ja va:57) at webwork.view.taglib.ui.ComponentTag.doEndTag(ComponentTag.java:152) at webwork.view.taglib.ui.LabelTag.doEndTag(LabelTag.java:31) Thanks, Frank --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] HTTP 204 Trick
Is it not possible to perform this 204 trick just by adding a new standard action that just sets the header and returns NONE? Similar to how the Redirect action works in WW1.x. One would then just chain to this action whenever one wants the header to be set? Would that work, or have I misunderstood something? Of course the HttpHeaderResult seems more flexible but perhaps also more complicated to implement. Cheers, Dick Zetterberg [EMAIL PROTECTED] - Original Message - From: Rickard Öberg [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 17, 2003 4:55 PM Subject: Re: [OS-webwork] HTTP 204 Trick Jason Carreira wrote: So you don't think there should be a HttpHeaderResult to enable you to return special Http header codes? That's not what I said. I was talking about the result codes, not view types. HttpHeaderResult seems fine to me. --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] HTTP 204 Trick
Dick Zetterberg wrote: Is it not possible to perform this 204 trick just by adding a new standard action that just sets the header and returns NONE? Similar to how the Redirect action works in WW1.x. One would then just chain to this action whenever one wants the header to be set? Would that work, or have I misunderstood something? That should work just fine. /Rickard --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Single Quote in value
I believe a patch has been made for this already (Jira WW-173 and WW-174), see also the included mail, where I think you already responded concerning this. You can find the patch in CVS. Cheers, Dick Zetterberg [EMAIL PROTECTED] - Original Message - From: Frank Febbraro [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 3:58 PM Subject: [OS-webwork] Single Quote in value Hey all, Using WW 1.3. I have a label tag as such, ww:label label='Comments' name=comment/ the property comment resolves to frank's first comment and appearantly (from the stack trace below) the ValueStack/Query mechanism cannot deal with that. Is there something I can do to make up for this? It seems unreasonable to not allow our users to use a single quote. how have the rest of you avoided this problem? java.lang.IllegalArgumentException: missing matching end quote for query: frank's first comment at webwork.util.Query.throwIllegalArgumentException(Query.java:369) at webwork.util.Query.init(Query.java:260) at webwork.util.Query.getQuery(Query.java:32) at webwork.util.ValueStack.findValue(ValueStack.java:162) at webwork.view.taglib.WebWorkBodyTagSupport.findValue(WebWorkBodyTagSupport.ja va:57) at webwork.view.taglib.ui.ComponentTag.doEndTag(ComponentTag.java:152) at webwork.view.taglib.ui.LabelTag.doEndTag(LabelTag.java:31) - Original Message - From: Frank Febbraro [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 07, 2003 3:44 PM Subject: Re: [OS-webwork] 1.3 LabelTag (JIRA: WW-174) Thanks guys, Will this make it into an official release of WW 1.3? If so any timeframe? Or should I just build WW locally to get that fix? - Original Message - From: Vedovato Paolo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 07, 2003 9:31 AM Subject: RE: [OS-webwork] 1.3 LabelTag (JIRA: WW-174) left it the way it is for backward compatibility reasons... cheers -paolo -Original Message- From: Erik Beeson [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] 1.3 LabelTag (JIRA: WW-174) Or, alternatively, it could be left the way it is now. I fixed the apostrophe in data problem (JIRA: WW-173), so the only issue now is one of orthogonality. --Erik --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Single Quote in value
Ha! I knew that looked familiar... (I'm so dumb) I think I use the property tag as a work around. I will look in CVS now. Sorry for wasting your time... - Original Message - From: Dick Zetterberg [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 11:23 AM Subject: Re: [OS-webwork] Single Quote in value I believe a patch has been made for this already (Jira WW-173 and WW-174), see also the included mail, where I think you already responded concerning this. You can find the patch in CVS. Cheers, Dick Zetterberg [EMAIL PROTECTED] - Original Message - From: Frank Febbraro [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 3:58 PM Subject: [OS-webwork] Single Quote in value Hey all, Using WW 1.3. I have a label tag as such, ww:label label='Comments' name=comment/ the property comment resolves to frank's first comment and appearantly (from the stack trace below) the ValueStack/Query mechanism cannot deal with that. Is there something I can do to make up for this? It seems unreasonable to not allow our users to use a single quote. how have the rest of you avoided this problem? java.lang.IllegalArgumentException: missing matching end quote for query: frank's first comment at webwork.util.Query.throwIllegalArgumentException(Query.java:369) at webwork.util.Query.init(Query.java:260) at webwork.util.Query.getQuery(Query.java:32) at webwork.util.ValueStack.findValue(ValueStack.java:162) at webwork.view.taglib.WebWorkBodyTagSupport.findValue(WebWorkBodyTagSupport.ja va:57) at webwork.view.taglib.ui.ComponentTag.doEndTag(ComponentTag.java:152) at webwork.view.taglib.ui.LabelTag.doEndTag(LabelTag.java:31) - Original Message - From: Frank Febbraro [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 07, 2003 3:44 PM Subject: Re: [OS-webwork] 1.3 LabelTag (JIRA: WW-174) Thanks guys, Will this make it into an official release of WW 1.3? If so any timeframe? Or should I just build WW locally to get that fix? - Original Message - From: Vedovato Paolo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 07, 2003 9:31 AM Subject: RE: [OS-webwork] 1.3 LabelTag (JIRA: WW-174) left it the way it is for backward compatibility reasons... cheers -paolo -Original Message- From: Erik Beeson [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] 1.3 LabelTag (JIRA: WW-174) Or, alternatively, it could be left the way it is now. I fixed the apostrophe in data problem (JIRA: WW-173), so the only issue now is one of orthogonality. --Erik --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] XWork and API Changes
How much longer until XWork's APIs are stable? Sincerely, Anthony Eden --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] XWork and API Changes
Jason and I are hoping for a beta release very soon. There are only a couple open issues for 1.0, so once the docs are satisfactory, a beta shouldn't be far off. -Pat - Original Message - From: Anthony Eden [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 7:35 PM Subject: [OS-webwork] XWork and API Changes How much longer until XWork's APIs are stable? Sincerely, Anthony Eden --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
