Le 09-11-23 à 14:59, Calven Eggert a écrit :
Thanks All! I'm able to install my app on the server now with or
without my framework embedded.
It seems that sometimes the build will not find the framework on my
machine until I quit eclipse, restart it and then do a clean. not
sure why. Has anyone else found this problem?
Because this "new" version catches the "The relationship attachment
is a to-many but also propagates its primary key" error I'll have to
now spend some time on this. :-( work never ends does it?
Oh yes, Wonder, Entity Modeler and the component editor now finds a
hell lot of errors that the old tools didn't catch up. It's a lot of
work to fix those, but it will improve your apps.
Again, thanks to all for your quick responses. It's near impossible
to get my work to pay for WOWODC, but in any case, if you guys are
in Toronto, give me a call and I'll take you out for a beer. Chuck
Hill and Mike Schrag, I owe you many beer over the years of help and
now Pascal and David.
Toronto, the city where none of your sports teams wins anything? :-)
But at least you still have a baseball team...
Calven
On 2009-11-23, at 2:22 PM, David Avendasora wrote:
On Nov 23, 2009, at 2:13 PM, Pascal Robert wrote:
Le 09-11-23 à 14:05, Calven Eggert a écrit :
hmmm, I did that, checked off the local/system frameworksin
WOLips Deploy and the install includes all the libraries except
mine. :-(
Looks like the Build path stuff is wrong. In the Projects tab I
include my project folder and in the Libraries Tab I added
myframework.jar file from the /Library/Framework/
myframework.framework/Resources/Java/ folder. This can't be right
because you say that I don't need to include my /LibraryFramework
any more.
No need to include your framework as a project in the Build Path,
you should add it as a WebObjects Library Framework, just like
other frameworks instead. In 3.4, this is where the major change
was done. So the "new" steps is to include your framework as a
Library Framework and if your framework source project is open in
Eclipse, WOLips will pick up the source, if your framework project
is closed in Eclipse, it will pick up the one in /Library/
Frameworks.
BUT you do need to install your framework in /Library/Frameworks
(on your development machine) before you build your app, or else
you have an old version of your framework (or no framework at all)
in your app. When I said you don't need to worry about /Library/
Frameworks, I meant on the deployment side, for development you
still need it.
I think you have that backwards. With the NewHotness WOLips (from
last January), for DEVELOPMENT you don't need a compiled framework
in Library/Frameworks, but if you are going to use WOLips Ant Tools
-> Install to DEPLOY your application, then you do need a fully
compiled version of your Frameworks in /Library/Frameworks.
With that said, Hudson is a much better way to go about building
for deployment than using WOLips Ant Tools -> Install.
Dave
So the steps is : when you are ready to deploy, run a Ant install
on your framework, after run the Ant install on your app and your
framework should be embed in your app just like Wonder and the WO
frameworks. I think David A. covered this in his WOWODC West
session.
hmmm, how to I make this right?
On 2009-11-23, at 1:42 PM, Pascal Robert wrote:
Embed your frameworks (and any other frameworks) into your app
and you won't have to worry about /Library/Frameworks anymore.
Right-click on your project name -> Properties, and in the
WOLips Deploy, check the boxes to say that you want to embed
local and system frameworks. Run the ant install again and your
app will now have all needed frameworks inside itself.
Ah, the Project.name= entry was NOT filled in in the
build.properties file and so that fixed the problem of my
Framework not appearing. Thanks for that.
The problem now is that installing my app on the server can't
find the framework and this time IT IS located in /Library/
Frameworks because I put it there on the server. I know this
because I get the error "java.lang.NoClassDefFoundError" for a
class in my framework.
My original WO application projects are from a long time ago
and so I suspect that this may be the problem. I am using
build.xml files from newly created WO projects in eclipse. What
should I check for in my build settings to make sure the WO app
is connecting to the framework properly? (The app runs no
problem from eclipse)
Current configuration:
Eclipse 3.4.2
WO5.4.3
WOLips from here(http://webobjects.mdimension.com/wolips/stable)
Java 1.5
Wonder 54 binaries
Calven
On 2009-11-23, at 12:07 PM, David LeBer wrote:
On 2009-11-23, at 11:51 AM, Calven Eggert wrote:
I just updated to Snow Leopard last week and I'm having
trouble building my WO framework and projects.
The first build I attempt is my framework. It builds with no
errors, although lots of warnings like ...should be
parameterized, but when I do the install the framework is NOT
in the /Library/Frameworks folder. It is in the /Build
folder, but looking in there, in the .framework/Resources/
Java folder the .jar is not there. hmmm
Are you sure?
Did you check the /Library/Framworks with the terminal (ls -
al)? You might find a .frameworks folder with the correct
creation/mod time. That would mean that you are missing the
project.name= entry in your project's build.properties.
If that is the case, how old was the WOLips you were updating
from?
Here is the output:
Buildfile: /Users/ceggert/Projects/COREFW/build.xml
init.properties:
init.install:
init.build:
compile:
build.woframework:
[woframework] Installing in /Library/Frameworks
javaclient:
install:
BUILD SUCCESSFUL
Total time: 873 milliseconds
I do have the wolips.properties in ~/Library/Application
Support/WOLips.
I have read the last two articles here (http://wolips.blogspot.com/
) but I can't say i fully understand it all.
Any suggestions?
Calven
_______________________________________________
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/dleber_wodev%40codeferous.com
This email sent to [email protected]
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
twitter: http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
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/probert%40macti.ca
This email sent to [email protected]
----
Pascal Robert
[email protected]
AIM: MacTICanada
Twitter : MacTICanada
LinkedIn : http://www.linkedin.com/in/macti
----
Pascal Robert
[email protected]
AIM: MacTICanada
Twitter : MacTICanada
LinkedIn : http://www.linkedin.com/in/macti
_______________________________________________
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]
David Avendasora
Senior Software Engineer
K12, Inc.
*****
WebObjects Documentation Wiki :
http://wiki.objectstyle.org/confluence/display/WO/
*****
WebObjects API:
http://developer.apple.com/legacy/mac/library/documentation/MacOSXServer/Reference/WO54_Reference/index.html
*****
----
Pascal Robert
[email protected]
AIM: MacTICanada
Twitter : MacTICanada
LinkedIn : http://www.linkedin.com/in/macti
_______________________________________________
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]
