Hi, I'm wondering if anyone has any comments as to how they've dealt with the following issue with XDoclet, or alternative proposals?
I've been running XDoclet happily on a 1-codebase -> 1-customer setup, but now want to try & support a 2nd customer configuration, but my problem is that 95% of the code is common, including the files that XDoclet scans to generate the ejb.xml, for instance. What I was originally considering was a core project what generates a jar and a set of meta-inf files, with the customer-specific projects using the generated code but the problem that I'm foreseeing is how to handle the case where, say, a customer-specific implementation called by a (common) bean A want's to access a bean B that isn't currently specified in the bean A's JavaDoc (and thus not in the ejb.xml)? -- Best regards, Gwyn mailto:[EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
