Not so much for deployment, but for development tools.
If the user, through some tool, deletes the servlet in the main dd, then that tool can delete information related to that servlet in the app-server-specific dd. Again, servlets have names so this might not be the best example.
The id mechanism, IMHO, is used to establish relationships that tools need to have to be user friendly and to offer something like foreign key constraints in a database (if that analogy makes sense).
Brian
----Original Message Follows---- From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Servlet Spec Question Date: Wed, 28 May 2003 09:25:46 -0600
Let me see if I understand correctly:
In my web.xml I would put:
<web-app>
<servlet id="foo">
...
</servlet>
</web-app>In my web containers proprietary descriptor file I would put:
<servlet id="foo">
<!-- extra non-standard servlet parameters -->
...
</servlet>So when I deploy, the container will match up the extra description information in my proprietary descriptor with the element in the web.xml based on the id?
Thanks, -Phil
_________________________________________________________________
------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
