A wise old hermit known only as Manuel Alzola <[EMAIL PROTECTED]> once
said:
> Are there any plans to support the new HP AS app server?. It seems an
> interesting choice.
> Manuel
I'm working on it, and have a hp-ejb-jar.xml template mostly done (this is
for version 8.0 as I couldn't find any DTDs/schemas for 7.3 files), but
I'm waiting to hear back on a couple of questions I'd had about it (I
don't actually use it myself, I'm just working from the schema file).
Perhaps you could help me?
The stateful session bean passivation settings have an attribute "root";
according to the schema "This attribute is the path to a local directory
indicating where the container should passivate instances." Is this
likely to change at all for different beans, or would all beans in a build
probably use the same directory? (it affects whether I get the value from
a class-level tag, or a setting on the <bluestone> subtask itself).
The entity bean CMP settings specify a persistence-manager, with an
optional third-party provider & version and an optional
concrete-bean-class-name suffix. Again, are these ever likely to vary on
different EJBs, or in practise would all the beans in a jar be using the
same settings? (if the latter, I can use a <bluestone> subtask setting and
they won't need to be specified in every bean). Also, are there any
particular default values for these (there's none specified in the XML
schema, but perhaps there's some default values used by Bluestone's tools
when creating a new bean?)
Regarding the ejb-refs settings for each bean, the schema seems to suggest
they should be grouped, first the co-located ones then a group for each
distributed location (app name, name server hostname and name server
port). If instead there was a new <distributed> section for each one,
would that still work or would it produce errors on deploying from having
multiple sections with the same settings?
Lastly, according to the schema for the hp-ejb-jar.xml, ejb-refs elements
should be contained within the enterprise-bean elements:
<xsd:element name="enterprise-bean">
...
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:element ref="stateful-session" minOccurs="0"/>
<xsd:element ref="stateless-session" minOccurs="0"/>
<xsd:element ref="entity" minOccurs="0"/>
<xsd:element ref="message-driven" minOccurs="0"/>
</xsd:choice>
<xsd:element ref="ejb-refs" minOccurs="0"/>
</xsd:sequence>
...
</xsd:element>
However, in the only sample DDs I can find that contain ejb-refs elements
(customer_hp_ejb.xml, estore_hp_ejb.xml and shoppingcard_hp_ejb.xml within
trailmaps\intermediate\hpas\trail_7\jps1.1.2\src\components) they occur
after all the enterprise-bean elements, i.e. as part of the main
hp-ejb-jar element. Which is correct? If you build and deploy the
JavaPetStore app from that trail, does it pick up the ejb mappings
correctly? (of course, since it's all local it may be impossible to tell
as the values used may be the defaults anyway)
For now, I'm assuming the schema is definitive and they've got it wrong in
the PetStore files.
Andrew.
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
