It isn't that I was concerned. It's just that I had disabled it (just
testing), and JSF didn't help me to find the error. In fact, often
MyFaces (or JSF in general) doesn't help very much to find errors,
altough they could be clearly mine like in this case. If you make a
mistake I would expect MyFaces to tell me, not just write something
that doesn't work.
My apologies.
al.
On 11/28/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> I can't understand for the life of me why someone would write a webapp
> that was complicated enough to justify JSF and still be concerned
> about browsers that don't support javascript. I'm sure there are some
> scenarios out there but if you can't count on javascript being enabled
> then IMO, you shouldn't be wasting your time with the overhead and
> complexities of JSF. Just use Struts or something simpler.
>
> sean
>
>
> On 11/28/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
> > JSF isn't designed to handle GET requests, so just modifying the link
> > wouldn't be sufficient. In any case, the parameters generated would
> > be far too large :) Take a look at a JSF form submit sometime.
> >
> > The idea of providing an error if you try to use JSF without
> > javascript isn't a bad one.
> > I'm not sure what to suggest, though. I don't think rendering a
> > message stating that you can't use links without javascript is the
> > best solution. Perhaps the server should simply throw a
> > FacesException if someone attempts to render a component that requires
> > javascript, and the parameter is set to false.
> >
> > Maybe some of the other committers can comment on this.
> >
> > On 11/28/05, Alberto Molpeceres <[EMAIL PROTECTED]> wrote:
> > > On 11/28/05, Mike Kienenberger (JIRA) <[email protected]> wrote:
> > > > [
> > > > http://issues.apache.org/jira/browse/MYFACES-882?page=comments#action_12358688
> > > > ]
> > > >
> > > > Mike Kienenberger commented on MYFACES-882:
> > > > -------------------------------------------
> > > >
> > > > Well, we can discuss it on the mailing lists, but the short answer is
> > > > that javascript is required to make the link submit the form. Normal
> > > > anchor tags can't submit forms, so the anchor tag has to use javascript
> > > > to click a submit button.
> > > >
> > >
> > >
> > > Hi Mike.
> > >
> > > I was just wondering, why something to "simply" should need
> > > javascript. I mean, why not simply add all needed parameters to the
> > > link?. Or if really that's not possible, it would be better just write
> > > a message like "don't use commandLink with js disabled" instead of
> > > just rendering a broken link.
> > >
> > > Don't get me worng, I know it's my failure if I don't know what the
> > > specification says, only I have lost around three hours looking for a
> > > solution and am a bit frustrated.
> > >
> > > al.
> > >
> >
>
--
Alberto Molpeceres
alberto.molpeceres @ linkingpaths.com
(+34) 661 304 614
Linking Paths
Francisco Maciá 11, 7º - 48014 Bilbao
(+34) 944 764 328
http://www.linkingpaths.com
