Re: submit button errors on deployment

2011-02-11 Thread Kieran Kelleher
Just guessing (disclaimer), but possibly WOOgnl is included in the classpath of an "Other" framework and you have "exported it" and "Other" framework is in classpath of the app. IIRC, the build/embedding only looks at the app classpath, Whereas Eclipse classpath calculation may be a little diffe

Re: submit button errors on deployment

2011-02-10 Thread Chuck Hill
Possibly because WOLips loads it. If it does. On Feb 10, 2011, at 2:41 PM, Joe Little wrote: > A new feature of Eclipse 3.6.1? :) > > On Thu, Feb 10, 2011 at 2:37 PM, Chuck Hill wrote: >> On Feb 10, 2011, at 2:08 PM, Joe Little wrote: >>> On Thu, Feb 10, 2011 at 2:04 PM, Chuck Hill >>> wrot

Re: submit button errors on deployment

2011-02-10 Thread Joe Little
A new feature of Eclipse 3.6.1? :) On Thu, Feb 10, 2011 at 2:37 PM, Chuck Hill wrote: > On Feb 10, 2011, at 2:08 PM, Joe Little wrote: >> On Thu, Feb 10, 2011 at 2:04 PM, Chuck Hill wrote: >>> On Feb 10, 2011, at 2:01 PM, Joe Little wrote: >>> That was it. Why oh why does it work in develop

Re: submit button errors on deployment

2011-02-10 Thread Chuck Hill
On Feb 10, 2011, at 2:08 PM, Joe Little wrote: > On Thu, Feb 10, 2011 at 2:04 PM, Chuck Hill wrote: >> On Feb 10, 2011, at 2:01 PM, Joe Little wrote: >> >>> That was it. Why oh why does it work in development? >> >> I am not sure. Is it getting embedded? Is it not installed in your dev >> env

Re: submit button errors on deployment

2011-02-10 Thread Joe Little
On Thu, Feb 10, 2011 at 2:04 PM, Chuck Hill wrote: > > On Feb 10, 2011, at 2:01 PM, Joe Little wrote: > >> That was it. Why oh why does it work in development? > > I am not sure.  Is it getting embedded?  Is it not installed in your dev > environment, so embedding can't find it? Its working w/ W

Re: submit button errors on deployment

2011-02-10 Thread Chuck Hill
On Feb 10, 2011, at 2:01 PM, Joe Little wrote: > That was it. Why oh why does it work in development? I am not sure. Is it getting embedded? Is it not installed in your dev environment, so embedding can't find it? > As for your quip about UNIX knowledge, you got me on that one. Especially

Re: submit button errors on deployment

2011-02-10 Thread Joe Little
That was it. Why oh why does it work in development? As for your quip about UNIX knowledge, you got me on that one. On Thu, Feb 10, 2011 at 1:55 PM, Chuck Hill wrote: > > On Feb 10, 2011, at 1:49 PM, Joe Little wrote: > >> Its embedded, but I'm wondering if there is a version issue with the >> c

Re: submit button errors on deployment

2011-02-10 Thread Chuck Hill
On Feb 10, 2011, at 1:49 PM, Joe Little wrote: > Its embedded, but I'm wondering if there is a version issue with the > classpath, as if something is overriding the methods in a new way. Do you see WOOGNL.framework in /Library/WebObjects/Applications/Affiliates.woa/Contents/Frameworks? It is N

Re: submit button errors on deployment

2011-02-10 Thread Joe Little
Its embedded, but I'm wondering if there is a version issue with the classpath, as if something is overriding the methods in a new way. I don't get a classpath when running in development, but Wonder reports it in deployment, although its not easily parsable to the naked eye :) com.webobjects.cla

Re: submit button errors on deployment

2011-02-10 Thread Chuck Hill
Is it missing from the deployment server? Did not get embedded? Classpath is wrong? On Feb 10, 2011, at 11:45 AM, Joe Little wrote: > Yep, it's my status page since I couldn't list multiple entities in one page, > i am instead getting 4 different arrays and creating listpageinterfaces for >

Re: submit button errors on deployment

2011-02-10 Thread Joe Little
Yep, it's my status page since I couldn't list multiple entities in one page, i am instead getting 4 different arrays and creating listpageinterfaces for each similar to the excel look demo. As for wognl, it's enabled, as it works in development mode. On Feb 10, 2011, at 11:17 AM, David LeBer

Re: submit button errors on deployment

2011-02-10 Thread David LeBer
On 2011-02-10, at 2:04 PM, Joe Little wrote: > I'm getting these errors: > > Error: > com.webobjects.appserver._private.WODynamicElementCreationException: > 'action' is a constant. > Reason: > 'action' > is a constant. > > For this section > > >value="$recentN

Re: submit button errors on deployment

2011-02-10 Thread Joe Little
Again, I get these errors only in deployment. On Feb 10, 2011, at 11:04 AM, Joe Little wrote: > I'm getting these errors: > > Error: > com.webobjects.appserver._private.WODynamicElementCreationException: > 'action' is a constant. > Reason: > 'action' > is a constant. > > For this s

submit button errors on deployment

2011-02-10 Thread Joe Little
I'm getting these errors: Error: com.webobjects.appserver._private.WODynamicElementCreationException: 'action' is a constant. Reason: 'action' is a constant. For this section                 In ModernLook. I noticed t