Hi, I think i was a bit unclear in my lasst post.. sorry
A real wold example: Lets say i have a jar file conting some common beans, which i would like to use in a number of projects. I.e., deploy in several applicaitons. The source for these beans reside in their own project (common), not in each of the other projects using the common stuf.. Now, to deploy several instances of the same common bean in the app server, each of the projects using this bean must register it under different names in the JNDI, to do this each project must add this bean to its ejb-jar.xml file and to its jboss.xml for the JNDI stuff. Ejb-jar.xml is taken care of with a session.xml in the root of the merge dir, but to add this bean, xxx.yyy.ABean to jboss.xml i must use a file called <mergedir>/xxx/yyy/jboss-ABean.xml. Now if the source for ABean was included in this project in <src>xxx/yyy/ABean.java, XDoclet would merge the JNDI info from <mergedir>/xxx/yyy/jboss-ABean.xml into this projects jboss.xml, but since the source is located in another project (common) xdoclet wont use the jboss-ABean.xml merge file... and that is rational behaviour!! What my last post did'nt say clearly enough, was that it would be possible to deploy external beans in a project if xdoclet had some additional merge points in jboss_xml.xdt. E.g., a jboss-session-beans.xml and a jboss-entity-beans.xml which should placed in the root of mergedir and correspond to session-beans.xml and entity-beans.xml, and just contain the jboss specific things? I havent cheked but perhaps correspoonding merge points are needed for jaws.xml and jbosscmp-jdbc.xml?!?! I really hope i was a bit more clear this time (but im not sure:). Tell if i wasnt... Commonts on this, is it a valid request? BR Torsten > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Ara > Abrahamian > Sent: 2. juli 2002 20:54 > To: 'Torsten Terp'; [EMAIL PROTECTED] > Subject: RE: [Xdoclet-user] Feature request/clarification > > > > As far as I can tell it is not possible to add application > > server specific deployment info about external class files > > used in an application. I.e., if i include a class file in > > my app containing an EJB, the merge feature can only be > > used to add bean info to ejb-jar.xml, not jboss.xml etc. > > > > Its my understanding that bean info in the mergedir is only > > added if xdoclet has processed a java file in the src dir > > with the same directory structure. Because of this jndi info > > etc. are not added, while ejb-jar.xml info IS added (ejb-jar.xml > > info is placed in session.xml or entity.xml in the root of merge > > dir, hence it will be included, despite of the fact that a java > > source file is not present for this bean) > > > > Can someone please verify this? If i am indeed correct on this > > can someone tell me if this is a feature that the xdoclet team > > is thinking about adding?? > > Adding what kind of feature? > > For java files we look at the @tags and generate various stuff for you. > For class files there's no such a thing, we just provide some merge > points. <deploymentdescriptor/> has some merge points, you can define > external classes that way. For <jboss/> some merge points are indeed > provided but if a merge point is missing then let us know about it and > we'll add it. > > Ara. > > > > ------------------------------------------------------- > 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 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek No, I will not fix your computer. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
