Hi Katya,
instead of returning the home page using pageWithName in your DA you could
return a WORedirect pointing to it. So after login the user sees a "normal"
component URL and not the DA URL.
jw
Am 23.06.2010 um 21:13 schrieb Katya Yurukova:
> Hi all,
>
> We're using a stateless login pa
Hi all,
We're using a stateless login page that invokes a DA on submit.
In the DA the user input is validated, a new session is created by
calling this.session() and the home page is returned using
this.pageWirhName(...).
It works as expected and no redundant sessions are created, but there
Le 10-06-23 à 13:03, Hugi Thordarson a écrit :
Theodore, check out USTooltip: http://bit.ly/cAonsK
Build available here :
http://services.wocommunity.org:8080/job/USWebObjects/
http://services.wocommunity.org:8080/job/USJava/
:-)
You can add BubbleTooltips.js to your compo
Theodore, check out USTooltip: http://bit.ly/cAonsK
You can add BubbleTooltips.js to your component, set the "linkTitle" attribute
on the AjaxModalDialogOpener to your tooltip text, and then use the method
shown in USTooltip.html to "activate" tooltips for your links.
- hugi
On 23.6.2010,
On Jun 23, 2010, at 8:17 AM, Theodore Petrosky wrote:
> Chuck,
>
> Thanks, googling helped and I feel good about putting in a simple tooltip...
>
> I still can not find an example or any other info on attaching the tooltip to
> the label of an AjaxModalDialogOpener maybe it's so obvious th
Chuck,
Thanks, googling helped and I feel good about putting in a simple tooltip...
I still can not find an example or any other info on attaching the tooltip to
the label of an AjaxModalDialogOpener maybe it's so obvious that I should
be able to figure it out, but I don't get it
--- O
Hi!
I can't wait to have Chuck's book right next to Winnie the pooh! Although I
believe Winnie's plot is a little more intense.
Yours
Miguel Arroz
On 2010/06/23, at 01:21, Chuck Hill wrote:
> I asked my publisher. They would have to do it.I would not want to read
> it on an iPhone,
Thanks guys. We aren't using JavaWebServicesGeneration, but adding the launch
argument took care of it.
-G
On Jun 23, 2010, at 4:23 AM, Hugi Thordarson wrote:
> If your project links to the JavaWebServicesGeneration framework,
> WebServiceAssistant will be launched automatically when you sta
Thanks to all.
Susanne, in fact my background pages should not be stored because I
initialize my dummyContext to deny page storing:
WOContext dummyContext = new WOContext(request) {
public boolean shouldNotStorePageInBacktrackCache() {
If your project links to the JavaWebServicesGeneration framework,
WebServiceAssistant will be launched automatically when you start your app.
You can set -WSAssistantEnabled=false to disable it.
- hugi
On 23.6.2010, at 10:05, David Avendasora wrote:
> Hi George,
>
> There is a launch config
Hi Gennady,
we are doing similar background tasks here. To avoid memory problems we
declared the generated HTML pages not to be stored into the page cache.
This background pages implement the Interface IASUnsaveablePage:
public interface IASUnsaveablePage {
/**
* defines if this pag
Hi George,
There is a launch config (-WOAutoOpenInBrowser) that controls whether or not to
open the browser, but I believe the WebServicesAssistant is web based, so I'm
guessing that maybe somehow your "princiapalClass" property in the
build.properties file, or the "Main class" in your run conf
12 matches
Mail list logo
