On 2012-02-14, at 9:03 PM, Ramsey Gurley wrote:
> Yeah, a "fluffy bunny" of deployment to round off the sharp edges would be
> nice. Maybe someday I will write a script/installer/jnlp/something that
> makes deployment extremely simple. I even know what to call it already...
>
> WOnan the Dep
Yeah, a "fluffy bunny" of deployment to round off the sharp edges would be
nice. Maybe someday I will write a script/installer/jnlp/something that makes
deployment extremely simple. I even know what to call it already...
WOnan the Deployer!
;-)
Ramsey
On Feb 14, 2012, at 5:46 PM, James Cice
That was it!
I had to include in application:
setFrameworksBaseURL("/WebObjects/MidwestFoodsWeb.woa/Frameworks");
You would think "EVERYTHING" came included with a pure wonder d2w app. :-)
Don't know how it ever worked before.
Thanks
James
On Feb 14, 2012, at 6:34 PM, Chuc
frameworksBaseURL set incorrectly?
http://wiki.wocommunity.org/display/WOL/WOApplication
On 2012-02-14, at 2:48 PM, James Cicenia wrote:
> src="/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js">
>
> The above is the url on the server... I would think that it would have the
It should if you set WOFrameworksBaseURL.
Ramsey
On Feb 14, 2012, at 3:48 PM, James Cicenia wrote:
> src="/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js">
> The above is the url on the server... I would think that it would have the
> app navme first i.e.
>
> /WebObjects/MW
The above is the url on the server... I would think that it would have the app
navme first i.e.
/WebObjects/MWF.woa/Frameworks .
no?
James
On Feb 14, 2012, at 4:09 PM, Chuck Hill wrote:
>
> On 2012-02-14, at 12:39 PM, James Cicenia wrote:
>
>> I don't know.
>>
>> Everything else wor
On 2012-02-14, at 12:39 PM, James Cicenia wrote:
> I don't know.
>
> Everything else works everywhere else. All the header files see the script
> files, etc.
> Straight out of the box D2W to edit page. Full embed deploy.
Embedding does not mean you don't need to split install the web server
r
I don't know.
Everything else works everywhere else. All the header files see the script
files, etc.
Straight out of the box D2W to edit page. Full embed deploy.
I am now looking around in circles.
Any other hints?
On Feb 14, 2012, at 1:11 PM, Chuck Hill wrote:
>
> On 2012-02-14, at 10:20
On 2012-02-14, at 10:20 AM, James Cicenia wrote:
> OK -
>
> I see all this but what am I supposed to do? Works great on my dev machine
> but deployment breaks.
Then find what is different. Did you forget to do the split install of web
server resources?
>
> This is also a very pure plan ja
By not creating a new WOContext :-)
I forget exactly what I was doing, but I think I was loading a component with
the action binding on an AMC. The action binding generated a new page, the new
page had a new context, and loaded prototype.js via AOD into the existing page.
Then everything br
Stick a breakpoint in the AOD. Is Prototype.js ever reloaded.
Ramsey
On Feb 14, 2012, at 10:42 AM, James Cicenia wrote:
> It is in the header
>
> /WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js
> and loads just find straight from the browser.
>
> James
>
>
>
> On Feb 14,
OK -
I see all this but what am I supposed to do? Works great on my dev machine but
deployment breaks.
This is also a very pure plan jane ERModernLook application... so I don't know
where new WOContexts would come from?
how did you solve it before?
On Feb 14, 2012, at 12:01 PM, Ramsey Gurle
AOD is on line 159 of wonder.js. It's called whenever you do a
ERXResponseRewriter on an ajax response. ERXResponseRewriter keeps track of
what it sends down, so it usually doesn't resend prototype.js. But if
something happens that generates a new WOContext, then prototype.js sometimes
can get
It is in the header
/WebObjects/Frameworks/Ajax.framework/WebServerResources/wonder.js
and loads just find straight from the browser.
James
On Feb 14, 2012, at 11:39 AM, Chuck Hill wrote:
> wonder.js is not getting loaded.
>
>
> On 2012-02-14, at 8:52 AM, James Cicenia wrote:
>
>> Referenc
wonder.js is not getting loaded.
On 2012-02-14, at 8:52 AM, James Cicenia wrote:
> ReferenceError: Can't find variable: AUP
>
>
>
> What is this? It stops my ERAttachment from opening up a finder file select.
>
> Thanks
> James
> ___
> Do not post
AUP = AjaxUploadClient.
It's provided by wonder.js
--
David LeBer
Codeferous Software
On 2012-02-14, at 11:52 AM, James Cicenia wrote:
> ReferenceError: Can't find variable: AUP
>
>
>
> What is this? It stops my ERAttachment from opening up a finder file select.
>
> Thanks
> James
> ___
Ajax Update Popsicle. It always makes my app freeze.
;-)
I've had the wonder.js ajax variables disappear on me on more than one occasion
when the prototype.js was reloaded by the Ajax On Demand (AOD) thing. I don't
know if that's the problem now, but it's a place to start.
Ramsey
On Feb 14,
ReferenceError: Can't find variable: AUP
What is this? It stops my ERAttachment from opening up a finder file select.
Thanks
James
smime.p7s
Description: S/MIME cryptographic signature
___
Do not post admin requests to the list. They will be ignored
18 matches
Mail list logo
