Volker: why do you think forceId causes more problems than it solves?  IMHO, it's the opposite, the naming containers cause way more problems than they solve. 

Travis

On 1/6/06, Volker Weber <[EMAIL PROTECTED]> wrote:
Hi,

can't you use these created ids in you _javascript_?

If you set a id to the form component, and to all other namingContainer
components, you will get defined ids for all your components and can
work with them in your scripts.

IMHO forceId makes more problems than it solves.

Regards
  Volker

Marti, Adrian (Adrian) wrote:
> Hello all,
>
>
>
> First post, hopefully not too common a question.
>
>
>
>
>
>             Working on a project with a lot of preexisting _javascript_
> functions where the id's of components need to be exactly what is
> expected. JSF seems to want to prefix all of my component id's with the
> form id.
>
>
>
>             Such as
>
>                         <h:form id="acctform">
>
>
>
>                         <h:inputText id="firstInput"   … />
>
>                         … </h:form>
>
>
>
>             Will show up in the html with an id="acctform:firstInput".
> This obviously breaks the _javascript_. I have found the forceId attribute
> for Tomahawk components but haven't seen anything for the regular
> components. Anyone have any advice?
>
>
>
>
>
> Thanks,
>
> Adrian
>
>
>
>
>

--
Don't answer to From: address!
Mail to this account are droped if not recieved via mailinglist.
To contact me direct create the mail address by
concatenating my forename to my senders domain.

Reply via email to