RE: Upgrade 2.1.6 to 2.1.8.1

2010-03-10 Thread CRANFORD, CHRIS
Wednesday, March 10, 2010 10:55 AM > To: Struts Users Mailing List > Subject: Re: Upgrade 2.1.6 to 2.1.8.1 > > 2010/3/10 CRANFORD, CHRIS > > > > When upgrading Struts from 2.1.6 to 2.1.8.1; I found that for some > > reason my application isn't actually loading struts.

Re: Upgrade 2.1.6 to 2.1.8.1

2010-03-10 Thread Lukasz Lenart
2010/3/10 CRANFORD, CHRIS > > When upgrading Struts from 2.1.6 to 2.1.8.1; I found that for some > reason my application isn't actually loading struts.  Did anyone > experience this problem when they upgraded?  Is there something specific > I should check or be aware of? > > It is as if the framew

Upgrade 2.1.6 to 2.1.8.1

2010-03-10 Thread CRANFORD, CHRIS
When upgrading Struts from 2.1.6 to 2.1.8.1; I found that for some reason my application isn't actually loading struts. Did anyone experience this problem when they upgraded? Is there something specific I should check or be aware of? It is as if the framework just isn't being loaded via web.xml.

RE: Upgrade 2.1.6 to 2.1.8.1 - Action Results in 404

2010-01-15 Thread CRANFORD, CHRIS
ues because of this maybe? -Original Message- From: Wes Wannemacher [mailto:w...@wantii.com] Sent: Friday, January 15, 2010 12:13 PM To: Struts Users Mailing List Subject: Re: Upgrade 2.1.6 to 2.1.8.1 - Action Results in 404 You mention that you get a 404, a few questions... First, does

Re: Upgrade 2.1.6 to 2.1.8.1 - Action Results in 404

2010-01-15 Thread Wes Wannemacher
You mention that you get a 404, a few questions... First, does this 404 come from the struts filter or the application server? When I am working, I can usually tell the difference because 404s coming from the struts filter generally indicate "Action" or "Action Mapping" not found. In the even that

Upgrade 2.1.6 to 2.1.8.1 - Action Results in 404

2010-01-15 Thread CRANFORD, CHRIS
I was using Struts 2.1.6 along with XWork2 2.1.2. After finding a bug with XWork2, it was recommended that this package be upgraded. As a result, XWork2's later release depends on 2.1.8.1 of Struts2 and thus I had to upgrade all my jars. Now web application no longer works. When I navigate to

Re: Upgrade 2.1.6 to 2.1.8.1

2009-12-02 Thread Saeed Iqbal
If you are using maven do a dependency:tree and exclude redundant packages On Wednesday, December 2, 2009, Musachy Barroso wrote: > make sure you dont have 2 versions of xwork. > > musachy > > On Wed, Dec 2, 2009 at 8:50 AM, Saeed Iqbal wrote: >> This looks like a classpath issue >> >> On Wednes

Re: Upgrade 2.1.6 to 2.1.8.1

2009-12-02 Thread Musachy Barroso
make sure you dont have 2 versions of xwork. musachy On Wed, Dec 2, 2009 at 8:50 AM, Saeed Iqbal wrote: > This looks like a classpath issue > > On Wednesday, December 2, 2009, Gustavo Andrés Guevara Saavedra > wrote: >> Hi, >> >> I've just migrated my app. from Struts 2.1.6 to 2.1.8.1. The appl

Re: Upgrade 2.1.6 to 2.1.8.1

2009-12-02 Thread Saeed Iqbal
This looks like a classpath issue On Wednesday, December 2, 2009, Gustavo Andrés Guevara Saavedra wrote: > Hi, > > I've just migrated my app. from Struts 2.1.6 to 2.1.8.1. The application > worked fine but now throws the following exception upon launching the server: > > Unable to load configura

Upgrade 2.1.6 to 2.1.8.1

2009-12-02 Thread Gustavo Andrés Guevara Saavedra
Hi, I've just migrated my app. from Struts 2.1.6 to 2.1.8.1. The application worked fine but now throws the following exception upon launching the server: Unable to load configuration. - bean - jar:file:/C:/Yazix/workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/front_

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-02 Thread Saeed Iqbal
Yes thats right On Wednesday, December 2, 2009, Brian Thompson wrote: > Link > > -Brian > > On Wed, Dec 2, 2009 at 1:40 AM, Henry Jen wrote: > >> 2009/12/1 Saeed Iqbal : >> > It totally depends on your needs. >> > >> >> The only reason we would like to use is that we want to use OGNL >> in href

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-02 Thread Brian Thompson
Oops, that should have been this: ">Link Closing the tag is always a good idea. -Brian On Wed, Dec 2, 2009 at 9:11 AM, Brian Thompson wrote: > Link > > -Brian > > > On Wed, Dec 2, 2009 at 1:40 AM, Henry Jen wrote: > >> 2009/12/1 Saeed Iqbal : >> > It totally depends on your needs. >> > >> >

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-02 Thread Brian Thompson
Link -Brian On Wed, Dec 2, 2009 at 1:40 AM, Henry Jen wrote: > 2009/12/1 Saeed Iqbal : > > It totally depends on your needs. > > > > The only reason we would like to use is that we want to use OGNL > in href. For example, > > Link > > If we can use would be cleaner. Any suggestion? > > Cheers

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-01 Thread Saeed Iqbal
My suggestion, if you are not able to do this then maybe go with s:set and c:out the href. You would attain the same thing back. On Wed, Dec 2, 2009 at 1:25 PM, Henry Jen wrote: > 2009/12/1 Saeed Iqbal : > > It totally depends on your needs. > > > > The only reason we would like to use is that

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-01 Thread Henry Jen
2009/12/1 Saeed Iqbal : > It totally depends on your needs. > The only reason we would like to use is that we want to use OGNL in href. For example, Link If we can use would be cleaner. Any suggestion? Cheers, Henry > On Wed, Dec 2, 2009 at 1:14 PM, Henry Jen wrote: > >> 2009/12/1 Henry Jen

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-01 Thread Saeed Iqbal
It totally depends on your needs. On Wed, Dec 2, 2009 at 1:14 PM, Henry Jen wrote: > 2009/12/1 Henry Jen : > > Thanks for the prompt reply, but document in 2.1.6 and 2.1.8 doesn't > > say that, though It does say it works with simple theme but works best > > for ajax. > > > > 2.1.6 works, so I a

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-01 Thread Henry Jen
2009/12/1 Henry Jen : > Thanks for the prompt reply, but document in 2.1.6 and 2.1.8 doesn't > say that, though It does say it works with simple theme but works best > for ajax. > > 2.1.6 works, so I am wondering if there is a quick way to make it work > for 2.1.8. > Maybe the right approach is si

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-01 Thread Henry Jen
Thanks for the prompt reply, but document in 2.1.6 and 2.1.8 doesn't say that, though It does say it works with simple theme but works best for ajax. 2.1.6 works, so I am wondering if there is a quick way to make it work for 2.1.8. Cheers, Henry 2009/12/1 Saeed Iqbal : > http://struts.apache.org

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-01 Thread Saeed Iqbal
http://struts.apache.org/2.0.8/docs/a.html says *THE FOLLOWING IS ONLY VALID WHEN AJAX IS CONFIGURED* On Wed, Dec 2, 2009 at 12:57 PM, Henry Jen wrote: > 2009/12/1 Saeed Iqbal : > > Is your Ajax configured? > > Sorry for my ignorance, we don't use ajax with struts, not sure what > need to be con

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-01 Thread Henry Jen
2009/12/1 Saeed Iqbal : > Is your Ajax configured? Sorry for my ignorance, we don't use ajax with struts, not sure what need to be configured. Would you shed some light for me? Cheers, Henry > > On Wed, Dec 2, 2009 at 12:45 PM, Henry Jen wrote: > >> Hi, >> >> I updated our project using 2.1.6 t

Re: Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-01 Thread Saeed Iqbal
Is your Ajax configured? On Wed, Dec 2, 2009 at 12:45 PM, Henry Jen wrote: > Hi, > > I updated our project using 2.1.6 to 2.1.8.1 and surprised to find > that tag breaks the application. > > An example is > Login > renders to in 2.1.8.1 > > > When I looked into the simple template, seems like

Upgrade 2.1.6 to 2.1.8.1, cause empty tag?

2009-12-01 Thread Henry Jen
Hi, I updated our project using 2.1.6 to 2.1.8.1 and surprised to find that tag breaks the application. An example is Login renders to in 2.1.8.1 When I looked into the simple template, seems like the change in a.ftl and a-close.ftl is causing this. In 2.1.8, the a.ftl basically moved into a-