Regarding iPlanet Deployment descriptors.
posted 15 years ago
Back in the day, the promise of "deploy your EAR file in *any* J2EE compliant server" seemed possible.
However, I've been developing an application (uses both web components (servlets/jsp's) and ejb's) with the J2EE Reference Implementation.
Now if I attempt to deploy this EAR file onto iPlanet, it won't work, because surprise, iPlanet has a requirement for there to be a matching iPlanet-proprietary deployment descriptor for each of the *.xml files in the EAR and its contents.
Does anyone know how to write an iPlanet deploy descriptor (it involves GUIDS).. or know of a tool that will simply parse an existing XML file and spit out a properly formatted iPlanet XML file? And no, iPlanet of course doesn't supply one.
However, I've been developing an application (uses both web components (servlets/jsp's) and ejb's) with the J2EE Reference Implementation.
Now if I attempt to deploy this EAR file onto iPlanet, it won't work, because surprise, iPlanet has a requirement for there to be a matching iPlanet-proprietary deployment descriptor for each of the *.xml files in the EAR and its contents.
Does anyone know how to write an iPlanet deploy descriptor (it involves GUIDS).. or know of a tool that will simply parse an existing XML file and spit out a properly formatted iPlanet XML file? And no, iPlanet of course doesn't supply one.
| It is sorta covered in the JavaRanch Style Guide. |