IT WORKS!!! But getting there was not painless.
After sending the message below to the list way after my bedtime, I
wanted to try an old tiny WOApp that I had developed to diagnose the
runtime environment to see what environment variables a running WO
app was getting under Xcode. The app needed a couple small
refinements to get me what I was looking for, so I fired up Xcode,
made the changes and tried a build/run.
Xcode's build blew chunks! I got the old "Command /Developer/Private/
jam failed with exit code 1." When I looked through the Build Log, I
found a java.lang.ArrayIndexOutOfBoundsException on the Java compiler!
Worse, this occurred on every Xcode project that I tried, including
those for my client's projects that I would have to be working on
this morning. I was not a happy camper. The only significant change I
had made to my system since the last time Xcode worked was to install
Eclipse.
After spending the next couple hours Googling on error messages and
generally trying everything I could think of, including drafting a
near panic message to this list for help, I decided to see if a
reboot would help. It fixed nearly everything!
Not only did the reboot fix my Xcode problem, it fixed my Eclipse
problems as well. So I trashed the message to the list that I was
drafting before it trashed all the nice people who have helped me
find salvation with Eclipse/WOLips (or at least started me on the
road thereto).
This morning, I'm at the stage where I can create a new WO project in
eclipse, enhance, build, run and debug it as per the tutorials at:
http://wiki.objectstyle.org/confluence/display/WOL/Tutorials
Nowhere did I see a suggestion that one should restart their Mac
after downloading and installing Eclipse/WOLips. Was that a
requirement that I just missed somewhere? If so, sorry for all the
unnecessary noise I made on the list. If not, perhaps the suggestion
ought to go somewhere in the instructions or troubleshooting tips.
I still get the incomplete project when I first create a new project,
but closing it and reopening it fixes that problem and now I can go
on with the project's development.
Today is client work day, but I'll be working with Eclipse over the
weekend to gain greater familiarity.
Thanks for all your help.
Regards,
Jerry
On Mar 2, 2007, at 2:29 AM, Jerry W. Walker wrote:
> Hi, Chuck,
>
> Thanks for offering to help.
>
> I went to the "Troubleshooting Problems Building and Running" that
> you suggested. Following your Mac OS X wobuild.properties file
> settings, I discovered that the only significant difference was my:
>
> wo.woroot=/
>
> vs. your:
>
> wo.woroot=/System
>
> That sounded like a possibility, so I set mine to /System, started
> Eclipse, deleted my earlier project and created a new one. No
> change. :-(
>
> However, I did notice that the Windows example that you posted on
> the page looks a little munged. In particular, the line that you
> commented out dribbled onto the next line and concatenated the
> setting on that line so it looks like this:
>
> #wo.dir.user.home.library=C:/Documents and Settings/Chuck Hill/Local/
> Library wo.dir.user.home.library=C:/Temp wo.dir.library=U:/Apple/
> Library
>
> (Note the "wo.dir.library=" starting at the end of the second line.)
>
> I checked my environment variables as per the lower pane and didn't
> see anything that might cause trouble on Mac OS X except my:
>
> JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/
> 1.5.0/Home
>
> Eclipse is not expecting Java 1.4, is it?
>
> Regards,
> Jerry
>
>
> On Mar 1, 2007, at 7:41 PM, Chuck Hill wrote:
>
>> Sounds like a config problem on your machine.
>>
>> Take a look here:
>>
>> http://wiki.objectstyle.org/confluence/display/WOL/Troubleshooting
>> +Problems+Building+and+Running
>>
>>
>> On Mar 1, 2007, at 4:34 PM, Jerry W. Walker wrote:
>>
>>> Hi, Mike,
>>>
>>>
>>> On Mar 1, 2007, at 9:13 AM, Mike Schrag wrote:
>>>>> In particular, note that it lists the javawebobjects.jar, so it
>>>>> shouldn't have problems accessing WOSession; but it seems to.
>>>> Can you send a screenshot of your Problems View along with the
>>>> source to the Java file that it claims is having a problem? Can
>>>> you verify that the java file is actually importing WOSession
>>>> (cmd-shift-o in the java editor = autogenerate imports).
>>>>
>>>> ms
>>>
>>> Sorry I didn't get back to you sooner. I had a small deadline
>>> this morning after reading your message, then forgot about your
>>> request till this evening.
>>>
>>> Here is a screenshot of the Problems View:
>>>
>>> <Picture 2.png>
>>>
>>> and here is the source for the file in question:
>>> ========================================================
>>> // Generated by the WOLips Templateengine Plug-in at Mar 1, 2007
>>> 7:30:04 AM
>>>
>>> import com.webobjects.appserver.*;
>>>
>>> public class Main extends WOComponent {
>>>
>>> public Main(WOContext context) {
>>> super(context);
>>> }
>>>
>>> }
>>> ========================================================
>>>
>>> After cmd-shift-o in the java editor, the source file looks like
>>> this:
>>> ========================================================
>>> // Generated by the WOLips Templateengine Plug-in at Mar 1, 2007
>>> 7:30:04 AM
>>>
>>> import com.webobjects.appserver.WOComponent;
>>> import com.webobjects.appserver.WOContext;
>>>
>>> public class Main extends WOComponent {
>>>
>>> public Main(WOContext context) {
>>> super(context);
>>> }
>>>
>>> }
>>> ========================================================
>>>
>>> and the errors remain.
>>>
>>> I have a screenshot of the entire Eclipse window with the
>>> Problems View showing the errors and the code in the Java Editor,
>>> but it's over 140KB, so I decided to comply with your request as
>>> you made it.
>>>
>>> If it helps any, this is completely reproducible. I was able to
>>> achieve this state by completing the Eclipse/WOLips installation
>>> instructions at:
>>>
>>> http://wiki.objectstyle.org/confluence/display/WOL/Install
>>> +WOLips+with+Eclipse+Update+Manager
>>>
>>> Then I went to the "Create a new WO Application" page at:
>>>
>>> http://wiki.objectstyle.org/confluence/display/WOL/Create+a
>>> +new+WO+Application
>>>
>>> and did steps 1 - 6 without a hitch. In step 7, I seemed to trip
>>> over the WOLips Bug mentioned in that step. As I said in earlier
>>> email, I wasn't able to create the project last night with the
>>> right components in over 8 tries without first closing the
>>> project and reopening it.
>>>
>>> After quitting Eclipse last night, then restarting it this
>>> morning, when I created the project, all the pictured components
>>> were there.
>>>
>>> The error messages appeared in the Problems view every time. I
>>> also deleted the project, both in Eclipse and on the disk at the
>>> end of each try so I would be working with a clean slate.
>>>
>>> About the only customization I was able to do, given the explicit
>>> nature of the steps, was to run the downloaded Eclipse
>>> application directory off my Desktop and create my workspace
>>> directory at ~/Development/Eclipse/workspace/
>>>
>>> I had nothing in either the Eclipse application directory, nor in
>>> the workspace directory, other than what was put there by doing
>>> the steps outlined on the web site.
>>>
>>> I hadn't moved either of them from the time I downloaded Eclipse
>>> until this morning, when I moved the Eclipse application
>>> directory to /Local/Applications/Eclipse/.
>>>
>>> I don't remember whether I did that before or after I was able to
>>> create a complete project.
>>>
>>> If it helps, I'm running off a MacBook Pro, 2.33 GHz Intel Core 2
>>> Duo with Mac OS X 10.4.8. Here's what Terminal says for Java:
>>>
>>> % java -version ~
>>> java version "1.5.0_07"
>>> Java(TM) 2 Runtime Environment, Standard Edition (build
>>> 1.5.0_07-164)
>>> Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
>>>
>>> The version of Eclipse that I downloaded was:
>>> Eclipse SDK
>>> Version: 3.2.1
>>> Build id: M20060921-0945
>>>
>>> For the WOLips plug-in, when I click the Configuration Details
>>> button on the About Eclipse panel, Eclipse tells me that it
>>> installed:
>>>
>>> org.objectstyle.wolips (2.0.0.3860) "WOLips Core Plug-
>>> in" [Active]
>>>
>>> All other plugins from org.objectstyle.wolips also say
>>> (2.0.0.3860) and they all say [Active] or [Resolved] except this
>>> line:
>>>
>>> org.objectstyle.wolips.jprofiler.launching (2.0.0.3860)
>>> "WOLips JProfiler Launching Plug-in" [Installed]
>>>
>>> I hope this helps you find trace down the problem. With all the
>>> feedback I'm getting, both off the mailing lists and from
>>> Eclipse, I'm starting to get excited.
>>>
>>> Thanks for your support.
>>>
>>> Regards,
>>> Jerry
>>>
>>>
>>>
>>> --
>>> __ Jerry W. Walker,
>>> WebObjects Developer/Instructor for High Performance
>>> Industrial Strength Internet Enabled Systems
>>>
>>> jerrywwalke..mail.com
>>> 203 278-4085 office
>>>
>>>
>>>
>>
>> --
>>
>> Practical WebObjects - for developers who want to increase their
>> overall knowledge of WebObjects or who are trying to solve
>> specific problems.
>> http://www.global-village.net/products/practical_webobjects
>>
>>
>>
>>
>>
>
>
> --
> __ Jerry W. Walker,
> WebObjects Developer/Instructor for High Performance Industrial
> Strength Internet Enabled Systems
>
> jerrywwalke..ee-em-aye-eye-ell.com
> 203 278-4085 office
>
>
>
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
jerrywwalke..ee-em-aye-eye-ell.com
203 278-4085 office
This archive was generated by hypermail 2.0.0 : Fri Mar 02 2007 - 08:50:53 EST