• Post Reply Bookmark Topic Watch Topic
  • New Topic

migrating from glassfish v2.x to glassfish v 3.0

 
sridhar kosna
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
HI to All,
i am trying to migrate from glassfish v2,x to glassfish v 3.0. its not purely migrating but the thing is my application was built in glassfish v2.x (jsf 1.2). now this application should be deployed in glassfish v3.0 (jsf 2.0). big deal is that most of the pages (new and edit) were built dynamically in my application.When i run the application after doing some modifications, duplicate id exception has been thrown where the page components were built dynamically. To overcome this i used setTransient(true). by using this exception has gone but dynamically built commandlinks and RichTabs are not working in the sense when i click on the commandlinks or tabs nothing is happening. processAction method is not being called. so please could anyone give me suggestions.
thanks & regards,
Sridhar Kosna.
 
Zachary Pry
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi sridhar.
I am guessing that your Managed Bean is session scoped ?
I am fairly new to JSF2.0, but I had the same problem. I fixed it by moving all dynamic creation code to request scoped managed bean. So I used session bean for storing session data and request bean for creating faces components.
That is solution for the duplicated id's problem. What about "setTransient(true)" - unfortunately I don't know what it does, nor am I familiar with the consequences of its use...
 
sridhar kosna
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thank you for your suggestions. ihave tried it but still that exception exists. setTransient(true) it will avoid duplicate ids in uicomponent tree . i had another question is it possible to use jsf 1.2 in glassfish v3.0 . because i think jsf 2.0 doesnot suppport richfaces 3.3.1 right ? please any other suggestions because it is causing me from past one week. And even i coudnt find exact bug location......
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!