On Nov 20, 2008, at 7:45 AM, James Cicenia wrote:
Ok -
Good morning... after sleeping on it... nothing.
When I did not do your session cheat... it complains on startup
about javax.mail.session.
It all works great on my dev and my old server.
Now with your cheat I found the following issues (which don't seem
to send anything out to the log?!)
1) public WHSession createSessionForRequest(WORequest aRequest) {
return new com.hb.Session();
}
My direct action just seems to burb.. it throws nothing but
definitely doesn't
go beyond the following statement:
nextPage
.takeValueForKey
(tag
.resources
(((Session)session()).defaultEditingContext(),"Product"),"resources");
because I have a System.out afterwards and it doesn't get there!?
Any other thoughts (besides wonderizing)?
Break. It. Down. Think. It. Though.
You have _three_ things happening there:
1. ((Session)session()).defaultEditingContext() - with BTW a totally
needless cast that Eclipse can warn you about
2. tag.resources(ec, "Product")
3. nextPage.takeValueForKey(resources, "resources");
So, which one is blocking? Where? Add some more logging. Run it and
get a thread dump from the instance.
Chuck
On Nov 19, 2008, at 10:34 PM, Chuck Hill wrote:
On Nov 19, 2008, at 8:22 PM, James Cicenia wrote:
ok -
1) All new projects will be wonderized, I promise.
2) I will refactor a large app next year into wonder.
3) In the meantime....
What does choke mean? Good question, how about, like nothing goes
to the log file after this call:
nextPage
.takeValueForKey
(tag
.resources
(((Session
)session()).defaultEditingContext(),"Product"),"resources");
so, my suspicion lies in the session handling now that bundles get
bungled.
This is by far the worst thing about webobjects... setting up a
new server.
Try deploying other things!
Something is always missed.
Narrow it down more. It makes no sense that it would hang on a
call to defaultEditingContext(). The EC is already locked at that
point.
Chuck
On Nov 19, 2008, at 10:07 PM, Chuck Hill wrote:
On Nov 19, 2008, at 7:57 PM, James Cicenia wrote:
OK -
I got my application to launch on Linux! WooHoo!
Now, I was originally getting a weir javax,mail.session vs. my
session, so I did the
Chuck Cheat™:
public WHSession createSessionForRequest(WORequest aRequest) {
return new com.hb.Session();
}
Using a modern version of Wonder (with ERExtensions first on the
classpath) should obviate the need to do this.
Anything like ((Session)session()).setXXX works fine.
However when it got to session().defaultEditingContext() it
choked.
Thoughts?
Mostly that you always keep a card or three hidden when asking
questions. But what the heck, I will play. What specifically
does "choked" mean in this context?
Chuck
--
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
--
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-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
