You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Lukasz Lenart <lu...@googlemail.com> on 2009/08/07 08:02:22 UTC
xwork-default.xml
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: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: xwork-default.xml
Posted by Lukasz Lenart <lu...@googlemail.com>.
Hi,
I've been thinking what to do with that file and the best option is
delete it when Xwork be merged into Struts 2
Regards
--
Lukasz
http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: xwork-default.xml
Posted by Arthur Neves <ar...@gmail.com>.
So,
do we have to open an issue in jira to solve this problem?
2009/8/20 Lukasz Lenart <lu...@googlemail.com>
> 2009/8/7 Musachy Barroso <mu...@gmail.com>:
> > The beans in xwork are currently defined in code, in the classes
> > mentioned before, not in xml files.
>
> Ok, but the problem is in
> ConfigurationManager.getContainerProviders(), there is reference to
> xwork.xml file which doesn't exist. Instead xwork-default.xml shoud be
> used.
>
> public List<ContainerProvider> getContainerProviders() {
> providerLock.lock();
> try {
> if (containerProviders.size() == 0) {
> containerProviders.add(new XWorkConfigurationProvider());
> containerProviders.add(new
> XmlConfigurationProvider("xwork.xml", false));
> }
>
> return containerProviders;
> } finally {
> providerLock.unlock();
> }
> }
>
>
> Regards
> --
> Lukasz
> http://www.lenart.org.pl/
> http://dailylog.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: xwork-default.xml
Posted by Lukasz Lenart <lu...@googlemail.com>.
2009/8/7 Musachy Barroso <mu...@gmail.com>:
> The beans in xwork are currently defined in code, in the classes
> mentioned before, not in xml files.
Ok, but the problem is in
ConfigurationManager.getContainerProviders(), there is reference to
xwork.xml file which doesn't exist. Instead xwork-default.xml shoud be
used.
public List<ContainerProvider> getContainerProviders() {
providerLock.lock();
try {
if (containerProviders.size() == 0) {
containerProviders.add(new XWorkConfigurationProvider());
containerProviders.add(new
XmlConfigurationProvider("xwork.xml", false));
}
return containerProviders;
} finally {
providerLock.unlock();
}
}
Regards
--
Lukasz
http://www.lenart.org.pl/
http://dailylog.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: xwork-default.xml
Posted by Musachy Barroso <mu...@gmail.com>.
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<we...@wantii.com> 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<lu...@googlemail.com> 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: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
>
> --
> Wes Wannemacher
>
> Head Engineer, WanTii, Inc.
> Need Training? Struts, Spring, Maven, Tomcat...
> Ask me for a quote!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: xwork-default.xml
Posted by Wes Wannemacher <we...@wantii.com>.
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<lu...@googlemail.com> 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: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Wes Wannemacher
Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org