I removed those three ide services files from the project today when
troubleshooting this. Funny thing is I first launched a test
deployment as a new different application and all was working, so I
was sure that those IDE services files were the problem first. Then I
went to the "real" app config in Monitor, selected the new deployed
bundle, launched it only to find that the resources URLs were wrong
again! .... wow .... so, here I was having the problem using the same
woa under one app config and no resource url problem with the other
temp app I had made to test the deployment. The only difference was
that the real app config had the -WOConcurrentRequestHandling YES
option and I had not set that for my test app.
So sure enough, removing that from app config and relaunching made
the problem go away!! This was the last thing I expected to be
affecting resource URLs.
Since I am using Wonder, I guess I have the Wonder resource manager
being used, so I need to poke around and put logging statements in
some useful places to figure out why this problem happens ....
actually I will try and simulate in development first when I get back
to it to see if I can affect the URLs by changing the
WOFrameworksBaseUrl and WOConcurrentHandling in Eclipse launch args.
Very very strange and totally reproducible in deployment by just that
one launch parameter in Monitor. I will let you know what I find out.
On Dec 7, 2007, at 5:08 PM, Mike Schrag wrote:
> That's insanity ... I would double-check that _WOIDEProject isn't
> screwing with you ... Now I'm just paranoid.
>
> ms
>
> On Dec 7, 2007, at 4:50 PM, Kieran Kelleher wrote:
>
>> This has me puzzled ..... just asking if anyone has seen this before:
>>
>> I deploy fully embedded builds which normally works fine, however
>> when concurrent request handling is turned on via launch args in
>> WOMonitor app config, the app seems to ignore the -
>> WOFrameworksBaseURL argument and proceeds to render all resource
>> URLs to default frameworks locations (and of course they are not
>> there ... they are embedded in the app). Stopping app, removing
>> the -WOAllowsConcurrentRequestHandling=true parameter and
>> relaunching in Monitor and all ws resource URLs work properly again!!
>>
>> Any ideas?
>>
>> App was built with today's WOLips and Wonder is a week old. All
>> deployed on WO 5.3.3 on Tiger server.
>>
>>
>> Regards, Kieran
>>
>>
>>
>>
>>
>
This archive was generated by hypermail 2.0.0 : Fri Dec 07 2007 - 23:45:29 EST