Modifying classes from the out of box portlet

Mohammed_Ahmed

Article Number: 17546523

Portal - Creating a unique duplicate to modify an out-of-the-box PortalBean portlet

As per the above KB item I want to modify the existing class to add some additional logic and put in the car file. Class extension is not an option here as it requires lot of changes. But step 9 mentions me to remove the classes, I just want to use the modified classes put in a new car file. Doesn't it access the files local to car file rather than going to original out of box portal bean.

9. Delete any classes in the \WEB–INF\classes folder.

NOTE: We delete the Vignette classes from your PortalBean duplicate because
it is not recommended to have two different PortalBeans in the system that
contain the same .class files. A conflict could occur if you deploy a
patched version of the original OOTB PortalBean in the future, then
redeploy your customized duplicate after that; the patched classes would
be overwritten by the older classes packaged in your PortalBean. For that
reason, we delete the Vignette classes from your duplicate. You can still
reference the Vignette class in your .PBD file and you can still
instantiate Vignette classes in your .jsp files and/or custom .class files.

Travis_Ebert

Quoted mohammed ahmed (mohammed.ahmed@chemtura.com) on 2011/06/09 14:07:

Article Number: 17546523

Portal - Creating a unique duplicate to modify an out-of-the-box PortalBean portlet

As per the above KB item I want to modify the existing class to add some additional logic and put in the car file. Class extension is not an option here as it requires lot of changes. But step 9 mentions me to remove the classes, I just want to use the modified classes put in a new car file. Doesn't it access the files local to car file rather than going to original out of box portal bean.

9. Delete any classes in the \WEB–INF\classes folder.

NOTE: We delete the Vignette classes from your PortalBean duplicate because
it is not recommended to have two different PortalBeans in the system that
contain the same .class files. A conflict could occur if you deploy a
patched version of the original OOTB PortalBean in the future, then
redeploy your customized duplicate after that; the patched classes would
be overwritten by the older classes packaged in your PortalBean. For that
reason, we delete the Vignette classes from your duplicate. You can still
reference the Vignette class in your .PBD file and you can still
instantiate Vignette classes in your .jsp files and/or custom .class files.

Nothing is read from car files at the execution time of a portalbean. The contents of car files are read and processed during deployment and written to the database and filesystem as appropriate. All portalbean classes are dropped into the same web app that portal is running in so any classes with the exact same name and package will collide.

---Travis