Xdoclet2 not loading Ant properties from propertyfile
|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
 |
Xdoclet2 not loading Ant properties from propertyfile
by Sakthivadivelu, Rajakumari
::
Rate this Message:
Hi, I am migrating from xdoclet1 to xdoclet2 I am using Ant to generate my files (EJB descriptors), as I couldn’t move to maven at this time My build.xml uses a property file to define properties which are used as attribute values in xdoclet tags
I find that there is already a discussion about this problem in this group
And I learnt that the user in the thread has fixed it locally by modifying xdoclet source
Thank you Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu - direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. |
|
|
|
|
|
RE: Xdoclet2 not loading Ant properties from propertyfile
by Sakthivadivelu, Rajakumari
::
Rate this Message:
Thanks for the reply
I would really like to do that But I am somehow lost, I got the xdoclet source from http://svn.codehaus.org/xdoclet/trunk/xdoclet/ From what I read around, I am hoping that this is the right place to get the latest sources, Please correct me if it is not However, I couldn't figure out how to compile them? Could you throw me some light on this Thanks again -----Original Message----- From: Konstantin Priblouda [mailto:kpriblouda@...] Sent: Thursday, May 14, 2009 2:54 PM To: user@... Subject: Re: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile An Attempt hasbeen made to integrate this, Judging from source code: ------------------%<------------- protected Generama createGenerama() { return new XDoclet(AntSourceProvider.class, FileWriterMapper.class) { public void composeContainer(MutablePicoContainer pico, Object scope) { super.composeContainer(pico, scope); pico.registerComponentInstance(filesets); pico.registerComponentInstance(getProject()); pico.registerComponentInstance(encoding); pico.registerComponentInstance(verbose); // turn em off, until we discover how to configure them properly // pico.registerComponentImplementation(PropertyComposer.class); // pico.registerComponentImplementation(SystemQDoxPropertyExpander.class); // pico.registerComponentInstance(new MyPropertiesQDoxPropertyExpander()); } }; } ---------------%<------------ But I'll have to investigate why it was disabled ( and it could take long as I have to do this in my not existing free time ) However, you may grab actual source base of xdoclet and cmpile snapshot version and report whether this works as intendet. regards, ----[ Konstantin Pribluda http://www.pribluda.de ]---------------- JTec quality components: http://www.pribluda.de/projects/ --- On Thu, 5/14/09, Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> wrote: > From: Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> > Subject: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile > To: user@... > Date: Thursday, May 14, 2009, 9:27 PM > > > > > > Xdoclet2 not loading Ant properties from > propertyfile > > > > > Hi, > > > I am migrating from xdoclet1 > to xdoclet2 > > > I am using Ant to generate > my files (EJB descriptors), as I couldn't move to > maven at this time > > > My build.xml uses a property > file to define properties which are used as attribute values > in xdoclet tags > > > But build fails as it does not > recognize the properties > > > I find that there is already > a discussion about this problem in this group > > > http://www.mail-archive.com/xdoclet-user@.../msg11296.html > > > I tried with both org.xdoclet.tools.PropertiesQDoxPropertyExpander , > > org.xdoclet.tools.SystemQDoxPropertyExpander > > > But it fails as said in the > thread > > > And I learnt that the user > in the thread has fixed it locally by modifying xdoclet > source > > > My question is , is there a > patch available already? > > > I am using xdoclet plugin1.0.4 > which uses xdoclet2.0.6 jar > > > Thank you > > > > > Notice: This e-mail message, together with any > attachments, contains > information of Merck & Co., Inc. (One Merck Drive, > Whitehouse Station, > New Jersey, USA 08889), and/or its affiliates (which may be > known > outside the United States as Merck Frosst, Merck Sharp > & Dohme or > MSD and in Japan, as Banyu - direct contact information for > affiliates is > available at http://www.merck.com/contact/contacts.html) > that may be > confidential, proprietary copyrighted and/or legally > privileged. It is > intended solely for the use of the individual or entity > named on this > message. If you are not the intended recipient, and have > received this > message in error, please notify us immediately by reply > e-mail and > then delete it from your system. > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu - direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
|
|
|
Re: Xdoclet2 not loading Ant properties from propertyfile
by Diogo Quintela (EF)
::
Rate this Message:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Hello List, As i recall, after my patch at the time, i realized i needed to register only a composer that would aggregate SystemQDoxPropertyExpander and PropertiesQDoxPropertyExpander, in dispite the registration of two implementations - that would give problems in ant task only. I was trying to look to my reported issue list to see if at the time i provided a patch for it - didn't find. Something like this: class MyAgregator implements PropertyComposer { PropertyComposer[] delegates; MyAgregator(PropertyComposer[] deletages) { ... } public String resolve(...) { // dont rememeber method names.. for ( PropertyComposer d : delegates) { String retVal = delegates.resolve(..); if (retVal != null) return retVal; } return null; } } and then something like this: pico.registerComponentInstance( new MyAgregator( new PropertyComposer[]{ new SystemQDoxPropertyExpander(), new PropertiesQDoxPropertyExpander() } ) ); Regards Diogo Konstantin Priblouda wrote: > An Attempt hasbeen made to integrate this, > Judging from source code: > ------------------%<------------- > protected Generama createGenerama() { > return new XDoclet(AntSourceProvider.class, FileWriterMapper.class) { > public void composeContainer(MutablePicoContainer pico, Object scope) { > super.composeContainer(pico, scope); > pico.registerComponentInstance(filesets); > pico.registerComponentInstance(getProject()); > pico.registerComponentInstance(encoding); > pico.registerComponentInstance(verbose); > // turn em off, until we discover how to configure them properly > // pico.registerComponentImplementation(PropertyComposer.class); > // pico.registerComponentImplementation(SystemQDoxPropertyExpander.class); > // pico.registerComponentInstance(new MyPropertiesQDoxPropertyExpander()); > } > }; > } > ---------------%<------------ > > But I'll have to investigate why it was disabled ( and it could take > long as I have to do this in my not existing free time ) > > However, you may grab actual source base of xdoclet and cmpile snapshot version and report whether this works as intendet. > > > regards, > > > ----[ Konstantin Pribluda http://www.pribluda.de ]---------------- > JTec quality components: http://www.pribluda.de/projects/ > > > --- On Thu, 5/14/09, Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> wrote: > >> From: Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> >> Subject: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile >> To: user@... >> Date: Thursday, May 14, 2009, 9:27 PM >> >> >> >> >> >> Xdoclet2 not loading Ant properties from >> propertyfile >> >> >> >> >> Hi, >> >> >> I am migrating from xdoclet1 >> to xdoclet2 >> >> >> I am using Ant to generate >> my files (EJB descriptors), as I couldn’t move to >> maven at this time >> >> >> My build.xml uses a property >> file to define properties which are used as attribute values >> in xdoclet tags >> >> >> But build fails as it does not >> recognize the properties >> >> >> I find that there is already >> a discussion about this problem in this group >> >> >> http://www.mail-archive.com/xdoclet-user@.../msg11296.html >> >> >> I tried with both org.xdoclet.tools.PropertiesQDoxPropertyExpander , >>> org.xdoclet.tools.SystemQDoxPropertyExpander >> >> But it fails as said in the >> thread >> >> >> And I learnt that the user >> in the thread has fixed it locally by modifying xdoclet >> source >> >> >> My question is , is there a >> patch available already? >> >> >> I am using xdoclet plugin1.0.4 >> which uses xdoclet2.0.6 jar >> >> >> Thank you >> >> >> >> >> Notice: This e-mail message, together with any >> attachments, contains >> information of Merck & Co., Inc. (One Merck Drive, >> Whitehouse Station, >> New Jersey, USA 08889), and/or its affiliates (which may be >> known >> outside the United States as Merck Frosst, Merck Sharp >> & Dohme or >> MSD and in Japan, as Banyu - direct contact information for >> affiliates is >> available at http://www.merck.com/contact/contacts.html) >> that may be >> confidential, proprietary copyrighted and/or legally >> privileged. It is >> intended solely for the use of the individual or entity >> named on this >> message. If you are not the intended recipient, and have >> received this >> message in error, please notify us immediately by reply >> e-mail and >> then delete it from your system. >> >> > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > - -- Diogo Bacelar Quintela EF - Tecnologias de Software, S.A. Av. António Serpa, 26 - 4º Dto. 1050-027 Lisboa Tel: 217827800 Fax: 217827830 email: diogo.quintela@... AVISO LEGAL: A informação presente nesta mensagem, bem como em qualquer dos seus anexos é confidencial e destinada exclusivamente ao(s) destinatário(s) nomeado(s). Qualquer utilização desta informação que não esteja de acordo com o seu objectivo, qualquer disseminação ou divulgação, total ou parcial, é proibida excepto se formalmente aprovada. A Internet não garante a integridade desta mensagem, a qual poderá ter sido interceptada, corrompida, perdida, atrasada ou acrescida de vírus. Assim, a EF Tecnologias de Software S.A. não se responsabiliza pela mensagem se modificada. DISCLAIMER: The information in this e-mail and in any attachments is confidential and intended exclusively for the named addressee(s). Any use of this information not in accordance with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except if formally approved. The internet can not guarantee the integrity of this message, as it could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or have viruses added to it. EF Tecnologias de Software, S.A. will not therefore be liable for the message if modified. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkoNQZgACgkQE8WFy05W90Jw4wCdFw7MvBC3URoXeu/iyjmjlxeU 0sIAn03mamwuGfzUuXpxw4LsNPcZtkHK =mCOU -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
RE: Xdoclet2 not loading Ant properties from propertyfile
by Sakthivadivelu, Rajakumari
::
Rate this Message:
Hi,
Thanks for you both for the support I tried uncommenting these 3lines, created a new snapshot jar // turn em off, until we discover how to configure them properly pico.registerComponentImplementation(PropertyComposer.class); pico.registerComponentImplementation(SystemQDoxPropertyExpander.class); pico.registerComponentInstance(new MyPropertiesQDoxPropertyExpander()); But it failed with my Ant build with the following error : org.picocontainer.defaults.AmbiguousComponentResolutionException: Ambiguous interface org.xdoclet. QDoxPropertyExpander, resolves to multiple keys [class org.xdoclet.ant.XDocletTask$PropertyComposer, class org.xdoclet.tools.SystemQDoxPropertyExpander, class org.xdoclet.ant.XDocletTask$MyPropertiesQ DoxPropertyExpander] I also tried the code for MyAgregator class as posted here But it failed with same kind of message AmbiguousComponentResolutionException . Though I am not clear with what the MyAgregator class is doing, I just did some trial and error modifications , but anyway it didn't work for me I don't have much time to do further analysis on this, so I think I am just going to try the workaround as in this old post http://www.mail-archive.com/xdoclet-user@.../msg11296.html Thanks again -----Original Message----- From: Diogo Quintela [mailto:diogo.quintela@...] Sent: Friday, May 15, 2009 6:19 AM To: user@... Subject: Re: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List, As i recall, after my patch at the time, i realized i needed to register only a composer that would aggregate SystemQDoxPropertyExpander and PropertiesQDoxPropertyExpander, in dispite the registration of two implementations - that would give problems in ant task only. I was trying to look to my reported issue list to see if at the time i provided a patch for it - didn't find. Something like this: class MyAgregator implements PropertyComposer { PropertyComposer[] delegates; MyAgregator(PropertyComposer[] deletages) { ... } public String resolve(...) { // dont rememeber method names.. for ( PropertyComposer d : delegates) { String retVal = delegates.resolve(..); if (retVal != null) return retVal; } return null; } } and then something like this: pico.registerComponentInstance( new MyAgregator( new PropertyComposer[]{ new SystemQDoxPropertyExpander(), new PropertiesQDoxPropertyExpander() } ) ); Regards Diogo Konstantin Priblouda wrote: > An Attempt hasbeen made to integrate this, > Judging from source code: > ------------------%<------------- > protected Generama createGenerama() { > return new XDoclet(AntSourceProvider.class, FileWriterMapper.class) { > public void composeContainer(MutablePicoContainer pico, Object scope) { > super.composeContainer(pico, scope); > pico.registerComponentInstance(filesets); > pico.registerComponentInstance(getProject()); > pico.registerComponentInstance(encoding); > pico.registerComponentInstance(verbose); > // turn em off, until we discover how to configure them properly > // pico.registerComponentImplementation(PropertyComposer.class); > // pico.registerComponentImplementation(SystemQDoxPropertyExpander.class); > // pico.registerComponentInstance(new MyPropertiesQDoxPropertyExpander()); > } > }; > } > ---------------%<------------ > > But I'll have to investigate why it was disabled ( and it could take > long as I have to do this in my not existing free time ) > > However, you may grab actual source base of xdoclet and cmpile snapshot version and report whether this works as intendet. > > > regards, > > > ----[ Konstantin Pribluda http://www.pribluda.de ]---------------- > JTec quality components: http://www.pribluda.de/projects/ > > > --- On Thu, 5/14/09, Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> wrote: > >> From: Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> >> Subject: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile >> To: user@... >> Date: Thursday, May 14, 2009, 9:27 PM >> >> >> >> >> >> Xdoclet2 not loading Ant properties from >> propertyfile >> >> >> >> >> Hi, >> >> >> I am migrating from xdoclet1 >> to xdoclet2 >> >> >> I am using Ant to generate >> my files (EJB descriptors), as I couldn't move to >> maven at this time >> >> >> My build.xml uses a property >> file to define properties which are used as attribute values >> in xdoclet tags >> >> >> But build fails as it does not >> recognize the properties >> >> >> I find that there is already >> a discussion about this problem in this group >> >> >> http://www.mail-archive.com/xdoclet-user@.../msg11296.html >> >> >> I tried with both org.xdoclet.tools.PropertiesQDoxPropertyExpander , >>> org.xdoclet.tools.SystemQDoxPropertyExpander >> >> But it fails as said in the >> thread >> >> >> And I learnt that the user >> in the thread has fixed it locally by modifying xdoclet >> source >> >> >> My question is , is there a >> patch available already? >> >> >> I am using xdoclet plugin1.0.4 >> which uses xdoclet2.0.6 jar >> >> >> Thank you >> >> >> >> >> Notice: This e-mail message, together with any >> attachments, contains >> information of Merck & Co., Inc. (One Merck Drive, >> Whitehouse Station, >> New Jersey, USA 08889), and/or its affiliates (which may be >> known >> outside the United States as Merck Frosst, Merck Sharp >> & Dohme or >> MSD and in Japan, as Banyu - direct contact information for >> affiliates is >> available at http://www.merck.com/contact/contacts.html) >> that may be >> confidential, proprietary copyrighted and/or legally >> privileged. It is >> intended solely for the use of the individual or entity >> named on this >> message. If you are not the intended recipient, and have >> received this >> message in error, please notify us immediately by reply >> e-mail and >> then delete it from your system. >> >> > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > - -- Diogo Bacelar Quintela EF - Tecnologias de Software, S.A. Av. António Serpa, 26 - 4º Dto. 1050-027 Lisboa Tel: 217827800 Fax: 217827830 email: diogo.quintela@... AVISO LEGAL: A informação presente nesta mensagem, bem como em qualquer dos seus anexos é confidencial e destinada exclusivamente ao(s) destinatário(s) nomeado(s). Qualquer utilização desta informação que não esteja de acordo com o seu objectivo, qualquer disseminação ou divulgação, total ou parcial, é proibida excepto se formalmente aprovada. A Internet não garante a integridade desta mensagem, a qual poderá ter sido interceptada, corrompida, perdida, atrasada ou acrescida de vírus. Assim, a EF Tecnologias de Software S.A. não se responsabiliza pela mensagem se modificada. DISCLAIMER: The information in this e-mail and in any attachments is confidential and intended exclusively for the named addressee(s). Any use of this information not in accordance with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except if formally approved. The internet can not guarantee the integrity of this message, as it could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or have viruses added to it. EF Tecnologias de Software, S.A. will not therefore be liable for the message if modified. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkoNQZgACgkQE8WFy05W90Jw4wCdFw7MvBC3URoXeu/iyjmjlxeU 0sIAn03mamwuGfzUuXpxw4LsNPcZtkHK =mCOU -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu - direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
RE: Xdoclet2 not loading Ant properties from propertyfile
by Sakthivadivelu, Rajakumari
::
Rate this Message:
Hi,
I am facing a different error now I get this error even if I don't modify the sources from trunk I just created a snapshot jar from the sources from trunk and Used it to run my ant build I get the following error. If I use the released jar xdoclet 2-0-6.jar,the same build file doesn't throw this error Though it fails because it doesn't recognize the ant properties Any thoughts on this? Thanks generate: [xdoclet] log4j:WARN No appenders could be found for logger (org.xdoclet.plugin.ejb.interfaces.Rem oteInterfacePlugin). [xdoclet] log4j:WARN Please initialize the log4j system properly. [xdoclet] Running org.xdoclet.plugin.ejb.EjbConfig BUILD FAILED java.lang.AbstractMethodError: createDocletTag at org.xdoclet.ModelCheckerTagFactory.createDocletTag(Ljava.lang.String;Ljava.lang.String;Lc om.thoughtworks.qdox.model.AbstractJavaEntity;I)Lcom.thoughtworks.qdox.model.DocletTag;(ModelChecker TagFactory.java:???) at com.thoughtworks.qdox.model.ModelBuilder.addJavaDoc(Lcom.thoughtworks.qdox.model.Abstract JavaEntity;)V(ModelBuilder.java:127) at com.thoughtworks.qdox.model.ModelBuilder.beginClass(Lcom.thoughtworks.qdox.parser.structs .ClassDef;)V(ModelBuilder.java:92) at com.thoughtworks.qdox.parser.impl.Parser.yyparse()I(Parser.java:927) at com.thoughtworks.qdox.parser.impl.Parser.parse()Z(Parser.java:592) at com.thoughtworks.qdox.JavaDocBuilder.addSource(Ljava.io.Reader;Ljava.lang.String;)Lcom.th oughtworks.qdox.model.JavaSource;(JavaDocBuilder.java:300) at com.thoughtworks.qdox.JavaDocBuilder.addSource(Ljava.net.URL;)Lcom.thoughtworks.qdox.mode l.JavaSource;(JavaDocBuilder.java:316) at org.xdoclet.QDoxMetadataProvider.addSourcesFromJavaSourceProvider(Lcom.thoughtworks.qdox. JavaDocBuilder;)V(QDoxMetadataProvider.java:129) at org.xdoclet.QDoxMetadataProvider.getMetadata()Ljava.util.Collection;(QDoxMetadataProvider .java:152) at org.xdoclet.plugin.ejb.util.QDoxFilterMetadataProvider.getMetadata()Ljava.util.Collection ;(QDoxFilterMetadataProvider.java:29) at org.xdoclet.plugin.ejb.util.QDoxCachedMetadataProvider.getMetadata()Ljava.util.Collection ;(QDoxCachedMetadataProvider.java:25) at org.generama.defaults.QDoxPlugin.getMetadata()Ljava.util.Collection;(QDoxPlugin.java:56) at org.generama.Plugin.start()V(Plugin.java:238) at org.picocontainer.defaults.DefaultPicoContainer.start()V(DefaultPicoContainer.java:349) at org.nanocontainer.integrationkit.LifecycleContainerBuilder.autoStart(Lorg.picocontainer.P icoContainer;)V(LifecycleContainerBuilder.java:52) at org.nanocontainer.integrationkit.LifecycleContainerBuilder.buildContainer(Lorg.picocontai ner.defaults.ObjectReference;Lorg.picocontainer.defaults.ObjectReference;Ljava.lang.Object;Z)V(Lifec ycleContainerBuilder.java:45) at org.nanocontainer.ant.PicoContainerTask.execute()V(PicoContainerTask.java:95) at org.apache.tools.ant.UnknownElement.execute()V(UnknownElement.java:193) at org.apache.tools.ant.Task.perform()V(Task.java:341) at org.apache.tools.ant.Target.execute()V(Target.java:309) at org.apache.tools.ant.Target.performTasks()V(Target.java:336) at org.apache.tools.ant.Project.executeTarget(Ljava.lang.String;)V(Project.java:1339) at org.apache.tools.ant.Project.executeTargets(Ljava.util.Vector;)V(Project.java:1255) at org.apache.tools.ant.Main.runBuild(Ljava.lang.ClassLoader;)V(Main.java:609) at org.apache.tools.ant.Main.start([Ljava.lang.String;Ljava.util.Properties;Ljava.lang.Class Loader;)V(Main.java:196) at org.apache.tools.ant.Main.main([Ljava.lang.String;)V(Main.java:235) Total time: 3 seconds java.lang.AbstractMethodError: createDocletTag at org.xdoclet.ModelCheckerTagFactory.createDocletTag(Ljava.lang.String;Ljava.lang.String;Lc om.thoughtworks.qdox.model.AbstractJavaEntity;I)Lcom.thoughtworks.qdox.model.DocletTag;(ModelChecker TagFactory.java:???) at com.thoughtworks.qdox.model.ModelBuilder.addJavaDoc(Lcom.thoughtworks.qdox.model.Abstract JavaEntity;)V(ModelBuilder.java:127) at com.thoughtworks.qdox.model.ModelBuilder.beginClass(Lcom.thoughtworks.qdox.parser.structs .ClassDef;)V(ModelBuilder.java:92) at com.thoughtworks.qdox.parser.impl.Parser.yyparse()I(Parser.java:927) at com.thoughtworks.qdox.parser.impl.Parser.parse()Z(Parser.java:592) at com.thoughtworks.qdox.JavaDocBuilder.addSource(Ljava.io.Reader;Ljava.lang.String;)Lcom.th oughtworks.qdox.model.JavaSource;(JavaDocBuilder.java:300) at com.thoughtworks.qdox.JavaDocBuilder.addSource(Ljava.net.URL;)Lcom.thoughtworks.qdox.mode l.JavaSource;(JavaDocBuilder.java:316) at org.xdoclet.QDoxMetadataProvider.addSourcesFromJavaSourceProvider(Lcom.thoughtworks.qdox. JavaDocBuilder;)V(QDoxMetadataProvider.java:129) at org.xdoclet.QDoxMetadataProvider.getMetadata()Ljava.util.Collection;(QDoxMetadataProvider .java:152) at org.xdoclet.plugin.ejb.util.QDoxFilterMetadataProvider.getMetadata()Ljava.util.Collection ;(QDoxFilterMetadataProvider.java:29) at org.xdoclet.plugin.ejb.util.QDoxCachedMetadataProvider.getMetadata()Ljava.util.Collection ;(QDoxCachedMetadataProvider.java:25) at org.generama.defaults.QDoxPlugin.getMetadata()Ljava.util.Collection;(QDoxPlugin.java:56) at org.generama.Plugin.start()V(Plugin.java:238) at org.picocontainer.defaults.DefaultPicoContainer.start()V(DefaultPicoContainer.java:349) at org.nanocontainer.integrationkit.LifecycleContainerBuilder.autoStart(Lorg.picocontainer.P icoContainer;)V(LifecycleContainerBuilder.java:52) at org.nanocontainer.integrationkit.LifecycleContainerBuilder.buildContainer(Lorg.picocontai ner.defaults.ObjectReference;Lorg.picocontainer.defaults.ObjectReference;Ljava.lang.Object;Z)V(Lifec ycleContainerBuilder.java:45) at org.nanocontainer.ant.PicoContainerTask.execute()V(PicoContainerTask.java:95) at org.apache.tools.ant.UnknownElement.execute()V(UnknownElement.java:193) at org.apache.tools.ant.Task.perform()V(Task.java:341) at org.apache.tools.ant.Target.execute()V(Target.java:309) at org.apache.tools.ant.Target.performTasks()V(Target.java:336) at org.apache.tools.ant.Project.executeTarget(Ljava.lang.String;)V(Project.java:1339) at org.apache.tools.ant.Project.executeTargets(Ljava.util.Vector;)V(Project.java:1255) at org.apache.tools.ant.Main.runBuild(Ljava.lang.ClassLoader;)V(Main.java:609) at org.apache.tools.ant.Main.start([Ljava.lang.String;Ljava.util.Properties;Ljava.lang.Class Loader;)V(Main.java:196) at org.apache.tools.ant.Main.main([Ljava.lang.String;)V(Main.java:235) createDocletTag -----Original Message----- From: Sakthivadivelu, Rajakumari Sent: Friday, May 15, 2009 1:59 PM To: user@... Subject: RE: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile Hi, Thanks for you both for the support I tried uncommenting these 3lines, created a new snapshot jar // turn em off, until we discover how to configure them properly pico.registerComponentImplementation(PropertyComposer.class); pico.registerComponentImplementation(SystemQDoxPropertyExpander.class); pico.registerComponentInstance(new MyPropertiesQDoxPropertyExpander()); But it failed with my Ant build with the following error : org.picocontainer.defaults.AmbiguousComponentResolutionException: Ambiguous interface org.xdoclet. QDoxPropertyExpander, resolves to multiple keys [class org.xdoclet.ant.XDocletTask$PropertyComposer, class org.xdoclet.tools.SystemQDoxPropertyExpander, class org.xdoclet.ant.XDocletTask$MyPropertiesQ DoxPropertyExpander] I also tried the code for MyAgregator class as posted here But it failed with same kind of message AmbiguousComponentResolutionException . Though I am not clear with what the MyAgregator class is doing, I just did some trial and error modifications , but anyway it didn't work for me I don't have much time to do further analysis on this, so I think I am just going to try the workaround as in this old post http://www.mail-archive.com/xdoclet-user@.../msg11296.html Thanks again -----Original Message----- From: Diogo Quintela [mailto:diogo.quintela@...] Sent: Friday, May 15, 2009 6:19 AM To: user@... Subject: Re: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List, As i recall, after my patch at the time, i realized i needed to register only a composer that would aggregate SystemQDoxPropertyExpander and PropertiesQDoxPropertyExpander, in dispite the registration of two implementations - that would give problems in ant task only. I was trying to look to my reported issue list to see if at the time i provided a patch for it - didn't find. Something like this: class MyAgregator implements PropertyComposer { PropertyComposer[] delegates; MyAgregator(PropertyComposer[] deletages) { ... } public String resolve(...) { // dont rememeber method names.. for ( PropertyComposer d : delegates) { String retVal = delegates.resolve(..); if (retVal != null) return retVal; } return null; } } and then something like this: pico.registerComponentInstance( new MyAgregator( new PropertyComposer[]{ new SystemQDoxPropertyExpander(), new PropertiesQDoxPropertyExpander() } ) ); Regards Diogo Konstantin Priblouda wrote: > An Attempt hasbeen made to integrate this, > Judging from source code: > ------------------%<------------- > protected Generama createGenerama() { > return new XDoclet(AntSourceProvider.class, FileWriterMapper.class) { > public void composeContainer(MutablePicoContainer pico, Object scope) { > super.composeContainer(pico, scope); > pico.registerComponentInstance(filesets); > pico.registerComponentInstance(getProject()); > pico.registerComponentInstance(encoding); > pico.registerComponentInstance(verbose); > // turn em off, until we discover how to configure them properly > // pico.registerComponentImplementation(PropertyComposer.class); > // pico.registerComponentImplementation(SystemQDoxPropertyExpander.class); > // pico.registerComponentInstance(new MyPropertiesQDoxPropertyExpander()); > } > }; > } > ---------------%<------------ > > But I'll have to investigate why it was disabled ( and it could take > long as I have to do this in my not existing free time ) > > However, you may grab actual source base of xdoclet and cmpile snapshot version and report whether this works as intendet. > > > regards, > > > ----[ Konstantin Pribluda http://www.pribluda.de ]---------------- > JTec quality components: http://www.pribluda.de/projects/ > > > --- On Thu, 5/14/09, Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> wrote: > >> From: Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> >> Subject: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile >> To: user@... >> Date: Thursday, May 14, 2009, 9:27 PM >> >> >> >> >> >> Xdoclet2 not loading Ant properties from >> propertyfile >> >> >> >> >> Hi, >> >> >> I am migrating from xdoclet1 >> to xdoclet2 >> >> >> I am using Ant to generate >> my files (EJB descriptors), as I couldn't move to >> maven at this time >> >> >> My build.xml uses a property >> file to define properties which are used as attribute values >> in xdoclet tags >> >> >> But build fails as it does not >> recognize the properties >> >> >> I find that there is already >> a discussion about this problem in this group >> >> >> http://www.mail-archive.com/xdoclet-user@.../msg11296.html >> >> >> I tried with both org.xdoclet.tools.PropertiesQDoxPropertyExpander , >>> org.xdoclet.tools.SystemQDoxPropertyExpander >> >> But it fails as said in the >> thread >> >> >> And I learnt that the user >> in the thread has fixed it locally by modifying xdoclet >> source >> >> >> My question is , is there a >> patch available already? >> >> >> I am using xdoclet plugin1.0.4 >> which uses xdoclet2.0.6 jar >> >> >> Thank you >> >> >> >> >> Notice: This e-mail message, together with any >> attachments, contains >> information of Merck & Co., Inc. (One Merck Drive, >> Whitehouse Station, >> New Jersey, USA 08889), and/or its affiliates (which may be >> known >> outside the United States as Merck Frosst, Merck Sharp >> & Dohme or >> MSD and in Japan, as Banyu - direct contact information for >> affiliates is >> available at http://www.merck.com/contact/contacts.html) >> that may be >> confidential, proprietary copyrighted and/or legally >> privileged. It is >> intended solely for the use of the individual or entity >> named on this >> message. If you are not the intended recipient, and have >> received this >> message in error, please notify us immediately by reply >> e-mail and >> then delete it from your system. >> >> > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > - -- Diogo Bacelar Quintela EF - Tecnologias de Software, S.A. Av. António Serpa, 26 - 4º Dto. 1050-027 Lisboa Tel: 217827800 Fax: 217827830 email: diogo.quintela@... AVISO LEGAL: A informação presente nesta mensagem, bem como em qualquer dos seus anexos é confidencial e destinada exclusivamente ao(s) destinatário(s) nomeado(s). Qualquer utilização desta informação que não esteja de acordo com o seu objectivo, qualquer disseminação ou divulgação, total ou parcial, é proibida excepto se formalmente aprovada. A Internet não garante a integridade desta mensagem, a qual poderá ter sido interceptada, corrompida, perdida, atrasada ou acrescida de vírus. Assim, a EF Tecnologias de Software S.A. não se responsabiliza pela mensagem se modificada. DISCLAIMER: The information in this e-mail and in any attachments is confidential and intended exclusively for the named addressee(s). Any use of this information not in accordance with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except if formally approved. The internet can not guarantee the integrity of this message, as it could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or have viruses added to it. EF Tecnologias de Software, S.A. will not therefore be liable for the message if modified. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkoNQZgACgkQE8WFy05W90Jw4wCdFw7MvBC3URoXeu/iyjmjlxeU 0sIAn03mamwuGfzUuXpxw4LsNPcZtkHK =mCOU -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu - direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu - direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
|
|
|
RE: Xdoclet2 not loading Ant properties from propertyfile
by Sakthivadivelu, Rajakumari
::
Rate this Message:
Just thought to update the thread, I couldn't continue further to try the changes suggested here due to time constraints :-(
We are going to just stay with xdoclet1.2.3 right now, as xdoc2 doesn't have many weblogic tags and Jboss plugin that we are in need and we couldn't invest time on that area, Thanks for all the support provided in the forum. -----Original Message----- From: Konstantin Priblouda [mailto:kpriblouda@...] Sent: Saturday, May 16, 2009 2:22 PM To: user@... Subject: RE: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile As you are building snapshot, it also uses snapshot dependencies. I would also recompile generama and eventually qdox. ( I'm redeploying snapshots right now on codehaus ) regards, ----[ Konstantin Pribluda http://www.pribluda.de ]---------------- JTec quality components: http://www.pribluda.de/projects/ --- On Fri, 5/15/09, Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> wrote: > From: Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> > Subject: RE: [xdoclet-user] Xdoclet2 not loading Ant properties from propertyfile > To: user@... > Date: Friday, May 15, 2009, 9:57 PM > Hi, > > I am facing a different error now > I get this error even if I don't modify the sources from > trunk > I just created a snapshot jar from the sources from trunk > and > Used it to run my ant build > > I get the following error. If I use the released jar > xdoclet 2-0-6.jar,the same build file doesn't throw this > error > Though it fails because it doesn't recognize the ant > properties > > Any thoughts on this? Thanks > generate: > [xdoclet] log4j:WARN No appenders could be found for > logger (org.xdoclet.plugin.ejb.interfaces.Rem > oteInterfacePlugin). > [xdoclet] log4j:WARN Please initialize the log4j > system properly. > [xdoclet] Running org.xdoclet.plugin.ejb.EjbConfig > > BUILD FAILED > java.lang.AbstractMethodError: createDocletTag > at > org.xdoclet.ModelCheckerTagFactory.createDocletTag(Ljava.lang.String;Ljava.lang.String;Lc > om.thoughtworks.qdox.model.AbstractJavaEntity;I)Lcom.thoughtworks.qdox.model.DocletTag;(ModelChecker > TagFactory.java:???) > at > com.thoughtworks.qdox.model.ModelBuilder.addJavaDoc(Lcom.thoughtworks.qdox.model.Abstract > JavaEntity;)V(ModelBuilder.java:127) > at > com.thoughtworks.qdox.model.ModelBuilder.beginClass(Lcom.thoughtworks.qdox.parser.structs > .ClassDef;)V(ModelBuilder.java:92) > at > com.thoughtworks.qdox.parser.impl.Parser.yyparse()I(Parser.java:927) > at > com.thoughtworks.qdox.parser.impl.Parser.parse()Z(Parser.java:592) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(Ljava.io.Reader;Ljava.lang.String;)Lcom.th > oughtworks.qdox.model.JavaSource;(JavaDocBuilder.java:300) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(Ljava.net.URL;)Lcom.thoughtworks.qdox.mode > l.JavaSource;(JavaDocBuilder.java:316) > at > org.xdoclet.QDoxMetadataProvider.addSourcesFromJavaSourceProvider(Lcom.thoughtworks.qdox. > JavaDocBuilder;)V(QDoxMetadataProvider.java:129) > at > org.xdoclet.QDoxMetadataProvider.getMetadata()Ljava.util.Collection;(QDoxMetadataProvider > .java:152) > at > org.xdoclet.plugin.ejb.util.QDoxFilterMetadataProvider.getMetadata()Ljava.util.Collection > ;(QDoxFilterMetadataProvider.java:29) > at > org.xdoclet.plugin.ejb.util.QDoxCachedMetadataProvider.getMetadata()Ljava.util.Collection > ;(QDoxCachedMetadataProvider.java:25) > at > org.generama.defaults.QDoxPlugin.getMetadata()Ljava.util.Collection;(QDoxPlugin.java:56) > at > org.generama.Plugin.start()V(Plugin.java:238) > at > org.picocontainer.defaults.DefaultPicoContainer.start()V(DefaultPicoContainer.java:349) > at > org.nanocontainer.integrationkit.LifecycleContainerBuilder.autoStart(Lorg.picocontainer.P > icoContainer;)V(LifecycleContainerBuilder.java:52) > at > org.nanocontainer.integrationkit.LifecycleContainerBuilder.buildContainer(Lorg.picocontai > ner.defaults.ObjectReference;Lorg.picocontainer.defaults.ObjectReference;Ljava.lang.Object;Z)V(Lifec > ycleContainerBuilder.java:45) > at > org.nanocontainer.ant.PicoContainerTask.execute()V(PicoContainerTask.java:95) > at > org.apache.tools.ant.UnknownElement.execute()V(UnknownElement.java:193) > at > org.apache.tools.ant.Task.perform()V(Task.java:341) > at > org.apache.tools.ant.Target.execute()V(Target.java:309) > at > org.apache.tools.ant.Target.performTasks()V(Target.java:336) > at > org.apache.tools.ant.Project.executeTarget(Ljava.lang.String;)V(Project.java:1339) > at > org.apache.tools.ant.Project.executeTargets(Ljava.util.Vector;)V(Project.java:1255) > at > org.apache.tools.ant.Main.runBuild(Ljava.lang.ClassLoader;)V(Main.java:609) > at > org.apache.tools.ant.Main.start([Ljava.lang.String;Ljava.util.Properties;Ljava.lang.Class > Loader;)V(Main.java:196) > at > org.apache.tools.ant.Main.main([Ljava.lang.String;)V(Main.java:235) > > Total time: 3 seconds > java.lang.AbstractMethodError: createDocletTag > at > org.xdoclet.ModelCheckerTagFactory.createDocletTag(Ljava.lang.String;Ljava.lang.String;Lc > om.thoughtworks.qdox.model.AbstractJavaEntity;I)Lcom.thoughtworks.qdox.model.DocletTag;(ModelChecker > TagFactory.java:???) > at > com.thoughtworks.qdox.model.ModelBuilder.addJavaDoc(Lcom.thoughtworks.qdox.model.Abstract > JavaEntity;)V(ModelBuilder.java:127) > at > com.thoughtworks.qdox.model.ModelBuilder.beginClass(Lcom.thoughtworks.qdox.parser.structs > .ClassDef;)V(ModelBuilder.java:92) > at > com.thoughtworks.qdox.parser.impl.Parser.yyparse()I(Parser.java:927) > at > com.thoughtworks.qdox.parser.impl.Parser.parse()Z(Parser.java:592) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(Ljava.io.Reader;Ljava.lang.String;)Lcom.th > oughtworks.qdox.model.JavaSource;(JavaDocBuilder.java:300) > at > com.thoughtworks.qdox.JavaDocBuilder.addSource(Ljava.net.URL;)Lcom.thoughtworks.qdox.mode > l.JavaSource;(JavaDocBuilder.java:316) > at > org.xdoclet.QDoxMetadataProvider.addSourcesFromJavaSourceProvider(Lcom.thoughtworks.qdox. > JavaDocBuilder;)V(QDoxMetadataProvider.java:129) > at > org.xdoclet.QDoxMetadataProvider.getMetadata()Ljava.util.Collection;(QDoxMetadataProvider > .java:152) > at > org.xdoclet.plugin.ejb.util.QDoxFilterMetadataProvider.getMetadata()Ljava.util.Collection > ;(QDoxFilterMetadataProvider.java:29) > at > org.xdoclet.plugin.ejb.util.QDoxCachedMetadataProvider.getMetadata()Ljava.util.Collection > ;(QDoxCachedMetadataProvider.java:25) > at > org.generama.defaults.QDoxPlugin.getMetadata()Ljava.util.Collection;(QDoxPlugin.java:56) > at > org.generama.Plugin.start()V(Plugin.java:238) > at > org.picocontainer.defaults.DefaultPicoContainer.start()V(DefaultPicoContainer.java:349) > at > org.nanocontainer.integrationkit.LifecycleContainerBuilder.autoStart(Lorg.picocontainer.P > icoContainer;)V(LifecycleContainerBuilder.java:52) > at > org.nanocontainer.integrationkit.LifecycleContainerBuilder.buildContainer(Lorg.picocontai > ner.defaults.ObjectReference;Lorg.picocontainer.defaults.ObjectReference;Ljava.lang.Object;Z)V(Lifec > ycleContainerBuilder.java:45) > at > org.nanocontainer.ant.PicoContainerTask.execute()V(PicoContainerTask.java:95) > at > org.apache.tools.ant.UnknownElement.execute()V(UnknownElement.java:193) > at > org.apache.tools.ant.Task.perform()V(Task.java:341) > at > org.apache.tools.ant.Target.execute()V(Target.java:309) > at > org.apache.tools.ant.Target.performTasks()V(Target.java:336) > at > org.apache.tools.ant.Project.executeTarget(Ljava.lang.String;)V(Project.java:1339) > at > org.apache.tools.ant.Project.executeTargets(Ljava.util.Vector;)V(Project.java:1255) > at > org.apache.tools.ant.Main.runBuild(Ljava.lang.ClassLoader;)V(Main.java:609) > at > org.apache.tools.ant.Main.start([Ljava.lang.String;Ljava.util.Properties;Ljava.lang.Class > Loader;)V(Main.java:196) > at > org.apache.tools.ant.Main.main([Ljava.lang.String;)V(Main.java:235) > createDocletTag > > -----Original Message----- > From: Sakthivadivelu, Rajakumari > Sent: Friday, May 15, 2009 1:59 PM > To: user@... > Subject: RE: [xdoclet-user] Xdoclet2 not loading Ant > properties from propertyfile > > Hi, > Thanks for you both for the support > I tried uncommenting these 3lines, created a new snapshot > jar > > // turn em off, until we discover how to > configure them properly > > > pico.registerComponentImplementation(PropertyComposer.class); > > > pico.registerComponentImplementation(SystemQDoxPropertyExpander.class); > > pico.registerComponentInstance(new > MyPropertiesQDoxPropertyExpander()); > > But it failed with my Ant build with the following error > : > org.picocontainer.defaults.AmbiguousComponentResolutionException: > Ambiguous interface org.xdoclet. > QDoxPropertyExpander, resolves to multiple keys [class > org.xdoclet.ant.XDocletTask$PropertyComposer, > class org.xdoclet.tools.SystemQDoxPropertyExpander, class > org.xdoclet.ant.XDocletTask$MyPropertiesQ > DoxPropertyExpander] > > I also tried the code for MyAgregator class as posted > here > But it failed with same kind of message > AmbiguousComponentResolutionException . Though I am not > clear with what the > MyAgregator class is doing, I just did some trial and error > modifications , but anyway it didn't work for me > I don't have much time to do further analysis on > this, so I think I am just going to try the workaround as in > this old post > http://www.mail-archive.com/xdoclet-user@.../msg11296.html > > Thanks again > -----Original Message----- > From: Diogo Quintela [mailto:diogo.quintela@...] > > Sent: Friday, May 15, 2009 6:19 AM > To: user@... > Subject: Re: [xdoclet-user] Xdoclet2 not loading Ant > properties from propertyfile > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello List, > > As i recall, after my patch at the time, i realized i > needed to register > only a composer that would aggregate > SystemQDoxPropertyExpander and > PropertiesQDoxPropertyExpander, in dispite the registration > of two > implementations - that would give problems in ant task > only. > > I was trying to look to my reported issue list to see if at > the time i > provided a patch for it - didn't find. > > Something like this: > > class MyAgregator implements PropertyComposer { > PropertyComposer[] delegates; > MyAgregator(PropertyComposer[] > deletages) { > ... > } > public String resolve(...) { // dont > rememeber method names.. > for ( > PropertyComposer d : delegates) { > String retVal = > delegates.resolve(..); > if > (retVal != null) return retVal; > } > return null; > } > } > > and then something like this: > pico.registerComponentInstance( > new MyAgregator( > new PropertyComposer[]{ > new SystemQDoxPropertyExpander(), > new PropertiesQDoxPropertyExpander() > } > ) > ); > > Regards > Diogo > > Konstantin Priblouda wrote: > > An Attempt hasbeen made to integrate this, > > Judging from source code: > > ------------------%<------------- > > protected Generama createGenerama() > { > > return new > XDoclet(AntSourceProvider.class, FileWriterMapper.class) { > > > public void > composeContainer(MutablePicoContainer pico, Object scope) { > > > > super.composeContainer(pico, scope); > > > > pico.registerComponentInstance(filesets); > > > > pico.registerComponentInstance(getProject()); > > > > pico.registerComponentInstance(encoding); > > > > pico.registerComponentInstance(verbose); > > > // turn em off, until > we discover how to configure them properly > > // > > pico.registerComponentImplementation(PropertyComposer.class); > > // > > pico.registerComponentImplementation(SystemQDoxPropertyExpander.class); > > // > > pico.registerComponentInstance(new > MyPropertiesQDoxPropertyExpander()); > > > } > > }; > > } > > ---------------%<------------ > > > > But I'll have to investigate why it was disabled > ( and it could take > > long as I have to do this in my not existing free time > ) > > > > However, you may grab actual source base of xdoclet > and cmpile snapshot version and report whether this > works as intendet. > > > > > > regards, > > > > > > ----[ Konstantin Pribluda http://www.pribluda.de ]---------------- > > JTec quality components: http://www.pribluda.de/projects/ > > > > > > --- On Thu, 5/14/09, Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> > wrote: > > > >> From: Sakthivadivelu, Rajakumari <rajakumari_sakthivadivelu@...> > >> Subject: [xdoclet-user] Xdoclet2 not loading Ant > properties from propertyfile > >> To: user@... > >> Date: Thursday, May 14, 2009, 9:27 PM > >> > >> > >> > >> > >> > >> Xdoclet2 not loading Ant properties from > >> propertyfile > >> > >> > >> > >> > >> Hi, > >> > >> > >> I am migrating from xdoclet1 > >> to xdoclet2 > >> > >> > >> I am using Ant to generate > >> my files (EJB descriptors), as I couldn't move to > >> maven at this time > >> > >> > >> My build.xml uses a property > >> file to define properties which are used as > attribute values > >> in xdoclet tags > >> > >> > >> But build fails as it does not > >> recognize the properties > >> > >> > >> I find that there is already > >> a discussion about this problem in this group > >> > >> > >> http://www.mail-archive.com/xdoclet-user@.../msg11296.html > >> > >> > >> I tried with both > org.xdoclet.tools.PropertiesQDoxPropertyExpander , > >>> org.xdoclet.tools.SystemQDoxPropertyExpander > >> > >> But it fails as said in the > >> thread > >> > >> > >> And I learnt that the user > >> in the thread has fixed it locally by modifying > xdoclet > >> source > >> > >> > >> My question is , is there a > >> patch available already? > >> > >> > >> I am using xdoclet plugin1.0.4 > >> which uses xdoclet2.0.6 jar > >> > >> > >> Thank you > >> > >> > >> > >> > >> Notice: This e-mail message, together with > any > >> attachments, contains > >> information of Merck & Co., Inc. (One Merck > Drive, > >> Whitehouse Station, > >> New Jersey, USA 08889), and/or its affiliates > (which may be > >> known > >> outside the United States as Merck Frosst, Merck > Sharp > >> & Dohme or > >> MSD and in Japan, as Banyu - direct contact > information for > >> affiliates is > >> available at http://www.merck.com/contact/contacts.html) > >> that may be > >> confidential, proprietary copyrighted and/or > legally > >> privileged. It is > >> intended solely for the use of the individual or > entity > >> named on this > >> message. If you are not the intended recipient, > and have > >> received this > >> message in error, please notify us immediately by > reply > >> e-mail and > >> then delete it from your system. > >> > >> > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > - -- > Diogo Bacelar Quintela > EF - Tecnologias de Software, S.A. > Av. António Serpa, 26 - 4º Dto. > 1050-027 Lisboa > Tel: 217827800 Fax: 217827830 > email: diogo.quintela@... > > AVISO LEGAL: A informação > presente nesta mensagem, bem como > em > qualquer dos seus anexos é confidencial > e destinada exclusivamente > ao(s) destinatário(s) nomeado(s). Qualquer utilização > desta informação > que não esteja de acordo com o seu objectivo, qualquer > disseminação ou > divulgação, total ou parcial, > é proibida excepto se formalmente > aprovada. A Internet não garante a integridade desta > mensagem, a qual > poderá ter sido interceptada, > corrompida, perdida, > atrasada ou > acrescida de vírus. Assim, a EF Tecnologias de > Software S.A. não se > responsabiliza pela mensagem se modificada. > > DISCLAIMER: The information in this e-mail and in any > attachments is > confidential and intended exclusively for the named > addressee(s). Any > use of this information not in > accordance with its purpose, any > dissemination or disclosure, either whole > or partial, is prohibited > except if formally approved. The > internet can not guarantee the > integrity of this message, as it > could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete or > have viruses added to > it. EF Tecnologias de Software, S.A. will not therefore be > liable for > the message if modified. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > > iEYEARECAAYFAkoNQZgACgkQE8WFy05W90Jw4wCdFw7MvBC3URoXeu/iyjmjlxeU > 0sIAn03mamwuGfzUuXpxw4LsNPcZtkHK > =mCOU > -----END PGP SIGNATURE----- > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > Notice: This e-mail message, together with any > attachments, contains > information of Merck & Co., Inc. (One Merck Drive, > Whitehouse Station, > New Jersey, USA 08889), and/or its affiliates (which may be > known > outside the United States as Merck Frosst, Merck Sharp > & Dohme or > MSD and in Japan, as Banyu - direct contact information for > affiliates is > available at http://www.merck.com/contact/contacts.html) that may > be > confidential, proprietary copyrighted and/or legally > privileged. It is > intended solely for the use of the individual or entity > named on this > message. If you are not the intended recipient, and have > received this > message in error, please notify us immediately by reply > e-mail and > then delete it from your system. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > Notice: This e-mail message, together with any > attachments, contains > information of Merck & Co., Inc. (One Merck Drive, > Whitehouse Station, > New Jersey, USA 08889), and/or its affiliates (which may be > known > outside the United States as Merck Frosst, Merck Sharp > & Dohme or > MSD and in Japan, as Banyu - direct contact information for > affiliates is > available at http://www.merck.com/contact/contacts.html) that may > be > confidential, proprietary copyrighted and/or legally > privileged. It is > intended solely for the use of the individual or entity > named on this > message. If you are not the intended recipient, and have > received this > message in error, please notify us immediately by reply > e-mail and > then delete it from your system. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu - direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |
