Re: Unserializable exceptions on declaring springs org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor
Sorry, I haven't said that I get unserializable exceptions in Provider
for my table - list.
public class UserDataProvider extends
CustomerAwareSortableDataProvider {
private final User findByExample;
@SpringBean
private UserDao userDao;
public UserDataProvider(User findByExample) {
InjectorHolder.getInjector().inject(this);
this.findByExample = findByExample;
}
I think SpringBean annotation injects proxy for my spring bean and not
a direct reference.
Here is error message:
Hibernate: select count(*) as col_0_0_ from User user0_ limit ?
Hibernate: select user0_.id as id0_, user0_.is_admin as is2_0_,
user0_.full_name as full3_0_, user0_.organization_id as organiza6_0_,
user0_.password as password0_, user0_.username as username0_ from User
user0_
WARN - AutoLinkResolver - Did not find corresponding java
class: net.smart4life.school.web.page.user.IndexPage
INFO - RequestLogger -
time=247,event=BookmarkablePage[net.smart4life.school.web.page.user.SuUserListPage()],response=BookmarkablePage[net.smart4life.school.web.page.user.SuUserListPage()],sessioninfo=user=n/a,sessionsize=5605,sessionstart=Tue
Jan 04 00:43:00 CET
2011,requests=3,totaltime=715,activerequests=0,maxmem=467M,total=162M,used=124M
ERROR - Objects- Error serializing object class
net.smart4life.school.web.page.user.SuUserListPage [object=[Page class
= net.smart4life.school.web.page.user.SuUserListPage, id = 1, version
= 0]]
java.io.NotSerializableException:
org.springframework.dao.support.PersistenceExceptionTranslationInterceptor
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:422)
at org.apache.wicket.Component.writeObject(Component.java:4674)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1346)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1154)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
at java.io.ObjectOutputStream.writeObject0(Ob
Re: Unserializable exceptions on declaring springs org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor
On Mon, Jan 3, 2011 at 4:50 PM, Roman Ilin wrote: > Hi *, > > in wicket 1.4.15 > spring 3.0.5 > hibernate 3.6 > application > > if defined springs PersistenceExceptionTranslationPostProcessor bean I > get Unserializable exceptions in > different spring classes (PersistenceExceptionTranslationInterceptor, > ChainedPersistenceExceptionTranslator, ...) > After looking into spring sources I see that they are really unserializable. > > Is there some workaround to use > PersistenceExceptionTranslationPostProcessor without redefinition of > all unserializable classes? > Or simply nobody uses PersistenceExceptionTranslationPostProcessor? No Wicket components should be directly holding a reference to anything that contains the application context, or any post processors. The error is that something is. The unserializable exception error message is very useful in seeing what is holding on to a reference that it should not. If you can't figure it out, post the whole message (including the part where Wicket draws arrows pointing to the field that isn't serializable) in this thread. -- Jeremy Thomerson http://wickettraining.com Need a CMS for Wicket? Use Brix! http://brixcms.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: quick page model question
On Mon, Jan 3, 2011 at 5:00 PM, gnugrf wrote: > > I'm pretty much a noob, even though I've been slowly working on a project for > about a year so bear with me. I've read "understanding models" a couple > dozen times already and lifecycle, requestcycle, etc. and did a fair amount > of slogging through the mailing list for old posts about "page resfresh" > "page model", etc. and didnt find anything to help me, so forgive my > stupidity.. > > How would i refresh it in the loadabledetachable model (how would the model > know when the page has been refreshed) In a LDM, load() will be called every time that getObject is called *and* the object has not already been loaded. There is a transient instance field in LDM that holds the object once it is loaded. At the end of every request, detach() is called, which nulls out that transient object reference. This means that on the next page view (new request), getObject will presumably be called by something that is using your page model, and in turn, load() will be called again. You don't have to do anything to "refresh" your model. If that is not happening, please show the LDM code you have. -- Jeremy Thomerson http://wickettraining.com Need a CMS for Wicket? Use Brix! http://brixcms.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: quick page model question
I'm pretty much a noob, even though I've been slowly working on a project for
about a year so bear with me. I've read "understanding models" a couple
dozen times already and lifecycle, requestcycle, etc. and did a fair amount
of slogging through the mailing list for old posts about "page resfresh"
"page model", etc. and didnt find anything to help me, so forgive my
stupidity..
How would i refresh it in the loadabledetachable model (how would the model
know when the page has been refreshed)
onbeforerender makes sense to me since its an event, i suppose you are
saying to override that method and i could force the page to reload the
model there. i saw in the javadocs it warned to call super.onbeforerender at
the end.
is there any advantage to either direction?
also as a sanity check my constructors are -->
public ManageClientPage(long id){this(new ClientLDM(id));}
public ManageClientPage(IModel client) { ///code here}
and its being called using id.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/quick-page-model-question-tp3172678p3172797.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Unserializable exceptions on declaring springs org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor
Hi *, in wicket 1.4.15 spring 3.0.5 hibernate 3.6 application if defined springs PersistenceExceptionTranslationPostProcessor bean I get Unserializable exceptions in different spring classes (PersistenceExceptionTranslationInterceptor, ChainedPersistenceExceptionTranslator, ...) After looking into spring sources I see that they are really unserializable. Is there some workaround to use PersistenceExceptionTranslationPostProcessor without redefinition of all unserializable classes? Or simply nobody uses PersistenceExceptionTranslationPostProcessor? Regards Roman - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: quick page model question
You can refresh it in your loadabledetachable model or onbeforerender.. there are some alternatives. ** Martin 2011/1/3 gnugrf : > > how do you get the page model to refresh when a user presses "reload" or F5? > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/quick-page-model-question-tp3172678p3172678.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
quick page model question
how do you get the page model to refresh when a user presses "reload" or F5? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/quick-page-model-question-tp3172678p3172678.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems with continueToOriginalDestination?
On Mon, Jan 3, 2011 at 11:24 AM, Daniel Peters wrote: > Hallo, > > i just wanted to ask if anybody else has problems with > Component.continueToOriginalDestination() at the moment... > For me it only works as expected until 1.4.12 , but all later versions (.13 > to .15) return false and the following code just sends the user to the > application homepage: > > if (!continueToOriginalDestination()) > setResponsePage(Application.get().getHomePage()); > > The only diffrence is the wicket-version and I can reproduce it in my app. > But before I build a quickstart, i wanted to ask here if anybody else > noticed it... I think it's weird that I can't find another bugreport about > it... :/ > > Some basic infos: Browser=FF, Root-Context or not doesn't make a diffrence I haven't personally seen it. Best bet is a JIRA + quickstart. -- Jeremy Thomerson http://wickettraining.com Need a CMS for Wicket? Use Brix! http://brixcms.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Problems with continueToOriginalDestination?
Hallo, i just wanted to ask if anybody else has problems with Component.continueToOriginalDestination() at the moment... For me it only works as expected until 1.4.12 , but all later versions (.13 to .15) return false and the following code just sends the user to the application homepage: if (!continueToOriginalDestination()) setResponsePage(Application.get().getHomePage()); The only diffrence is the wicket-version and I can reproduce it in my app. But before I build a quickstart, i wanted to ask here if anybody else noticed it... I think it's weird that I can't find another bugreport about it... :/ Some basic infos: Browser=FF, Root-Context or not doesn't make a diffrence regards, Daniel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: [ANNOUNCE] Wicket 1.4.15 released
On Mon, Jan 3, 2011 at 4:48 AM, Daniel Peters wrote: > On 27.12.2010 19:15, Daan van Etten wrote: > >> One thing I noticed: the release tag is not (yet?) created in SVN. > > I just noticed that too. > http://svn.apache.org/repos/asf/wicket/releases/wicket-1.4.15/ does not > exist. Thanks Daan and Daniel. I just fixed this. $ svn cp https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.15 \ > https://svn.apache.org/repos/asf/wicket/releases/wicket-1.4.15 \ > -m "tag release 1.4.15" Committed revision 1054650. -- Jeremy Thomerson http://wickettraining.com Need a CMS for Wicket? Use Brix! http://brixcms.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problem AjaxFormChoiceComponentUpdatingBehavior & IE7
Vladimir V. Bychkov wrote: > > Hello. Sorry my bad english. > > Component RadioChoice with AjaxFormChoiceComponentUpdatingBehavior has > different > behavior in Firefox and IE7. Source: > > Adding around RadioGroup in the html file works for me. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problem-AjaxFormChoiceComponentUpdatingBehavior-IE7-tp2330305p3171905.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Display component feedback message once: "safety net" renders them always before
You are testing the behaviors types of reporter, but if two components with
an FeedbackHighlightBehavior report an feedback you break the functionality
A - no message should be rendered twice
On Wed, Dec 29, 2010 at 12:05 PM, joseph.pachod wrote:
>
> Hi Pedro Santos
>
> I hadn't seen your answer, sorry.
>
> In between, I had time again to look into my issue.
>
> Actually, the root of it was about not displaying the feedback message
> twice: once in the general feedback panel and once close from the
> generating
> component.
>
> As such, while helpful, your solution didn't help there.
>
> But I now found this "workaround" for this:
> add(new FeedbackPanel("plainFeedback", new IFeedbackMessageFilter()
>{
>
>@Override
>public boolean accept(final FeedbackMessage message)
>{
>List behaviors =
> message.getReporter().getBehaviors();
>for (IBehavior behavior : behaviors)
>{
>if (behavior instanceof FeedbackHighlightBehavior)
>{
>return false;
>}
>}
>return true;
>}
>}));
>
> => the feedback panel doesn't display the message twice :)
>
> I have yet to put this change in production, where maybe I would have to do
> extra check (like to check that the reporter component is effectively
> visible in order to be sure of the feedback message display), but at least
> I've found a way to go.
>
> :)
>
> ++
> joseph
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Display-component-feedback-message-once-safety-net-renders-them-always-before-tp3068969p3167130.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Pedro Henrique Oliveira dos Santos
Re: Display component feedback message once: "safety net" renders them always before
Hi Joseph, I didn't understood your solution
If have an page with 3 form components and 5 feedback panels: 1 for each
form component, 1 for the form, and the last one for the page. And I want
feedback messages address to form components to be presented only by the
correspondent feedback panel.
I would create:
FeedbackPanel fp1 = new
ComponentFeedbackPanel("formComponent1FeedbackPanel", formComponent1);
FeedbackPanel fp2 = new
ComponentFeedbackPanel("formComponent2FeedbackPanel", formComponent2);
FeedbackPanel fp3 = new
ComponentFeedbackPanel("formComponent3FeedbackPanel", formComponent3);
FeedbackPanel fp4 = new ComponentFeedbackPanel("formFeedbackPanel", form);
FeedbackPanel fp5 = new ComponentFeedbackPanel("pageFeedbackPanel", page);
formComponent1.info("some message") register an message that will only be
presented by fp1
form.error("some message") register an message that will only be presented
by the form
On Wed, Dec 29, 2010 at 12:05 PM, joseph.pachod wrote:
>
> Hi Pedro Santos
>
> I hadn't seen your answer, sorry.
>
> In between, I had time again to look into my issue.
>
> Actually, the root of it was about not displaying the feedback message
> twice: once in the general feedback panel and once close from the
> generating
> component.
>
> As such, while helpful, your solution didn't help there.
>
> But I now found this "workaround" for this:
> add(new FeedbackPanel("plainFeedback", new IFeedbackMessageFilter()
>{
>
>@Override
>public boolean accept(final FeedbackMessage message)
>{
>List behaviors =
> message.getReporter().getBehaviors();
>for (IBehavior behavior : behaviors)
>{
>if (behavior instanceof FeedbackHighlightBehavior)
>{
>return false;
>}
>}
>return true;
>}
>}));
>
> => the feedback panel doesn't display the message twice :)
>
> I have yet to put this change in production, where maybe I would have to do
> extra check (like to check that the reporter component is effectively
> visible in order to be sure of the feedback message display), but at least
> I've found a way to go.
>
> :)
>
> ++
> joseph
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Display-component-feedback-message-once-safety-net-renders-them-always-before-tp3068969p3167130.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Pedro Henrique Oliveira dos Santos
Re: [ANNOUNCE] Wicket 1.4.15 released
On 27.12.2010 19:15, Daan van Etten wrote: One thing I noticed: the release tag is not (yet?) created in SVN. I just noticed that too. http://svn.apache.org/repos/asf/wicket/releases/wicket-1.4.15/ does not exist. regards, Daniel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: OrderByBorder Markup
public static class CssModifier extends AttributeModifier
This seems to be the problem.
File a ticket in Jira. With quickstart will be easier for us to reproduce it
and fix it faster ;-)
In the meantime you can workaround the problem by calling:
orderByBorder.add(new AttributeAppender("class", true",
Model.of("MandateEntityTypeField"), " ")).
On Mon, Jan 3, 2011 at 9:29 AM, Peter Diefenthaeler wrote:
> Hi,
>
> I'm using the OrderByBorder feature and it works well for rows
> without stylesheet classes.
> Unfortunately it fails if the already has a stylesheet class:
>
>
>
>
>
> Wicket replaces the class="MandateEntityTypeField"with the
> class="wicket_orderUp" and my field width properties will be lost.
> It would be better, if Wicket would add his style class instead of
> replacing it ( class="MandateEntityTypeField,wicket_orderUp")
>
> Is this an error or is it my fault?
>
> Thanks, Peter
>
OrderByBorder Markup
Hi, I'm using the OrderByBorder feature and it works well for rows without stylesheet classes. Unfortunately it fails if the already has a stylesheet class: Wicket replaces the class="MandateEntityTypeField"with the class="wicket_orderUp" and my field width properties will be lost. It would be better, if Wicket would add his style class instead of replacing it ( class="MandateEntityTypeField,wicket_orderUp") Is this an error or is it my fault? Thanks, Peter
