Jason: I figured it out.
The element with the sourceID of "customerForm:sDocType" had a attribute
set as value="".
Which is an illegal syntax for a set operation...
This was getting past Tomcat, but when I moved to Java 1.6.0 and
Glassfish v2 b28/JSF 1.2 - I had not seen this before.
Thanks,
--Todd
-----Original Message-----
From: Jason Lee [mailto:lee_at_iecokc.com]
Sent: Tuesday, January 16, 2007 4:10 PM
To: users_at_javaserverfaces.dev.java.net
Subject: RE: Glassfish v2 b28: JSF 1.2: Illegal Syntax for Set Operation
error.
Hmmm. Have you updated that to the latest JSF, just to be sure? I'm
not sure what version b28 bundles, so that may not be necessary. I've
also had better luck (so far) with b32 nightlies, so you might try that.
I ran into that error just today when I tried, basically,
context.getApplication().createValueBinding("foo"), though I see no
reason your mark up would cause something like that. You might try
upgrading to the latest of both JSF and GF and see if the problem
persists.
-----
Jason Lee, SCJP
Programmer/Analyst
http://www.iec-okc.com
> -----Original Message-----
> From: Todd Patrick [mailto:Todd.Patrick_at_dtn.com]
> Sent: Tuesday, January 16, 2007 3:56 PM
> To: users_at_javaserverfaces.dev.java.net
> Subject: Glassfish v2 b28: JSF 1.2: Illegal Syntax for Set Operation
> error.
>
> What an eventful day.
>
> First, I've switched to Glassfish v2 b28.
>
> Now, when I run my application, when I fill out a h:inputText, such
> as:
>
> <h:inputText id="fLastName" size="30" maxlength="30" tabindex="4"
> value="#{customerSearch.lastName}"/>
>
> I return this message in my server.log file:
>
> sourceId=customerForm:sDocType[severity=(ERROR 2), summary=(Illegal
> Syntax for Set Operation), detail=(Illegal Syntax for Set
> Operation)];|WARNING: FacesMessage(s) have been enqueued, but may not
> have been displayed.
>
> sourceId=customerForm:sDocType[severity=(ERROR 2), summary=(Illegal
> Syntax for Set Operation), detail=(Illegal Syntax for Set
> Operation)]|#]
>
> I've never seen this before.
>
> What could possibility be the issue?
>
> Thanks,
>
> --Todd
>
> -----------------------------------------
> NOTICE: This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized use, disclosure or distribution is prohibited. If you
> are not the intended recipient, please contact the sender by reply
> email and destroy all copies of the original message.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_javaserverfaces.dev.java.net
> For additional commands, e-mail:
> users-help_at_javaserverfaces.dev.java.net
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_javaserverfaces.dev.java.net
For additional commands, e-mail: users-help_at_javaserverfaces.dev.java.net