Hi Mark,
On Apr 10, 2011, at 4:31 PM, Mark Wardle wrote:
> Writing to a mailing list is always therapeutic, even before anyone
> has a chance to respond.
:-) True, that.
> Now whenever I start hacking URLs like this in WebObjects, I think I'm
> clearly going about something the wrong way. Doe
Hello Ray,
On Apr 8, 2011, at 5:16 PM, naneon.raym...@neuf.fr wrote:
> Hi,
>
> I'm newbie on WebObjects and I have big problem to fetching on joined table.
> Example :
> I have my SQL like that :
A good rule with WebObjects is "If you are thinking about SQL, you are doing it
wrong." There a
Hi Mark,
On Apr 10, 2011, at 3:43 PM, Mark Wardle wrote:
> Hi all,
>
> I'd previously written about this but despite considerable advice and
> help, I didn't make much progress although only just got around to
> taking Chuck Hill's advice overriding Application.displayRequest().
>
> My applica
Writing to a mailing list is always therapeutic, even before anyone
has a chance to respond.
At present, I'm performing just-in-time login and looking at
context().request().uri(). (ie
setDestinationUrl(context().request().uri());
I'm storing that URI and then redirecting after successful login.
Hi all,
I'd previously written about this but despite considerable advice and
help, I didn't make much progress although only just got around to
taking Chuck Hill's advice overriding Application.displayRequest().
My application is working perfectly except when I have multiple
instances. I've also
why not:
WOComponent myPage = pageWithName(ComponentName.class);
.
.
WOResponse response = myPage.generateResponse();
return response;
regards
Amedeo
On 10/apr/2011, at 20.31, Paolo Sommaruga wrote:
> Hi,
>
> I have an application in which inside in a component I need to call a child
> compon
Hi,
I have an application in which inside in a component I need to call a child
component invoked programmatically in the java code of the parent component. I
use
(WOApplication.application ()). responseForComponentWithName(ComponentName,
null