Re: WOLips new Wonder app+framework creation fails
Re: WOLips new Wonder app+framework creation fails
- Subject: Re: WOLips new Wonder app+framework creation fails
- From: Mike Schrag <email@hidden>
- Date: Wed, 18 Mar 2009 21:22:40 -0400
All that really matters is that ERX is above the Java* frameworks ...
You would have failed much earlier if that wasn't the case.
On Mar 18, 2009, at 8:30 PM, Ricardo J. Parada wrote:
On Mar 18, 2009, at 3:04 PM, Mike Schrag wrote:
Essentially, this isn't really a problem with WOLips, it's a
"problem" that Wonder does some crazy stuff that requires it to
come in(near) the top of the classpath. However, I think I'm to
blame for BOTH of those, soooooo well, you know. The other thing
to consider is that my sense is that most people will start new
projects and just use the New Wonder Application wizard, which sets
everything up for you. If you're adding Wonder into an existing
project after the fact, it's presumed that you know you're in for a
bit of a ride.
I read this and I checked my .classpath for an app where I converted
to Wonder after the fact and realized the .classpath entries are not
the same and not in the same order as the .classpath created with
the Wonder wizard.
I don't quite understand yet why but I'm gonna go back and change
the .classpath for that application to match the one created by the
wizard for creating a wonder app.
I had a problem where characters are not displayed correctly and I'm
hoping this may have something to do with that.
:-)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden