Just sharing my experience too that It also does not like the case where the
project name and project folder have different names.
Farrukh
Sent from my iPad 2
On 2012-04-02, at 10:39 PM, Ted Archibald wrote:
> I can duplicate the bug on my computer by creating a new wonder app called
> test1
I can duplicate the bug on my computer by creating a new wonder app called
test1.0
Something in wolips doesn't like the period, or at least something on my
computer doesn't.
And I can assure it's not a classpath issue because I meticulously copied
and pasted EVERY file between a non-working app a
That also seems unlikely. This should be a classpath order problem and having
ERExtensions first on the classpath (assuming you are using it, WOLips should
do this) should prevent this error.
Chuck
On 2012-04-02, at 9:32 AM, Ted Archibald wrote:
> Well I think I got it cased now, I think it'
Well I think I got it cased now, I think it's because the app name had a
period in the name, perhaps that freaks out the incremental builder.
On Mon, Apr 2, 2012 at 9:34 AM, Ted Archibald wrote:
> The plot thickens...
>
> I'm not sure if this is a bug in wolips or what.
>
> But the symptoms are:
The plot thickens...
I'm not sure if this is a bug in wolips or what.
But the symptoms are:
-When you run the app you get an error like: Class 'Session' exists
(interfacce org.jabsorb.client.Session) but is not a subclass of WOSession.
-In the component validation, some (but not all components)
I think you should spend a few more weeks on this. That's the responsible
thing to do.
On Fri, Feb 17, 2012 at 2:06 PM, Ted Archibald wrote:
> Feels like I'm beating a dead horse:
>
> After trying many combinations of changes I finally found one change that
> helps. If I have wolips generate bu
Feels like I'm beating a dead horse:
After trying many combinations of changes I finally found one change that
helps. If I have wolips generate bundles, everything works perfectly. But
I wonder how I can get bundleless builds to work again.
If I have wolips generate bundles, clean the project t
Now when I call a direct action I keep getting a no such method exceptions.
It appears that my DirectAction class is not being used instead of the
default WODirectionAction.
For instance, if I go to App.woa/wa/test I'll get:
java.lang.NoSuchMethodException:
com.webobjects.appserver.WODirectActio
On 16/02/2012, at 5:34 PM, Ted Archibald wrote:
> Make you code explicitly declare what it uses in a FQ manner and be done with
> it.
>
> What does "in a FQ" manner mean, pardon my ignorance.
"Fully qualified". Use the full package name prefixed to the class name.
--
Paul.
http://logicsq
>
>
> The root issue is that WO is trying to be clever and find a class based on
> the simple name. With the same name in multiple packages, this gets a bit
> dodgy. That it worked before is not the real issue.
Fair enough. I simply wonder why in 7 years of WO development I've never
had this p
Just updated Wonder, it didn't fix anything.
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/op
That looks correct.
What is the exact error message you are getting and what code are you using to
avoid it?
On 2012-02-14, at 3:51 PM, Ted Archibald wrote:
> Here's the output. It appears that the bin folder for the project is missing
> (it exists in the file system though).
>
> System Pro
That must means the /bin directory is not a jar file.
On 2012-02-14, at 3:51 PM, Ted Archibald wrote:
> Here's the output. It appears that the bin folder for the project is missing
> (it exists in the file system though).
>
> System Properties Follow
> file.encoding.pkg = sun.io
> java.ho
Try this and call it in main() to see what the classpath is.
Chuck
static public String dumpJVMConfiguration()
{
StringBuffer output = new StringBuffer("\nSystem Properties
Follow\n");
Properties systemProperties = System.getProperties();
Enumeration property
Every jar from /Library/Java/Extensions and /Library/WebObjects/Extensions
is now removed, still no fix yet. I fired up an older version of
eclipse/wolips and that didn't make a difference either.
On Tue, Feb 14, 2012 at 12:30 PM, Pascal Robert wrote:
> Anything strange in /Library/WebObjects/E
Anything strange in /Library/WebObjects/Extensions ?
> So now I'm getting more perplexed.
>
> I just created a fresh clean wonder app with no references to any extra
> project or library and I get the same error. But I have other projects that
> I can run just fine.
>
> On Tue, Feb 14, 2012 a
It is not finding the Wonder frameworks? Have you updated Eclipse or WOLips
and thus changed something?
On 2012-02-14, at 9:57 AM, Ted Archibald wrote:
> So now I'm getting more perplexed.
>
> I just created a fresh clean wonder app with no references to any extra
> project or library and I
/Library/WebObjects/Extensions is another place that jars get loaded from.
Unless they are also in your app/frameworks (a good idea BTW), clearing this
out can prevent your apps from starting. But it is a place to investigate.
I'd also review the classpath file that is built into your applicat
So now I'm getting more perplexed.
I just created a fresh clean wonder app with no references to any extra
project or library and I get the same error. But I have other projects
that I can run just fine.
On Tue, Feb 14, 2012 at 11:28 AM, Ted Archibald wrote:
> I also tried removing any superflu
I also tried removing any superfluous frameworks in the classpath, also to
no avail.
On Tue, Feb 14, 2012 at 11:21 AM, Ted Archibald wrote:
> I tried that as well and I got the same original error.
>
>
> On Tue, Feb 14, 2012 at 8:44 AM, John Huss wrote:
>
>> You could also just tell WO explicitl
I tried that as well and I got the same original error.
On Tue, Feb 14, 2012 at 8:44 AM, John Huss wrote:
> You could also just tell WO explicitly where your classes are. You can do
> this in your Application's main method:
>
> _NSUtilities.setClassForName(Main.class, Main.class.getSimpleName()
I had some old jars in /Library/Java/Extensions so I removed them to no
avail.
On Mon, Feb 13, 2012 at 9:55 PM, Chuck Hill wrote:
> Read carefully. The first is for Session.java, the second is for
> Main.java. Either make the default action a direction action and in
> defaultAction() return the
You could also just tell WO explicitly where your classes are. You can do
this in your Application's main method:
_NSUtilities.setClassForName(Main.class, Main.class.getSimpleName());
_NSUtilities.setClassForName(Session.class, Session.class.getSimpleName());
_NSUtilities.setClassForName(DirectAc
Read carefully. The first is for Session.java, the second is for Main.java.
Either make the default action a direction action and in defaultAction() return
the fully qualified name of the Main component, or, in Application override
pageForNameWithContext() (or whatever it is is called) and if
No, this is the stack trace I get:
: Exception
occurred while handling request:
java.lang.IllegalArgumentException:
Class 'Session' exists
(interface org.jabsorb.client.Session) but is not a subclass of WOSession.
[2012-2-13 18:33:34 CST] java.lang.IllegalArgumentException:
Class 'Session' ex
Is the Session class name in the stack trace correct? If it is correct, your
app .jar is missing something. If it is not correct, the _sessionClass has the
wrong signature or is in the wrong class.
Chuck
On 2012-02-13, at 4:36 PM, Ted Archibald wrote:
> I'm currently having this same issue
I'm currently having this same issue on a project I haven't touched in
months. I haven't changed wonder, nothing changed in the class path.
There's no obvious reason what's going on, and overriding _sessionClass
doesn't fix the problem, cleaning the project didn't help, restarting the
computer di
Changing compiler settings back and forth seemed to clean it up. Thanks.
JPM
Le 7 juin 2011 à 14:39, Mike Schrag a écrit :
> your classpath is messed up ...
>
> On Jun 7, 2011, at 8:37 AM, Jean Pierre Malrieu wrote:
>
>>
>> Le 7 juin 2011 à 14:23, Mike Schrag a écrit :
>>
>>> not sure what
your classpath is messed up ...
On Jun 7, 2011, at 8:37 AM, Jean Pierre Malrieu wrote:
>
> Le 7 juin 2011 à 14:23, Mike Schrag a écrit :
>
>> not sure what changed in your app, but it's basically just guessing wrong on
>> the session class .. you can override _session() in your WOApplication
Le 7 juin 2011 à 14:23, Mike Schrag a écrit :
> not sure what changed in your app, but it's basically just guessing wrong on
> the session class .. you can override _session() in your WOApplication
> subclass and return the exact class you expect it to be.
if I put the following method in my A
whoops, yeah, sorry
On Jun 7, 2011, at 8:32 AM, Jean Pierre Malrieu wrote:
> You mean _sessionClass() ?
>
> Le 7 juin 2011 à 14:23, Mike Schrag a écrit :
>
>> not sure what changed in your app, but it's basically just guessing wrong on
>> the session class .. you can override _session() in you
You mean _sessionClass() ?
Le 7 juin 2011 à 14:23, Mike Schrag a écrit :
> not sure what changed in your app, but it's basically just guessing wrong on
> the session class .. you can override _session() in your WOApplication
> subclass and return the exact class you expect it to be.
>
> ms
>
not sure what changed in your app, but it's basically just guessing wrong on
the session class .. you can override _session() in your WOApplication subclass
and return the exact class you expect it to be.
ms
On Jun 7, 2011, at 8:20 AM, Jean Pierre Malrieu wrote:
> No I didn't... My Wonder vers
No I didn't... My Wonder version is probably several months old...
Le 7 juin 2011 à 14:16, Mike Schrag a écrit :
> did you update wonder within the past two days? try updating again.
>
> On Jun 7, 2011, at 7:56 AM, Jean Pierre Malrieu wrote:
>
>> Hi all,
>>
>> All of a sudden, I cannot debug t
did you update wonder within the past two days? try updating again.
On Jun 7, 2011, at 7:56 AM, Jean Pierre Malrieu wrote:
> Hi all,
>
> All of a sudden, I cannot debug the app I was working on...
>
> I am now receiving the following exception:
>
> Application: SaisieIEP
> Error: java.lang.Ill
Hi all,
All of a sudden, I cannot debug the app I was working on...
I am now receiving the following exception:
Application: SaisieIEP
Error: java.lang.IllegalStateException exception
Reason:
java.lang.IllegalStateException: An Exception occurred while generating the
Exception page 'WOException
36 matches
Mail list logo
