Re: hivemodule.xml and classpaths and jetty6 and maven 2 snapshots..
Thank you, hv! It's very, very appreciated. (Im sending myself that information in an email) Josh On 8/11/06, hv @ Fashion Content <[EMAIL PROTECTED]> wrote: This is how I inject spring into my engine service: "Josh Long" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] >I was usuing tapestry 4.1.1-snapshot gleefully and one day it (maven > and the snapshot with it) updated above and beyond > 4.1.1-20060802.044417-5 (the particular snapshot iteration after which > my build stop working around a week or two ago). I was receiving > strange errors about classpath conflicts, etc. > > I pinned my snapshot iteration down and just now took another whack at > resolving the issue. the errors were related to hivemodule.xml having > a conflict with the class path of the tapestry framework jars > hivemodule.xml. > > so, first question: where (if not webapp/WEB-INF/) does hivemodule.xml > properly go? Right now i have hivemodule.xml named oldhivemodule.xmla > nd everything works properly.. except all the things hivemodule.xml > was responsible for (engine services, freindly-urls, a custom > persistence mechanism...) > > And, while im on a hivemodule roll, would someone be kind enough to > show me how i would inject a spring bean accessible through spring:foo > into an engine service? Im not quite sure I get the > factory/create-instance/lightweight initialization etc routine, and > cant figure out for the live of me what i would need to get a tapestry > service wired with a spring bean... > > Thanks again! > > Peace, > Josh > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: hivemodule.xml and classpaths and jetty6 and maven 2 snapshots..
This is how I inject spring into my engine service: "Josh Long" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] >I was usuing tapestry 4.1.1-snapshot gleefully and one day it (maven > and the snapshot with it) updated above and beyond > 4.1.1-20060802.044417-5 (the particular snapshot iteration after which > my build stop working around a week or two ago). I was receiving > strange errors about classpath conflicts, etc. > > I pinned my snapshot iteration down and just now took another whack at > resolving the issue. the errors were related to hivemodule.xml having > a conflict with the class path of the tapestry framework jars > hivemodule.xml. > > so, first question: where (if not webapp/WEB-INF/) does hivemodule.xml > properly go? Right now i have hivemodule.xml named oldhivemodule.xmla > nd everything works properly.. except all the things hivemodule.xml > was responsible for (engine services, freindly-urls, a custom > persistence mechanism...) > > And, while im on a hivemodule roll, would someone be kind enough to > show me how i would inject a spring bean accessible through spring:foo > into an engine service? Im not quite sure I get the > factory/create-instance/lightweight initialization etc routine, and > cant figure out for the live of me what i would need to get a tapestry > service wired with a spring bean... > > Thanks again! > > Peace, > Josh > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: hivemodule.xml and classpaths and jetty6 and maven 2 snapshots..
I answered my own question. Amazing how that works sometimes... Apparently, this contribution which hitherto caused no problems was suddenly causing tapestry to wig out. remove it, and everything else is fine. Thanks for indulding me. Josh On 8/9/06, Josh Long <[EMAIL PROTECTED]> wrote: I was usuing tapestry 4.1.1-snapshot gleefully and one day it (maven and the snapshot with it) updated above and beyond 4.1.1-20060802.044417-5 (the particular snapshot iteration after which my build stop working around a week or two ago). I was receiving strange errors about classpath conflicts, etc. I pinned my snapshot iteration down and just now took another whack at resolving the issue. the errors were related to hivemodule.xml having a conflict with the class path of the tapestry framework jars hivemodule.xml. so, first question: where (if not webapp/WEB-INF/) does hivemodule.xml properly go? Right now i have hivemodule.xml named oldhivemodule.xmla nd everything works properly.. except all the things hivemodule.xml was responsible for (engine services, freindly-urls, a custom persistence mechanism...) And, while im on a hivemodule roll, would someone be kind enough to show me how i would inject a spring bean accessible through spring:foo into an engine service? Im not quite sure I get the factory/create-instance/lightweight initialization etc routine, and cant figure out for the live of me what i would need to get a tapestry service wired with a spring bean... Thanks again! Peace, Josh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
hivemodule.xml and classpaths and jetty6 and maven 2 snapshots..
I was usuing tapestry 4.1.1-snapshot gleefully and one day it (maven and the snapshot with it) updated above and beyond 4.1.1-20060802.044417-5 (the particular snapshot iteration after which my build stop working around a week or two ago). I was receiving strange errors about classpath conflicts, etc. I pinned my snapshot iteration down and just now took another whack at resolving the issue. the errors were related to hivemodule.xml having a conflict with the class path of the tapestry framework jars hivemodule.xml. so, first question: where (if not webapp/WEB-INF/) does hivemodule.xml properly go? Right now i have hivemodule.xml named oldhivemodule.xmla nd everything works properly.. except all the things hivemodule.xml was responsible for (engine services, freindly-urls, a custom persistence mechanism...) And, while im on a hivemodule roll, would someone be kind enough to show me how i would inject a spring bean accessible through spring:foo into an engine service? Im not quite sure I get the factory/create-instance/lightweight initialization etc routine, and cant figure out for the live of me what i would need to get a tapestry service wired with a spring bean... Thanks again! Peace, Josh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
