The Bluestone template's about ready to check in, but first I'd like to get a second opinion on the tags it'll use, in particular whether any of them should use extra parameters to the existing @ejb tags rather than new tags of their own (looking at the other vendor subtasks, the trend seems to be to use specific tags for each of them?). They're all class-level tags. My choices are:
@bluestone:read-only enabled=<boolean.> or @bluestone:bean read-only=<boolean> or @ejb:bean bluestone-read-only=<boolean> @bluestone:pool initial-size=<int> cache-limit=<int> idle-timeout=<int> use-reaper=<boolean> reap-asynch=<boolean> (don't think there's much doubt about this one) @bluestone:entity-passivation enabled=<boolean> @bluestone:session-passivation enabled=<boolean> threshold=<int> or @bluestone:passivation enabled=<boolean> [threshold=<int>] or @bluestone:bean passivation=<boolean> [passivate-threshold=<int>] or @ejb:bean bluestone-passivation=<boolean> [bluestone-passivate-threshold=<int>] and similarly for the SFSB-only setting @bluestone:session timeout=<int> and MDB-only settings @bluestone:concurrent-message-processing enabled=<boolean> max-messages=<int> maximum-server-sessions=<int> server-session-idle-timeout=<int> @bluestone:connection-retry enabled=<boolean> @bluestone:jndi factory=<string> destination=<string> and lastly, there's @bluestone:ejb-ref type="colocated|distributed" jndi-name=<string> ref-name=<string> [app=<string> host=<string> port=<string>] or @ejb:ejb-ref bluestone-type="colocated|distributed" bluestone-jndi-name=<string> bluestone-ref-name=<string> [bluestone-app=<string> bluestone-host=<string> bluestone-port=<string>] (or perhaps pick up jndi/ref names from existing parameters) Any suggestions? Andrew. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
