You should ask that on the Apple’s WebObjects Development or Deployment mailing lists. I’m certainly someone will help you fixing that problem.

Application: WOAppName
Error: java.lang.reflect.InvocationTargetException exception
Reason:
java.lang.reflect.InvocationTargetException

I believe this is coming from the cgi adaptor but I have not been able to get the Apache 1.3 or 2.2 adaptors to work. Can anyone help?

Thanks

Hi!

One of the best links I can give you is the WO Community page. Get Eclipse and checkout the simple WOLips plugin installation instructions.

The WO Community page has the “Getting started” link, with everything you need to setup your development environment, and some tutorials made by a few people in the community. Janine’s tutorial seems to be particularly cool.

One of the problems of WO is precisely the “learning cliff”, specially how confusing is to setup everything and start. People are trying to work on that. Until then, you may get all the help you need on the WebObjects Development mailing list, hosted by Apple. There’s also the deploy list.

Feel free to ask all kinds of questions on that list, I have found there many many helpful people who will help you getting on this WOnderful world!

BTW, don’t forget that, if you want to use Wonder (a huge open-source set of frameworks that provide a lot of enhancements to the bare-bones WO), and I DO recommend you to do that, you must use WebObjects 5.3.1 (or 5.3.2 or whatever the latest 5.3 version is, I don’t recall it). Although Wonder already compiles with 5.4, there are still many bugs.

That said, you have done a masterful job of clearing that up for me, and I do appreciate it. Do you have any links to some more information for the Eclipse WOLips plugin, leaning towards the rudimentary?

Again, thank you for the clarification!

xCode, and all the other tools, moved from the “deprecated” status in Tiger to “dead” in Leopard. Apple finally killed the Java/ObjectiveC bridge, so none of the tools work.

xCode still opens old WebObjects projects, and compiles them (that is a pure Java operation, it’s not related to the bridge) but won’t allow you to create any more projects.

Eclipse and the WOLips plugin are now the official tools to create WebObjects projects. WOLips, although it’s created and maintained by the open-source community, is being partially sponsored by Apple. Apple itself uses Eclipse/WOLips massively, and that is one the the reasons the Apple tools were dropped: they clearly think Eclipse and WOLips are much better than their own tools.

Personally, I jumped to Eclipse some time ago, and I love every minute of it. It’s so much better than xCode for Java coding that you won’t ever want to use another IDE. It’s a bit heavy on the machine (specially on RAM, you should have 2GB at least) but all those CPU cycles are being used to do very useful stuff.

WOLips is the plugin that will make Eclipse create and compile WO projects, and replaces all the Apple tools (WOBuilder, EO Modeler, etc) with modern tools that are integrated right there on the IDE.

Has anyone experienced this or have any idea how to fix it or where I could go to figure out how to do so?

Thanks in advance.

/Volumes/Xcode\ Tools/Packages/Packages/WebObjectsDevelopment.pkg/Contents/Archive.pax.gz

you have:

EOModeler.framework
JavaEOTool.framework
JavaWebObjects.framework
JDBCEOAdaptor.framework
JNDIEOAdaptor.framework

and in

/Volumes/Xcode\ Tools/Packages/Packages/WebObjectsRuntime.pkg/Contents/Archive.pax.gz

you have:

JavaDirectToWeb.framework
JavaEOApplication.framework
JavaDTWGeneration.framework
JavaEOCocoa.framework
JavaEODistribution.framework
JavaEOGeneration.framework
JavaEOAccess.framework
JavaEOControl.framework
JavaEOInterface.framework
JavaEOInterfaceCocoa.framework
JavaEOInterfaceSwing.framework
JavaEOProject.framework
JavaEORuleSystem.framework
JavaFoundation.framework
JavaJDBCAdaptor.framework
JavaJNDIAdaptor.framework
JavaWebObjects.framework
JavaWebServicesClient.framework
JavaWebServicesGeneration.framework
JavaWebServicesSupport.framework
JavaWOExtensions.framework
JavaWOJSPServlet.framework
JavaXML.framework

Note that the JavaWebobjects.framework is inside both Archives, you should use the one in the WebobjectsRuntime.