Hi, Peter
The information specified in the GF specific descriptors are often
used to complement the information specified in the standard deployment
descriptors. For example, the standard descriptor could define a
resource reference with a logical JNDI name and the GF descriptor could
map the logical JNDI name of that resource to the physical JNDI name in
server.
The versions of the standard and GF specific descriptors can evolve
independently, as long as the descriptors are conformed to the declared
version of the schema/DTD. And all previous versions of standard and GF
specific descriptors are supported for backward compatibility, so the
set up you have should work on GF 4. I don't think the GlassFish plug in
for Eclipse need to enforce any constraints here.
- Hong
On 4/10/2013 5:21 AM, Peter Benedikovic wrote:
> Hi,
>
> is there any implicit correlation between Java EE descriptors and GF specific descriptors?
> Let me explain my question on example:
> I have web app which web.xml uses servlet 2.2 DTD. In the same app, I have glassfish-web.xml compliant to the latest glassfish-web-app_3_0-1.dtd. I want to deploy it on GF 4. Is it going to work?
>
> I am doing on Glassfish plugin for Eclipse and I am curious if the plugin should enforce some relationship between java ee descriptors and glassfish specific descriptors. Or the setup can be arbitrary.
>
> Regards,
> Peter Benedikovic