You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "Chris Webster (JIRA)" <be...@incubator.apache.org> on 2005/05/21 00:27:54 UTC

[jira] Commented: (BEEHIVE-612) ControlAssembler does not support server specific descriptors

     [ http://issues.apache.org/jira/browse/BEEHIVE-612?page=comments#action_65892 ]
     
Chris Webster commented on BEEHIVE-612:
---------------------------------------

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. 

> ControlAssembler does not support server specific descriptors
> -------------------------------------------------------------
>
>          Key: BEEHIVE-612
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-612
>      Project: Beehive
>         Type: New Feature
>   Components: Controls
>     Reporter: Chris Webster
>      Fix For: TBD

>
> 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. 

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira