Hi!

Malcolm Sparks wrote:
>
> On Mon, May 17, 1999 at 07:56:50AM +0200, Rickard �berg wrote:
> > Vlada:
> > Is it the intent of the EJB1.1 spec. authors that vendors should add
> > server specific tags to the EJB-JAR-XML which could be used by the
> > Deployer role? It seems logical to do so, and it would not break
> > interoperability (XML: gotta love it). If so, any guidelines on how
> > these tags should be constructed to allow EJB-JAR-XML files to contain
> > server specific tags for several servers at the same time?
> >
> > Thanks!
> >
> > /Rickard
> >
>
> As was mentioned by Constantine, namespaces in XML address this
> problem, without breaking the important notion of document validity.

Actually I'm not convinced one actually needs namesspaces for it.
Example:
<ejb-jar>
  <enterprise-beans>
  ...
  </enterprise-beans>
  <assembly-descriptor>
  ...
  </assembly-descriptor>
  <deployment-descriptor>
    <deployment>
    <description>Blah</description>
    <server-name>XS</server-name>
    ... whatever.. such as:
    <bean>
      <ejb-link>Account</ejb-ref>
      <shared-db>True</shared-db>
      <active-pool-max>100</active-pool-max>
      ...
    </bean>
    ...
    </deployment>
    <deployment>
    <server-name>Tengah</server-name>
    ... whatever ...
    </deployment>
    <server-name>Silverstream</server-name>
    ... whatever ...
    </deployment>
  </deployment-descriptor>
</ejb-jar>

This format will allow deployment info from several servers to happily
coexist in the same EJB-JAR XML descriptor. Unfortunately it seems as
deployment info will not be put into EJB-JAR, at least not in the XML
descriptor.

> On the subject of validation, is there any reason why it was decided
> not to specify any attributes in the tags for the XML format?

I think the reason is, as Vlada stated, that some attributes couldn't be
XML attributes because they needed to be multiline, so instead elements
only was chosen for consistency (BTW, a decision that I agree with).

> The DTD in EJB1.1 serves to validate the hierarchy used in the
> deployment descriptor, but not the content. I've been writing some XML
> descriptor examples, and notice there is nothing in the DTD, comments
> notwithstanding, to stop me specifying illegal values for any of the tags,
> <transaction-type> and <reentrant> tags, for example.

I don't see this as a problem as editors will be used to edit the XML
files, and there will be validators available which cover all nasty
rules.

/Rickard

--
Rickard �berg

@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to