Hi Birgit,
thanks for reporting this issue.
Yes, you are right that in ISIS-714 changes were made here. Previously we
were (wrongly) storing Blobs as a serialized Java object. As of 1.5 I used
the IsisBlobMapping to explicitly map the three fields of an Isis blob (or
clob), specifically its name
Hi,
I tried to use isis 1.5. instead of 1.4 in our app and ran into some exceptions
because of blobs (we use postgresql 9). Then I tried it with a fresh ToDoApp
and the same thing happened. I removed the comments from the lines for
PostgreSQL Server in persistor.properties, commented out the li
Hi Erik,
In the end, we've decided to keep the Wizard implementation out of the core
framework. It does require 1.6.0-SNAPSHOT, though, unfortunately, since it
builds on the cloneable (=editable) form wizard stuff.
As the above thread says, the add-on is at [3]. At a future date we'll
move it to
Hi Erik,
You need a setter on that property:
public Boolean isForcedonPBX()
{
return getMobileSubscriber().isForcedonPBX();
}
public void setForcedonPBX(Boolean forcedonPBX)
{
getMobileSubscriber().setForcedonPBX(forcedonPBX);
}
It's the presence of the setter that hints to Isis that th
Hi Oscar,
I did what you said but this still doesn't enable the fields in the wicket
viewer. Is that what your proposed solution should do?
My problem is not that my setter is not called after editing the entity. I'm
not able to edit the derived entity (properties) at all. Any other idea?
Erik
1. Once updated Isis to the latest snapshot,
2. try to inject the "WrapperFactory" service,
3. and then replace
> public void modifyForcedonPBX(Boolean forcedonPBX)
> {
> getMobileSubscriber().setForcedonPBX(forcedonPBX);
> }
with
> public void modifyForcedonPBX(Bo
I'm not wrapping any object. This is what I have in my code:
public Boolean isForcedonPBX()
{
return getMobileSubscriber().isForcedonPBX();
}
public void modifyForcedonPBX(Boolean forcedonPBX)
{
getMobileSubscriber().setForcedonPBX(forcedonPB
Hi Dan,
I had some trouble reading my mail (not sending though...) so I missed a lot of
updates on this thread. Thanks for your quick implementation! I will look at it
asap.
I think the wizard should be part of the wicket-viewer but when all add-ons can
be found on one clear website it shouldn
Hi Erik.
Are you invoking the setter within a a wrapped call?
If so, on the modifyXXX instead of "this.wrap(domainObjectB).setXXX"
Try
"this.wrapSkipRules(domainObjectB).setXXX"
This will execute all business logic associated with the property (validate,
modify, etc) without taking into ac
Hi,
I have a class A that has a derived property referencing class B that has some
properties. B's fields are all disabled when editing class A.
Is it possible to modify B's properties by delegating the setters of these
properties to A by using modifyXXX-methods? I tried to do this but the fiel
Hi Dan, Jeroen,
I believe both your methods work for us. I'll think about what option is the
best for this case. Thanks for your replies.
Erik
On 06/10/2014 02:35 PM, Jeroen van der Wal wrote:
Personally I'm not a fan of using the lifecycle events. The pattern
that works best for us is to disa
11 matches
Mail list logo
