The beans in xwork are currently defined in code, in the classes mentioned before, not in xml files.
musachy On Fri, Aug 7, 2009 at 6:06 AM, Wes Wannemacher<[email protected]> wrote: > I don't know if it will help Lukasz, but I did some work in > xwork-showcase to get a base (non-struts) configuration up and > running. I think I mentioned before, the xml files in xwork-core > aren't enough to get xwork running standalone, no beans are defined. > You can check out the xwork-showcase, I think I added the exec-java > plugin so you can just do mvn exec:java to see it run an action. > > -Wes > > On Fri, Aug 7, 2009 at 2:02 AM, Lukasz > Lenart<[email protected]> wrote: >> Hi, >> >> I've been playing how to inject custom TextProvider in xwork I >> discovered small mistake. Instead of using xwork-default.xml in >> XmlConfigurationProvider, in all palces xwork.xml is used. Is it >> correct, means should xwork.xml (which doesn't exist) should be used? >> >> >> Regards >> -- >> Lukasz >> http://www.lenart.org.pl/ >> http://dailylog.lenart.org.pl/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > -- > Wes Wannemacher > > Head Engineer, WanTii, Inc. > Need Training? Struts, Spring, Maven, Tomcat... > Ask me for a quote! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- "Hey you! Would you help me to carry the stone?" Pink Floyd --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
