This is what i found is happening in jsp pages, we have defined some tags
with same ID in jsp page, jsf 1.1 would let you do that, but jsf 1.2 does
not like it, also what i have found that in tomohawck 1.2 it does not like
action="" as below, but works fine in jsf 1.1
<t:commandLink
style="color:black;padding-top:7px;font-weight:bold;font-size:14px;float:
right;margin-right: 50px" action="" value="(Opt Out)"
onclick="hideGuestRecognitionOverlay();return false;"/>
On Wed, Oct 5, 2011 at 1:10 PM, Mike Kienenberger <mkien...@gmail.com>wrote:
> I think you'll find it easier to migrate to 1.2 before trying to upgrade to
> 2.x.
>
> We migrated from 1.1 to 1.2 a few months back, but are still having issues
> when migrating to 2.x from 1.2.
>
> On Wed, Oct 5, 2011 at 10:33 AM, Ashish Kulkarni <
> ashish.kulkarn...@gmail.com> wrote:
>
> > Hi
> > Is there anyway to migrate from jsf 1.1 to 2.0 or 2.1, or is it a
> complete
> > rewrite?
> >
> > The exact error i have is as below
> >
> > This jsp page works fine in jsf 1.1,
> >
> > An exception occurred processing JSP page /jsf/welcome.jsp at line 378
> 375:
> > onchange="determineCoutryType('traveler-country','traveler-zip-label');"
> > 376: style="width:150px;margin-left:3em"> 377: <f:selectItem
> > itemLabel="All"
> > itemValue="All" /> 378: <f:selectItems id="countryList" 379:
> > value="#{tauckData.country3JSFList}" /> 380: </h:selectOneMenu></td> 381:
> > </tr> Stacktrace:
> >
> > Caused by:
> > javax.servlet.jsp.JspException - Duplicated component Id:
> > 'speak-form:countryList' for component: '{Component-Path : [Class:
> > javax.faces.component.UIViewRoot,ViewId: /jsf/welcome.jsp][Class:
> > javax.faces.component.html.HtmlForm,Id: speak-form][Class:
> > javax.faces.component.html.HtmlSelectOneMenu,Id: traveler-country][Class:
> > javax.faces.component.UISelectItems,Id: countryList]}'.
> >
> >
> >
> > On Wed, Oct 5, 2011 at 12:36 AM, Scott O'Bryan <darkar...@gmail.com>
> > wrote:
> >
> > > I see. I'm not sure what technologies your using, but 2.0 should be
> > > available for most things. I'm just saying because, with 2.1 coming
> > > down the pike, migrating to 1.2 at this point may not give you the
> > > longevity you desire. Your essentially upgrading into an already
> > > obsolete branch and you may find it necessary to move to 2.0 anyway.
> > >
> > > Just a thought.. ;)
> > >
> > > So what do you mean by duplicate variable names?
> > >
> > > Sent from my iPad
> > >
> > > On Oct 4, 2011, at 9:21 PM, Ashish Kulkarni <
> ashish.kulkarn...@gmail.com
> > >
> > > wrote:
> > >
> > > > I would love to go to 2.0, but i could not find any clear path of
> > > migration
> > > > from jsf 1.1.3 to 1.2, we have tomohawk 1.1.3 also in the mix
> > > >
> > > > On Tue, Oct 4, 2011 at 10:02 PM, Scott O'Bryan <darkar...@gmail.com>
> > > wrote:
> > > >
> > > >> Explain what you mean by duplicate variable names? And just out of
> > > >> curiosity, why are you moving to 1.2 instead of skipping to 2.0..
> Is
> > it
> > > a
> > > >> limitation of your ISP?
> > > >>
> > > >>
> > > >> On 10/04/2011 07:45 PM, Ashish Kulkarni wrote:
> > > >>
> > > >>> Hi
> > > >>> I was trying to migrate our application from jsf 1.1 to jsf 1.2 and
> > had
> > > >>> issues with duplicate variable names, this code worked fine in jsf
> > 1.1
> > > why
> > > >>> complain in jsf 1.2
> > > >>>
> > > >>>
> > > >>
> > > >
> > > >
> > > > --
> > > > Ashish
> > > > www.ayurwellness.com
> > > > www.mysoftwareneeds.com
> > >
> >
> >
> >
> > --
> > Ashish
> > www.ayurwellness.com
> > www.mysoftwareneeds.com
> >
>
--
Ashish
www.ayurwellness.com
www.mysoftwareneeds.com
