ControlAssembler does not support server specific descriptors

• Key: BEEHIVE-612
• Type: New Feature
• Status: Open
• Priority: Major
• Assignee: Unassigned
• Reporter: Chris Webster
• Component/s: Controls

Description

The control assemble framework does not provide a way to access the server specific deployment descriptors. This presents a problem for applications which are deployed to servers similar to the J2EE 1.4 application server which requires that a resource such as JDBC be described in the server specific descriptor. The typical description is something like:
  resource
     jndi-name
     server-jndi-name

Which binds the generic resource declaration to the specific resource on the server. This will likely require some generic jndi annotation on the control itself to facilitate this generation.

Comments

[Eddie O'Neil]

Chris -- I definitely agree that this is something we should be clear about. Given that this is a new feature, I don't think we'll get to it in in the next couple of weeks, so I'm going to push to TBD.

[Chris Webster]

If this capability is not part of the standard control generation model, this would force a control client to edit the server specific deployment descriptor out of band. If I am using a JMS control, the standard deployment descriptor would be generated to include a destination and resource reference (assuming J2EE 1.4). However, the control author would not be able to generate anything into the server specific descriptor, so the control client would have to build the control (to see what deployment descriptor entries are created) and then hand edit the server specific descriptor.