Hi Drew,
The new WOLips/Eclipse 3.4 that you've just upgraded to allows you to
easily embed all the frameworks that you are using into your project.
This way, you actually don't need to have *any* of the frameworks
installed on your production box if you have "embedded" them properly
in your project. When you build your project on the development box,
it will automatically grab the frameworks from wherever you've told
it to, and if you keep your development box updated (with the latest
WOnder, for example) you don't have to worry about doing the same on
the production box. You also don't have to worry about updated
frameworks on the production box breaking any applications that you
haven't explicitly tested against with the new version.
David
On 7-Mar-09, at 2:08 PM, Drew Thoeni wrote:
David,
This does help. I actually, normally, do it this way, but at one
point in the past I was discussing having the right frameworks on
the production servers (keep in mind, I'm small time compared to
most people on this list) and someone suggested that for the less-
used JARs, I add them to the project so they get moved as part of
the project.
They were probably referring to "embedding" the .jar framework.
Am I misunderstanding that?
Or, is it generally considered better form to just keep the
frameworks all current on production machines (even for the rarely
used ones)?
No, I don't think this would be best practice. Embedding would be far
more unlikely to break something in production.
The "theory" behind it is here: http://wiki.objectstyle.org/
confluence/display/WOL/Embedding+WOFrameworks
In practice, for 3.4, you need to read: http://wolips.blogspot.com/
2008/09/its-alive.html
Especially: "Embedding can now be controlled from the panel. You can
check which sets of frameworks get embedded in your deployment."
Best,
Drew
On Mar 6, 2009, at 11:04 AM, David Avendasora wrote:
Hi Drew,
You are _really_ doing things the hard way. Adding Frameworks to
your projects is much, much easier than adding individual .jars to
your project's Libraries folder.
1) Download the latest Wonder Frameworks, unzip the archive and
add all the FrameworkName.framework directories to your /Library/
Frameworks directory.
2) In Eclipse, right-click on your project, Select Build Path ->
Configure Build Path...
3) Click on the Libraries tab
4) On the right side, click "Add Libraries..."
5) Select "WebObjects Frameworks", click Next
6) Go through the list and select the Frameworks you need
7) Click Finish
8) Click Okay
All those frameworks have now been added to your project and you
don't have to add individual .jar files as they are included in
the Frameworks you just linked.
The only thing I ever actually add to my Project's "Libraries"
folder (then add to my build path so they show up under
"Referenced Libraries") are stand-alone .jars for libraries *other
than* WebObjects/WOnder frameworks.
I hope this helps!
Dave
On Mar 2, 2009, at 5:25 PM, Drew Thoeni wrote:
Screen shots. Good idea.
You can see in this screen shot ERExtensions.jar is in the
"Referenced Libraries" having gotten there by me 1) putting the
JAR in the file system folder "Libraries" and then adding it to
the Java Build Path using project properties and selecting "Add
JARs" and picking this JAR from the project's "Libraries" folder.
Interestingly, the imports in other classes for org.jfree are
working fine and I assume are referencing the JARs in the
"Referenced Libraries" folder.
Thanks again,
Drew
<pastedGraphic.tiff>
On Mar 2, 2009, at 2:51 PM, Chuck Hill wrote:
On Mar 1, 2009, at 3:46 PM, Drew Thoeni wrote:
Checked that and it seems OK. Your earlier post on that was
helpful as com.webobjects was not being resolved. Adding the
properties file corrected that issue.
In this case, my project actually shows the JAR as part of the
Referenced Libraries,
Not sure what you are referring to there.
if I remove it, it shows back up in "Libraries" as part of the
project.
On the Build Path tab of the Properties?
It is, in fact in the Libraries folder and its behavior is as
expected. But, the classes are still not resolved.
Maybe some screen shots of what you have setup might help. If
they are in the Libraries folder of the same project it should
not be a path issue.
Chuck
On Mar 1, 2009, at 2:45 PM, Chuck Hill wrote:
Check the contents of
~/Library/Application\ Support/WOLips/wolips.properties
On Mar 1, 2009, at 7:53 AM, Drew Thoeni wrote:
I just did the big upgrade from Eclipse 3.3 to the 3.4.2 with
WOLips installed fresh.
I added the WO frameworks (as com.webobjects) was not
resolved but am still having difficulties getting JARs in my
Referenced Libraries to resolve.
Example:
I have ERExtensions.jar in Referenced Libraries but "import
er.extensions.localization.ERXLocalizer;" is not resolved.
This strikes me as a path problem, but project properties
point to the correct location.
Any help is appreciated.
Best,
Drew
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-
[email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill%
40global-village.net
This email sent to [email protected]
--
Chuck Hill Senior Consultant / VP Development
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
--
Chuck Hill Senior Consultant / VP Development
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
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%
40avendasora.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/programmingosx
%40mac.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]