A follow up question to the committers on this : Is Jun's approach below
something acceptable to do in the meantime ? I was trying to deploy a test
5.1 app to GAE and I ran into the same issue. As he indicated these methods
had emtpy try-catch blocks, removing which is supposed to resolve the issue
Just to add, I have the same problem with Jetty setup behind IIS with AJP13.
Then it might be related to how the filter works. The object
selectedPlan stays to null after selection and refresh.
Anyone any ideas?
On 12.09.2009 21:25, Vangel V. Ajanovski wrote:
Hi,
I have a problem with submit
As I said it was late.
created a union of already assigned values and new values for encoder.
rolfst wrote:
>
> Hi is there a way to use a custom list with entities as a selection and a
> property from another domainobject to set.
> like a onetomany relation.
>
> sorry for my bad english its
If the context needs to be shared, it needs to be exposed to the rest of the
environment in some way.
One option is for the page to implement an interface; components get get the
page (from ComponentResources) and cast it to the interface to obtain the
desired information.
Another option is a per-
What about injecting ComponentEventLinkEncoder and Request to the component and
call #decodePageRenderRequest(request) to get PageRenderRequestParameters.
It contains the activationContext.
DH
http://www.gaonline.com.cn
- Original Message -
From: "chakra"
To:
Sent: Sunday, September 1
Isn't the textfield bound to user.lastName by setting t:value="user.lastName"?
Why there is another 'name'?
And remember to initialize an user instance in the prepareForSubmit event
handler, then T5 set value of the textfield to its property 'lastName'.
void onPrepareForSubmit() {
this.user
yes but in that case i loose the object, so now I m getting
Class com.limonn.pages.Form does not contain a property named 'name' (within
property expression 'name'). Available properties: class,
componentResources, user
because in the class page I have
private User user
it is the object I wa
Agreed. Any number of exceptions can occur when you commit, regardless
of what queries you've run in the same transaction. That's the nature
of multi-user systems, unless of course you want to set the
transaction isolation level to serialize (not usually recommended).
As for using onValida
Hi All,
Is there any easy way of accessing page context from within a component?
I have a page page1 containing components comp1 and comp2
I am accessing the page as http://localhost:8080/page/param1/param2
in Page class ,I can access param1 and param2 by simply writing an
onActivate method.
I
