Perhaps a bit of a hack, but you could use the Ant replace task to
set the value of your proxied attribute differently depending on the
ant target:
http://ant.apache.org/manual/CoreTasks/replace.html
- Jes
On Mar 1, 2007, at 3:17 AM, Robin Sheat wrote:
On Thursday 01 March 2007 21:44, you wrote:
Proxying is a feature of the Laszlo server... In solo mode, there is
no proxying. So, 'proxied="false"' is somewhat synonymous with Solo
mode.
Yes, however if I use proxied=false, then I have no choice: it must
be a solo
app. This means I can deploy it and it works, which is good. If I
leave out
the proxied=false, when I deploy it, it doesn't work, because it's
looking
for a server.
When you say "I want it to be proxied," what do you mean, exactly?
When debugging the app, I like to run it locally, non-solo, so that
the
debugger works. When doing that, I'd like to not have to change the
proxied
attribute, because I _know_ that I'll forget to change it back, and
stuff
will break.
Perhaps there's another way of accomplishing what you're looking for.
A way to tell the compiler to give me something built for solo mode
would be
ideal :)
Note that up until now I've been creating the deployed file by
viewing it at
localhost:8080/..., and clicking the 'solo' button, then copying
the file to
the server. And that worked great. But now that I'm close to
rolling out a
proper application that uses this, I'm moving towards a proper
change-controlled system, where there are minimal manual steps for
me to
break things, so I'm using the ant script to compile and deploy it.
That's
why this is coming up now :)
--
Robin <[EMAIL PROTECTED]> JabberID:
<[EMAIL PROTECTED]>
Hostes alienigeni me abduxerunt. Qui annus est?
PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C
EB6D
