Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/JS2-11 Here is an overview of the issue: --------------------------------------------------------------------- Key: JS2-11 Summary: Offline (Maven -o) usage of o.a.j.tools.pamanager.DeployUtilities Type: Improvement Status: Unassigned Priority: Minor Project: Jetspeed 2 Versions: 2.0-dev/cvs Assignee: Reporter: Ate Douma Created: Thu, 15 Apr 2004 1:04 AM Updated: Thu, 15 Apr 2004 1:04 AM Environment: WindowsXP, J2SE1.4.2_03, Tomcat 4.1.29 Description: If I want to deploy a new portlet using o.a.j.tools.pamanager.DeployUtilities I'll need to have the web.xml DTD (web-app_2_3.dtd) available in my current working directoy otherwise it will fail. The method processWebXML() resolves the DTD using: new InputSource(new FileInputStream("./web-app_2_3.dtd")) If instead this would be resolved from the current classpath using: new InputSource(getClass().getResourceAsStream("web-app_2_3.dtd")) and the web-app_2_3.dtd file is put in the same directory as the DeployUtilities source file this restriction would be lifted (the DTD will automatically be deployed together with Jetspeed in the portal war). Another benifit is that even for online usage no remote loading of the DTD is needed anymore (now on every deployment). Note that the 2.3 DTD is currently available from the portal subproject directory and therefore used for the Jetspeed own portlet deployments. If this DTD would be moved to the above specified location the Jetspeed portlet deployments will still work and then also for external (offline) portlet deployments. I'll attach a patch file for if you would want to implement this (with the code change and the addition of the 2.3. DTD in portal/src/java/org/apache/jetspeed/tools/pamanager but NOT the removal of the DTD from portal/src/java/org/apache/jetspeed/portal). --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
