Re: Attributes integrity and crossorigin for UrlResourceReference
Hi Martin, I am watching https://issues.apache.org/jira/browse/WICKET-6321 now and will think about it, if I have an inspiration, I will suggest it ;-) Dieter Tremel Am 28.02.2018 um 13:24 schrieb Martin Grigorov: > Hi Dieter, > > There is a ticket in JIRA about this. > Pull requests are welcome! :-) > > Martin Grigorov > Wicket Training and Consulting > Looking for a remote position with Wicket ? Contact me! > https://twitter.com/mtgrigorov > > > On Wed, Feb 28, 2018 at 8:23 AM, Dieter Tremel <tre...@tremel-computer.de> > wrote: > >> In my code an interface IBootstrapResourceReferencer abstracts getting >> resource references for Bootstrap 4. Three implementations give >> package-, webjar, and CDN resources. >> >> CDN resources use UrlResourceReferences. Is it possible to add the >> integrity and crossorigin attributes to the rendered header items as >> given on http://getbootstrap.com/docs/4.0/getting-started/introduction/? >> >> Thank you for any answer >> Dieter Tremel >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > -- Tremel Computerhttp://www.tremel-computer.de Dieter Tremel mailto:tre...@tremel-computer.de Rebenring 16 Tel +49 871 9357080 84032 Altdorf Fax +49 871 9357081 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Attributes integrity and crossorigin for UrlResourceReference
In my code an interface IBootstrapResourceReferencer abstracts getting resource references for Bootstrap 4. Three implementations give package-, webjar, and CDN resources. CDN resources use UrlResourceReferences. Is it possible to add the integrity and crossorigin attributes to the rendered header items as given on http://getbootstrap.com/docs/4.0/getting-started/introduction/? Thank you for any answer Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-guice and recursive injection of non serializable JPA2 objects
Am 17.06.2016 um 12:58 schrieb Bas Gooren: > Although I do wonder why you are trying to cache JPA objects by yourself - > you could simply plug in a second level cache to your JPA provider. Then it > will cache transparently. Didn't know, activated JPA second level cache, works well, dropped my Caching implementation. ;-) In German I say "Wissen ist Macht, wir wissen nichts, macht nichts" Thank You Dieter -- Tremel Computerhttp://www.tremel-computer.de Dieter Tremel mailto:tre...@tremel-computer.de Rebenring 16 Tel +49 871 9357080 84032 Altdorf Fax +49 871 9357081 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-guice and recursive injection of non serializable JPA2 objects
Hello Martin,
I tried this to learn it, but didn't find it.
I put a breakpoint at org.apache.wicket.serialize.java.JavaSerializer
SerializationCheckerObjectOutputStream#writeObjectOverride line 260 and
277 and looked at the variables content.
The obj was the complete page PersonenTable and I had to look at all the
children in the page hierarchy. Not straight forward to find.
Did I miss something?
Thanks Dieter
Am 17.06.2016 um 11:56 schrieb Martin Grigorov:
> Hi Dieter,
>
> It is quite easy to debug such issues by putting a breakpoint at line where
> the exception is being thrown.
> Once you have the debugger stopped there you could click on the stack
> methods to see what was the parent object of the currently failing one.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Fri, Jun 17, 2016 at 11:46 AM, Dieter Tremel <tre...@tremel-computer.de>
> wrote:
>
>> Hello Bas,
>>
>> first of all let me thank you and Martin for your great support and the
>> helpful thoughts and examples :-)
>>
>> I am using wicket 7.30, the use of onBefore() is an old pattern I have
>> been used to, changed it now to
>> @Override
>> protected void onInitialize() {
>> super.onInitialize();
>> initMarkup();
>> }
>> on all pages.
>>
>> The last days I spent a lot of time in analyzing, debugging, some
>> refactoring, searching. But I didn't find the culprit yet. :-(
>>
>> Your example is useful, I read some similar blogpost about outside final
>> vars in methods of anonymous inner classes, but had no match in my code
>> so far.
>>
>> I will do some more exhaustive search and report, if I solved the problem.
>>
>> Thank You
>> Dieter
>>
>> Am 16.06.2016 um 16:32 schrieb Bas Gooren:
>>> Hi Dieter,
>>>
>>>
>>> Which version of wicket are you using? (I ask since I see you are using
>>> onBeforeRender() to initialize your components, while since wicket 1.5
>>> there is onInitialize() for that in each component).
>>>
>>>
>>> For as far as I can see there are no references to your dao in the gist
>>> you provided; However, since it is serialized somewhere in the component
>>> tree, it could be in one of the smaller components used in your
>>> PersonenTable page.
>>>
>>> In any case, your page (or a component inside it) has a reference to
>>> your dao.
>>>
>>>
>>> Since I’ve seen this a lot when I started using wicket, please check if
>>> you are referencing your dao somewhere inside an anonymous inner class /
>>> component.
>>>
>>>
>>> E.g.:
>>>
>>>
>>> public Component createMyComponent(String id) {
>>>
>>> DAO dao = getDaoFromPageOrElsewhere();
>>>
>>> return new AjaxLink(id) {
>>>
>>> public void onClick(AjaxRequestTarget target) {
>>>
>>> // This is where an instance of DAO will get serialized into the
>>> component tree!
>>>
>>> dao.performAction();
>>>
>>> }
>>>
>>> }
>>>
>>> }
>>>
>>>
>>> Rewrite such code (if you have it) to look up the DAO reference at the
>>> time you actually need it:
>>>
>>>
>>> public void onClick(AjaxRequestTarget target) {
>>>
>>> DAO dao = getDaoFromPageOrElsewhere();
>>>
>>> dao.performAction();
>>>
>>> }
>>>
>>>
>>> My guess is that you’ll find the culprit by simply looking at all places
>>> in your code where you use the PersonenDao.
>>>
>>>
>>> Met vriendelijke groet,
>>> Kind regards,
>>>
>>> Bas Gooren
>>>
>>> Op 15 juni 2016 bij 16:25:25, Dieter Tremel (tre...@tremel-computer.de
>>> <mailto:tre...@tremel-computer.de>) schreef:
>>>
>>>> Hello Martin,
>>>>
>>>> it is:
>>>>
>>>> personenProvider = (com.sun.proxy.$Proxy24)
>>>> org.apache.wicket.proxy.LazyInitProxyFactory$JdkHandler@6eb3b9ea
>>>>
>>>> wrapInProxies is true
>>>>
>>>> I added a SignIn mechanism, SignInSession uses PersonenDao too to
>>>> authorize in the database. But I checked not to have any references to
>>>> it, that could be serialized. I added more of this this part to the
>> gist:
>>>>
>>>> https://gist.github.com/tremel/dd9bfa252282b5853d6d464feccaad2
Re: wicket-guice and recursive injection of non serializable JPA2 objects
Hello,
I think I have found it:
In my AbstractProvider superclass I implemented:
@Override
public IModel model(E object) {
return new JPAEntityModel<>((E) object);
}
PersonenTable uses a CachingProvider, a subclass of AbstractProvider
which overwrites
@Override
public IModel model(E entity) {
return new AbiProviderModel(this, entity);
}
which is implemented as:
public class AbiProviderModel extends
LoadableDetachableModel {
private static final long serialVersionUID = 1L;
private final IAbiDataProvider provider;
private final Object id;
public AbiProviderModel(IAbiDataProvider provider, E instance) {
super(instance);
this.provider = provider;
this.id = instance.getUniqueId();
}
public AbiProviderModel(IAbiDataProvider provider, Object id) {
super();
this.provider = provider;
this.id = id;
}
@Override
protected E load() {
return provider.find(id);
}
}
Here the embedded provider is the problem!
I replaced this with a JPAEntityModel again, and it works without
serialization error. I am unburdened but ashamed it took so long to find.
But this does not make use of the cache. Perhaps I will refactor my code
not to make the provider holding the cache, but the dao itself.
Thank You for your help!
Dieter
Am 16.06.2016 um 16:32 schrieb Bas Gooren:
> Hi Dieter,
>
>
> Which version of wicket are you using? (I ask since I see you are using
> onBeforeRender() to initialize your components, while since wicket 1.5
> there is onInitialize() for that in each component).
>
>
> For as far as I can see there are no references to your dao in the gist you
> provided; However, since it is serialized somewhere in the component tree,
> it could be in one of the smaller components used in your PersonenTable
> page.
>
> In any case, your page (or a component inside it) has a reference to your
> dao.
>
>
> Since I’ve seen this a lot when I started using wicket, please check if you
> are referencing your dao somewhere inside an anonymous inner class /
> component.
>
>
> E.g.:
>
>
> public Component createMyComponent(String id) {
>
> DAO dao = getDaoFromPageOrElsewhere();
>
> return new AjaxLink(id) {
>
> public void onClick(AjaxRequestTarget target) {
>
> // This is where an instance of DAO will get serialized into the component
> tree!
>
> dao.performAction();
>
> }
>
> }
>
> }
>
>
> Rewrite such code (if you have it) to look up the DAO reference at the time
> you actually need it:
>
>
> public void onClick(AjaxRequestTarget target) {
>
> DAO dao = getDaoFromPageOrElsewhere();
>
> dao.performAction();
>
> }
>
>
> My guess is that you’ll find the culprit by simply looking at all places in
> your code where you use the PersonenDao.
>
>
> Met vriendelijke groet,
> Kind regards,
>
> Bas Gooren
>
> Op 15 juni 2016 bij 16:25:25, Dieter Tremel (tre...@tremel-computer.de)
> schreef:
>
> Hello Martin,
>
> it is:
>
> personenProvider = (com.sun.proxy.$Proxy24)
> org.apache.wicket.proxy.LazyInitProxyFactory$JdkHandler@6eb3b9ea
>
> wrapInProxies is true
>
> I added a SignIn mechanism, SignInSession uses PersonenDao too to
> authorize in the database. But I checked not to have any references to
> it, that could be serialized. I added more of this this part to the gist:
>
> https://gist.github.com/tremel/dd9bfa252282b5853d6d464feccaad29
>
> Dieter
>
> Am 15.06.2016 um 15:00 schrieb Martin Grigorov:
>> Hi,
>>
>> Put a breakpoint at PersonenTable constructor and see what is the type of
> '
>> personenProvider'.
>> It must be JDK Proxy instance.
>> If it is not then something wrong is going on.
>>
>>
> org.apache.wicket.guice.GuiceComponentInjector#GuiceComponentInjector(org.apache.wicket.Application,
>
>> com.google.inject.Injector, boolean) - the last parameter here is
>> 'wrapInProxies'. It must be 'true'.
>>
>> Martin Grigorov
>> Wicket Training and Consulting
>> https://twitter.com/mtgrigorov
>>
>> On Wed, Jun 15, 2016 at 2:18 PM, Dieter Tremel <tre...@tremel-computer.de>
>
>> wrote:
>>
>>> Hi Bas,
>>>
>>> I put it in http://pastie.org/private/19zeomb8uy1beb1gfjegq
>>>
>>> I fear it is not really useful, since it starts with
>>>
>>> org.apache.wicket.WicketRuntimeException: A problem occurred while
>>> trying to collect debug information about not serializable object
>>>
>>> Dieter
>>>
>>> Am 15.06.2016 um 13:39 schrieb Bas Gooren:
>>>> Hi Dieter
Re: wicket-guice and recursive injection of non serializable JPA2 objects
Hello Bas,
first of all let me thank you and Martin for your great support and the
helpful thoughts and examples :-)
I am using wicket 7.30, the use of onBefore() is an old pattern I have
been used to, changed it now to
@Override
protected void onInitialize() {
super.onInitialize();
initMarkup();
}
on all pages.
The last days I spent a lot of time in analyzing, debugging, some
refactoring, searching. But I didn't find the culprit yet. :-(
Your example is useful, I read some similar blogpost about outside final
vars in methods of anonymous inner classes, but had no match in my code
so far.
I will do some more exhaustive search and report, if I solved the problem.
Thank You
Dieter
Am 16.06.2016 um 16:32 schrieb Bas Gooren:
> Hi Dieter,
>
>
> Which version of wicket are you using? (I ask since I see you are using
> onBeforeRender() to initialize your components, while since wicket 1.5
> there is onInitialize() for that in each component).
>
>
> For as far as I can see there are no references to your dao in the gist
> you provided; However, since it is serialized somewhere in the component
> tree, it could be in one of the smaller components used in your
> PersonenTable page.
>
> In any case, your page (or a component inside it) has a reference to
> your dao.
>
>
> Since I’ve seen this a lot when I started using wicket, please check if
> you are referencing your dao somewhere inside an anonymous inner class /
> component.
>
>
> E.g.:
>
>
> public Component createMyComponent(String id) {
>
> DAO dao = getDaoFromPageOrElsewhere();
>
> return new AjaxLink(id) {
>
> public void onClick(AjaxRequestTarget target) {
>
> // This is where an instance of DAO will get serialized into the
> component tree!
>
> dao.performAction();
>
> }
>
> }
>
> }
>
>
> Rewrite such code (if you have it) to look up the DAO reference at the
> time you actually need it:
>
>
> public void onClick(AjaxRequestTarget target) {
>
> DAO dao = getDaoFromPageOrElsewhere();
>
> dao.performAction();
>
> }
>
>
> My guess is that you’ll find the culprit by simply looking at all places
> in your code where you use the PersonenDao.
>
>
> Met vriendelijke groet,
> Kind regards,
>
> Bas Gooren
>
> Op 15 juni 2016 bij 16:25:25, Dieter Tremel (tre...@tremel-computer.de
> <mailto:tre...@tremel-computer.de>) schreef:
>
>> Hello Martin,
>>
>> it is:
>>
>> personenProvider = (com.sun.proxy.$Proxy24)
>> org.apache.wicket.proxy.LazyInitProxyFactory$JdkHandler@6eb3b9ea
>>
>> wrapInProxies is true
>>
>> I added a SignIn mechanism, SignInSession uses PersonenDao too to
>> authorize in the database. But I checked not to have any references to
>> it, that could be serialized. I added more of this this part to the gist:
>>
>> https://gist.github.com/tremel/dd9bfa252282b5853d6d464feccaad29
>>
>> Dieter
>>
>> Am 15.06.2016 um 15:00 schrieb Martin Grigorov:
>> > Hi,
>> >
>> > Put a breakpoint at PersonenTable constructor and see what is the type of '
>> > personenProvider'.
>> > It must be JDK Proxy instance.
>> > If it is not then something wrong is going on.
>> >
>> > org.apache.wicket.guice.GuiceComponentInjector#GuiceComponentInjector(org.apache.wicket.Application,
>> > com.google.inject.Injector, boolean) - the last parameter here is
>> > 'wrapInProxies'. It must be 'true'.
>> >
>> > Martin Grigorov
>> > Wicket Training and Consulting
>> > https://twitter.com/mtgrigorov
>> >
>> > On Wed, Jun 15, 2016 at 2:18 PM, Dieter Tremel <tre...@tremel-computer.de
>> > <mailto:tre...@tremel-computer.de>>
>> > wrote:
>> >
>> >> Hi Bas,
>> >>
>> >> I put it in http://pastie.org/private/19zeomb8uy1beb1gfjegq
>> >>
>> >> I fear it is not really useful, since it starts with
>> >>
>> >> org.apache.wicket.WicketRuntimeException: A problem occurred while
>> >> trying to collect debug information about not serializable object
>> >>
>> >> Dieter
>> >>
>> >> Am 15.06.2016 um 13:39 schrieb Bas Gooren:
>> >>> Hi Dieter,
>> >>>
>> >>> Can you share the stack trace of the serialization checker error?
>> >>> Normally it points out where in the hierarchy it found a
>> >>> non-serializable object.
>> >>> My first guess is that you are referencing the dao class somewhe
Re: wicket-guice and recursive injection of non serializable JPA2 objects
Hello Martin,
it is:
personenProvider = (com.sun.proxy.$Proxy24)
org.apache.wicket.proxy.LazyInitProxyFactory$JdkHandler@6eb3b9ea
wrapInProxies is true
I added a SignIn mechanism, SignInSession uses PersonenDao too to
authorize in the database. But I checked not to have any references to
it, that could be serialized. I added more of this this part to the gist:
https://gist.github.com/tremel/dd9bfa252282b5853d6d464feccaad29
Dieter
Am 15.06.2016 um 15:00 schrieb Martin Grigorov:
> Hi,
>
> Put a breakpoint at PersonenTable constructor and see what is the type of '
> personenProvider'.
> It must be JDK Proxy instance.
> If it is not then something wrong is going on.
>
> org.apache.wicket.guice.GuiceComponentInjector#GuiceComponentInjector(org.apache.wicket.Application,
> com.google.inject.Injector, boolean) - the last parameter here is
> 'wrapInProxies'. It must be 'true'.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Wed, Jun 15, 2016 at 2:18 PM, Dieter Tremel <tre...@tremel-computer.de>
> wrote:
>
>> Hi Bas,
>>
>> I put it in http://pastie.org/private/19zeomb8uy1beb1gfjegq
>>
>> I fear it is not really useful, since it starts with
>>
>> org.apache.wicket.WicketRuntimeException: A problem occurred while
>> trying to collect debug information about not serializable object
>>
>> Dieter
>>
>> Am 15.06.2016 um 13:39 schrieb Bas Gooren:
>>> Hi Dieter,
>>>
>>> Can you share the stack trace of the serialization checker error?
>>> Normally it points out where in the hierarchy it found a
>>> non-serializable object.
>>> My first guess is that you are referencing the dao class somewhere
>>> directly from your page. The stack trace will prove me right or wrong :-)
>>>
>>> Met vriendelijke groet,
>>> Kind regards,
>>>
>>> Bas Gooren
>>>
>>> Op 15 juni 2016 bij 13:29:24, Dieter Tremel (tre...@tremel-computer.de
>>> <mailto:tre...@tremel-computer.de>) schreef:
>>>
>>>> Hello Bas,
>>>>
>>>> I try to cut small pieces of the code, please tell me if you want to see
>>>> more.
>>>>
>>>> First the error:
>>>>
>>>> 12:59:03.919 [http-nio-8084-exec-6] WARN
>>>> o.a.w.c.u.o.c.CheckingObjectOutputStream - error delegating to
>>>> writeObject :
>>>>
>> de.tremel_computer.abi81.datahandling.PersonenDao$$EnhancerByGuice$$4769627f,
>>>>
>>>> path: /children
>>>> 12:59:03.925 [http-nio-8084-exec-6] ERROR
>>>> o.a.w.serialize.java.JavaSerializer - Error serializing object class
>>>> de.tremel_computer.abi81.pages.PersonenTable [object=[Page class =
>>>> de.tremel_computer.abi81.pages.PersonenTable, id = 1, render count = 1]]
>>>> org.apache.wicket.WicketRuntimeException: A problem occurred while
>>>> trying to collect debug information about not serializable object
>>>> at
>>>>
>> org.apache.wicket.serialize.java.JavaSerializer$SerializationCheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:278)
>>>>
>>>>
>>>>
>>>>
>>>> public class PersonenTable extends BasePage {
>>>>
>>>> @Inject
>>>> private ICachingAbiDataProvider personenProvider;
>>>> ...
>>>> }
>>>>
>>>> public class AbstractProvider extends
>>>> SortableDataProvider<E, String> implements IAbiDataProvider {
>>>>
>>>> @Inject
>>>> private ReadOnlyDao dao;
>>>> ...
>>>> }
>>>>
>>>> public abstract class JPAReadOnlyDao implements
>>>> ReadOnlyDao {
>>>>
>>>> private Provider emProvider;
>>>> private final Class entityClass;
>>>>
>>>> public JPAReadOnlyDao(Class entityClass) {
>>>> this.entityClass = entityClass;
>>>> }
>>>> ...
>>>>
>>>> @Inject
>>>> public void setEntityManagerProvider(Provider
>>>> emProvider) {
>>>> this.emProvider = emProvider;
>>>> }
>>>> ...
>>>> }
>>>>
>>>> public class Abi81GuiceModule extends AbstractModule {
>>>>
>>>> @Override
>>>> protected void configure() {
>>>> bind(PersistServiceInitializer.class).asEagerSingleton();
>>>> bind(new TypeLiteral<ReadOnlyDao>()
>>>> {}).to(AbiartikelDao.class);
>>
Re: wicket-guice and recursive injection of non serializable JPA2 objects
Hi Bas,
I put it in http://pastie.org/private/19zeomb8uy1beb1gfjegq
I fear it is not really useful, since it starts with
org.apache.wicket.WicketRuntimeException: A problem occurred while
trying to collect debug information about not serializable object
Dieter
Am 15.06.2016 um 13:39 schrieb Bas Gooren:
> Hi Dieter,
>
> Can you share the stack trace of the serialization checker error?
> Normally it points out where in the hierarchy it found a
> non-serializable object.
> My first guess is that you are referencing the dao class somewhere
> directly from your page. The stack trace will prove me right or wrong :-)
>
> Met vriendelijke groet,
> Kind regards,
>
> Bas Gooren
>
> Op 15 juni 2016 bij 13:29:24, Dieter Tremel (tre...@tremel-computer.de
> <mailto:tre...@tremel-computer.de>) schreef:
>
>> Hello Bas,
>>
>> I try to cut small pieces of the code, please tell me if you want to see
>> more.
>>
>> First the error:
>>
>> 12:59:03.919 [http-nio-8084-exec-6] WARN
>> o.a.w.c.u.o.c.CheckingObjectOutputStream - error delegating to
>> writeObject :
>> de.tremel_computer.abi81.datahandling.PersonenDao$$EnhancerByGuice$$4769627f,
>>
>> path: /children
>> 12:59:03.925 [http-nio-8084-exec-6] ERROR
>> o.a.w.serialize.java.JavaSerializer - Error serializing object class
>> de.tremel_computer.abi81.pages.PersonenTable [object=[Page class =
>> de.tremel_computer.abi81.pages.PersonenTable, id = 1, render count = 1]]
>> org.apache.wicket.WicketRuntimeException: A problem occurred while
>> trying to collect debug information about not serializable object
>> at
>> org.apache.wicket.serialize.java.JavaSerializer$SerializationCheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:278)
>>
>>
>>
>>
>> public class PersonenTable extends BasePage {
>>
>> @Inject
>> private ICachingAbiDataProvider personenProvider;
>> ...
>> }
>>
>> public class AbstractProvider extends
>> SortableDataProvider<E, String> implements IAbiDataProvider {
>>
>> @Inject
>> private ReadOnlyDao dao;
>> ...
>> }
>>
>> public abstract class JPAReadOnlyDao implements
>> ReadOnlyDao {
>>
>> private Provider emProvider;
>> private final Class entityClass;
>>
>> public JPAReadOnlyDao(Class entityClass) {
>> this.entityClass = entityClass;
>> }
>> ...
>>
>> @Inject
>> public void setEntityManagerProvider(Provider
>> emProvider) {
>> this.emProvider = emProvider;
>> }
>> ...
>> }
>>
>> public class Abi81GuiceModule extends AbstractModule {
>>
>> @Override
>> protected void configure() {
>> bind(PersistServiceInitializer.class).asEagerSingleton();
>> bind(new TypeLiteral<ReadOnlyDao>()
>> {}).to(AbiartikelDao.class);
>> bind(new TypeLiteral<ReadOnlyDao>()
>> {}).to(PersonenDao.class);
>> bind(new TypeLiteral<WritingDao>()
>> {}).to(PersonenDao.class);
>> bind(new TypeLiteral<ICachingAbiDataProvider>()
>> {}).to(CachingAbiartikelProvider.class);
>> bind(new TypeLiteral<ICachingAbiDataProvider>()
>> {}).to(CachingPersonenProvider.class);
>> }
>> }
>>
>> BasePage creates a SignInPanel that links to a SignIn-Page, that uses
>> methods of SignInSession, that makes use a PersonenDao in only in a
>> method.
>>
>> I also made a gist:
>> https://gist.github.com/tremel/dd9bfa252282b5853d6d464feccaad29
>>
>> Thank you
>> Dieter
>>
>>
>> Am 15.06.2016 um 08:17 schrieb Bas Gooren:
>> > Dieter,
>> >
>> > Since the data provider is inject as a proxy, only the proxy should be
>> > serialized. On deserialization it should look up the actual data
>> > provider again.
>> >
>> > Can you share some code so we can see how you set things up? What you
>> > are trying is something that should work out of the box - it does for
>> > us.
>> >
>> > Bas
>> >
>> > Verstuurd vanaf mijn iPhone
>> >
>> >> Op 15 jun. 2016 om 07:53 heeft Dieter Tremel <tre...@tremel-computer.de>
>> >> het volgende geschreven:
>> >>
>> >> Hallo wicket-user,
>> >>
>> >> IMHO combining wicket with non serializable objects is a challenging
>> >> topic.
>> >>
>> >> On a page I have a DataProvider, that is injected by wicked-guice.
>> >> Inside this provider an injected dao is used for fetching the data.
>> >> Inside the
Re: wicket-guice and recursive injection of non serializable JPA2 objects
Hello Bas,
I try to cut small pieces of the code, please tell me if you want to see
more.
First the error:
12:59:03.919 [http-nio-8084-exec-6] WARN
o.a.w.c.u.o.c.CheckingObjectOutputStream - error delegating to
writeObject :
de.tremel_computer.abi81.datahandling.PersonenDao$$EnhancerByGuice$$4769627f,
path: /children
12:59:03.925 [http-nio-8084-exec-6] ERROR
o.a.w.serialize.java.JavaSerializer - Error serializing object class
de.tremel_computer.abi81.pages.PersonenTable [object=[Page class =
de.tremel_computer.abi81.pages.PersonenTable, id = 1, render count = 1]]
org.apache.wicket.WicketRuntimeException: A problem occurred while
trying to collect debug information about not serializable object
at
org.apache.wicket.serialize.java.JavaSerializer$SerializationCheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:278)
public class PersonenTable extends BasePage {
@Inject
private ICachingAbiDataProvider personenProvider;
...
}
public class AbstractProvider extends
SortableDataProvider<E, String> implements IAbiDataProvider {
@Inject
private ReadOnlyDao dao;
...
}
public abstract class JPAReadOnlyDao implements
ReadOnlyDao {
private Provider emProvider;
private final Class entityClass;
public JPAReadOnlyDao(Class entityClass) {
this.entityClass = entityClass;
}
...
@Inject
public void setEntityManagerProvider(Provider
emProvider) {
this.emProvider = emProvider;
}
...
}
public class Abi81GuiceModule extends AbstractModule {
@Override
protected void configure() {
bind(PersistServiceInitializer.class).asEagerSingleton();
bind(new TypeLiteral<ReadOnlyDao>()
{}).to(AbiartikelDao.class);
bind(new TypeLiteral<ReadOnlyDao>()
{}).to(PersonenDao.class);
bind(new TypeLiteral<WritingDao>()
{}).to(PersonenDao.class);
bind(new TypeLiteral<ICachingAbiDataProvider>()
{}).to(CachingAbiartikelProvider.class);
bind(new TypeLiteral<ICachingAbiDataProvider>()
{}).to(CachingPersonenProvider.class);
}
}
BasePage creates a SignInPanel that links to a SignIn-Page, that uses
methods of SignInSession, that makes use a PersonenDao in only in a method.
I also made a gist:
https://gist.github.com/tremel/dd9bfa252282b5853d6d464feccaad29
Thank you
Dieter
Am 15.06.2016 um 08:17 schrieb Bas Gooren:
> Dieter,
>
> Since the data provider is inject as a proxy, only the proxy should be
> serialized. On deserialization it should look up the actual data
> provider again.
>
> Can you share some code so we can see how you set things up? What you
> are trying is something that should work out of the box - it does for
> us.
>
> Bas
>
> Verstuurd vanaf mijn iPhone
>
>> Op 15 jun. 2016 om 07:53 heeft Dieter Tremel <tre...@tremel-computer.de> het
>> volgende geschreven:
>>
>> Hallo wicket-user,
>>
>> IMHO combining wicket with non serializable objects is a challenging topic.
>>
>> On a page I have a DataProvider, that is injected by wicked-guice.
>> Inside this provider an injected dao is used for fetching the data.
>> Inside the dao a provider for a JPA2 entity manager (EclipseLink) is
>> injected.
>>
>> Page -> DataProvider -> Dao -> Provider
>>
>> Seems to be useful, but since the page is stateful I recognized the non
>> serializeable error for the dao at the end of page rendering.
>>
>> After some code studies I think wicket-guice is only using a proxy for
>> the DataProvider, the second second and third level of injection is done
>> only by guice, not handled by wicket-guice and wicket-ioc. This causes
>> serializable error for dao. Am I right here? wicket-guice is not as
>> useful as it could be, if it would not be restricted to the fields in
>> the first level. Setter injection is another topic. The name-pair lets
>> associate a transparent combination of the two technologies, but it isn't.
>>
>> At the moment I have no solution for this.
>> I still struggle with the right architecture fore using generic JPA2
>> provided entities on my pages. The only idea so far is not to use guice
>> and use the application as a link to the non serializable JPA objects
>> and using detachable models to handle the on pages.
>>
>> Any hints for my confused mind welcome. Thanks!
>>
>> Dieter Tremel
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
wicket-guice and recursive injection of non serializable JPA2 objects
Hallo wicket-user, IMHO combining wicket with non serializable objects is a challenging topic. On a page I have a DataProvider, that is injected by wicked-guice. Inside this provider an injected dao is used for fetching the data. Inside the dao a provider for a JPA2 entity manager (EclipseLink) is injected. Page -> DataProvider -> Dao -> Provider Seems to be useful, but since the page is stateful I recognized the non serializeable error for the dao at the end of page rendering. After some code studies I think wicket-guice is only using a proxy for the DataProvider, the second second and third level of injection is done only by guice, not handled by wicket-guice and wicket-ioc. This causes serializable error for dao. Am I right here? wicket-guice is not as useful as it could be, if it would not be restricted to the fields in the first level. Setter injection is another topic. The name-pair lets associate a transparent combination of the two technologies, but it isn't. At the moment I have no solution for this. I still struggle with the right architecture fore using generic JPA2 provided entities on my pages. The only idea so far is not to use guice and use the application as a link to the non serializable JPA objects and using detachable models to handle the on pages. Any hints for my confused mind welcome. Thanks! Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Resolution of url() in ContextRelativeResourceReference
For your information: I implemented a better solution with
http://www.webjars.org today.
>
> de.agilecoders.wicket.webjars
> wicket-webjars
> 0.5.3
>
>
> org.webjars
> bootstrap
> 3.3.5
>
If WebjarsCssResourceReference is used, the problem of the Glyphicons
fonts is solved.
Dieter
Am 07.10.2015 um 10:12 schrieb Dieter Tremel:
> Hello list,
>
> Using Bootstrap 3.3.5 I want to include the stylesheet, js and font
> resources myself, not using wicket-bootstrap. To have a dependency to
> wicket's jquery version I decided to move resource handling from html to
> java and to use ContextRelativeResourceReference like this:
>
>> ContextRelativeResourceReference bootstrapCSS = new
>> ContextRelativeResourceReference("css/bootstrap.css");
>> response.render(CssHeaderItem.forReference(bootstrapCSS));
>> ...
>
> When using gylphicons the icons are not rendered correctly, a 404 error
> is given for the fonts and the log says
>> 09:45:37.976 [http-nio-8084-exec-6] WARN
>> o.a.w.r.r.ResourceReferenceRegistry - A ResourceReference wont be created
>> for a resource with key [scope: org.apache.wicket.Application; name:
>> fonts/glyphicons-halflings-regular.ttf; locale: null; style: null;
>> variation: null] because it cannot be located.
>
> The fonts are defined in bootstrap.css with paths relative to css folder
> like this
>> @font-face {
>> font-family: 'Glyphicons Halflings';
>>
>> src: url('../fonts/glyphicons-halflings-regular.eot');
>> src: url('../fonts/glyphicons-halflings-regular.eot?#iefix')
>> format('embedded-opentype'),
>> url('../fonts/glyphicons-halflings-regular.woff2') format('woff2'),
>> url('../fonts/glyphicons-halflings-regular.woff') format('woff'),
>> url('../fonts/glyphicons-halflings-regular.ttf') format('truetype'),
>> url('../fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular')
>> format('svg');
>> }
>
> Of course the fonts exist at /src/main/webapp/fonts (sibling of folder
> css) and are in the war file at /fonts.
>
> I tried to use
> getResourceSettings().setCssCompressor(new CssUrlReplacer());
> in my WebApplication#init but with no difference, the errors are still
> there.
>
> What is the correct way of resource handling at java side?
>
> Thank You
> Dieter Tremel
>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Resolution of url() in ContextRelativeResourceReference
Hi Martin,
The url is (in DEVELOPMENT mode):
At the moment I use a workaround by including the css by html and the js
by java code:
> ContextRelativeResourceReference bootstrapJavascript
> = new ContextRelativeResourceReference("js/bootstrap.js") {
> // use wicket's jquery lib for Bootstrap
> @Override
> public List getDependencies() {
> Application application = Application.get();
> ResourceReference jqueryRef =
> application.getJavaScriptLibrarySettings().
> getJQueryReference();
>
> return Arrays.asList(new
> HeaderItem[]{JavaScriptHeaderItem.forReference(jqueryRef)});
> }
> };
>
> response.render(JavaScriptHeaderItem.forReference(bootstrapJavascript));
This works.
After some investigations I think including css by
ContextRelativeResource is not widely used, I must be a quirky
developer, because I always try to use libs the exotic way ;-)
By the way there is another strange effect, perhaps a bug:
When I include css with a leading slash as described in Guide "16.5
Context-relative resources"
https://ci.apache.org/projects/wicket/guide/7.x/guide/resources.html#resources_5
it leads to a 404, without the slash it is found.
In a Quickstart with
> ContextRelativeResourceReference styles = new
> ContextRelativeResourceReference("/style.css");
leads to
> HTTP Status 404 -
> /Quickstart20151008/wicket/resource/org.apache.wicket.Application/style-ver-1444283523604.css
whereas
> ContextRelativeResourceReference styles = new
> ContextRelativeResourceReference("style.css");
is OK.
Strange because in ContextRelativeResource there is a demand for the
leading slash:
> public ContextRelativeResource(String pathRelativeToContextRoot)
> {
> Args.notNull(pathRelativeToContextRoot,
> "pathRelativeToContextRoot");
>
> // Make sure there is a leading '/'.
> if (!pathRelativeToContextRoot.startsWith("/"))
> {
> pathRelativeToContextRoot = "/" +
> pathRelativeToContextRoot;
> }
> this.path = pathRelativeToContextRoot;
> this.cachingEnabled = true;
> }
With a JavaScriptHeaderItem the slash makes no difference, only with
CssHeaderItem.
Dieter
Am 07.10.2015 um 21:41 schrieb Martin Grigorov:
> Hi,
>
> What is the generated url for the .css resource ?
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Wed, Oct 7, 2015 at 10:12 AM, Dieter Tremel <tre...@tremel-computer.de>
> wrote:
>
>> Hello list,
>>
>> Using Bootstrap 3.3.5 I want to include the stylesheet, js and font
>> resources myself, not using wicket-bootstrap. To have a dependency to
>> wicket's jquery version I decided to move resource handling from html to
>> java and to use ContextRelativeResourceReference like this:
>>
>>> ContextRelativeResourceReference bootstrapCSS = new
>> ContextRelativeResourceReference("css/bootstrap.css");
>>> response.render(CssHeaderItem.forReference(bootstrapCSS));
>>> ...
>>
>> When using gylphicons the icons are not rendered correctly, a 404 error
>> is given for the fonts and the log says
>>> 09:45:37.976 [http-nio-8084-exec-6] WARN
>> o.a.w.r.r.ResourceReferenceRegistry - A ResourceReference wont be created
>> for a resource with key [scope: org.apache.wicket.Application; name:
>> fonts/glyphicons-halflings-regular.ttf; locale: null; style: null;
>> variation: null] because it cannot be located.
>>
>> The fonts are defined in bootstrap.css with paths relative to css folder
>> like this
>>> @font-face {
>>> font-family: 'Glyphicons Halflings';
>>>
>>> src: url('../fonts/glyphicons-halflings-regular.eot');
>>> src: url('../fonts/glyphicons-halflings-regular.eot?#iefix')
>> format('embedded-opentype'),
>> url('../fonts/glyphicons-halflings-regular.woff2') format('woff2'),
>> url('../fonts/glyphicons-halflings-regular.woff') format('woff'),
>> url('../fonts/glyphicons-halflings-regular.ttf') format('truetype'),
>> url('../fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular')
>> format('svg');
>>> }
>>
>> Of course the fonts exist at /src/main/webapp/fonts (sibling of folder
>> css) and are in the war file at /fonts.
>>
>> I tried to use
>> getResourceSettings().setCssCompressor(new CssUrlReplacer());
>> in my WebApplication#init but with no difference, the errors are still
>> there.
>>
>> What is the correct way of resource handling at java side?
>>
>> Thank You
>> Dieter Tremel
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Resolution of url() in ContextRelativeResourceReference
Am 08.10.2015 um 08:14 schrieb Dieter Tremel: > With a JavaScriptHeaderItem the slash makes no difference, only with > CssHeaderItem. Sorry, this is wrong, same problem with js. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Resolution of url() in ContextRelativeResourceReference
Now I understand. Thank You Martin. Dieter Am 08.10.2015 um 12:08 schrieb Martin Grigorov: > Hi, > > I guess the problem is that you have a context path and the person who > wrote the guide didn't have it. > If there is no context path then "/style.css" and "style.css" would resolve > to the same - the resource that is in the root of the app. > If there is context path then the absolute url that the browser will use > will be http://host:port/style.css instead of http://host:port > /contextPath/style.css > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Thu, Oct 8, 2015 at 10:01 AM, Dieter Tremel <tre...@tremel-computer.de> > wrote: > >> Am 08.10.2015 um 08:14 schrieb Dieter Tremel: >>> With a JavaScriptHeaderItem the slash makes no difference, only with >>> CssHeaderItem. >> >> Sorry, this is wrong, same problem with js. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Resolution of url() in ContextRelativeResourceReference
Hello list,
Using Bootstrap 3.3.5 I want to include the stylesheet, js and font
resources myself, not using wicket-bootstrap. To have a dependency to
wicket's jquery version I decided to move resource handling from html to
java and to use ContextRelativeResourceReference like this:
> ContextRelativeResourceReference bootstrapCSS = new
> ContextRelativeResourceReference("css/bootstrap.css");
> response.render(CssHeaderItem.forReference(bootstrapCSS));
> ...
When using gylphicons the icons are not rendered correctly, a 404 error
is given for the fonts and the log says
> 09:45:37.976 [http-nio-8084-exec-6] WARN o.a.w.r.r.ResourceReferenceRegistry
> - A ResourceReference wont be created for a resource with key [scope:
> org.apache.wicket.Application; name: fonts/glyphicons-halflings-regular.ttf;
> locale: null; style: null; variation: null] because it cannot be located.
The fonts are defined in bootstrap.css with paths relative to css folder
like this
> @font-face {
> font-family: 'Glyphicons Halflings';
>
> src: url('../fonts/glyphicons-halflings-regular.eot');
> src: url('../fonts/glyphicons-halflings-regular.eot?#iefix')
> format('embedded-opentype'),
> url('../fonts/glyphicons-halflings-regular.woff2') format('woff2'),
> url('../fonts/glyphicons-halflings-regular.woff') format('woff'),
> url('../fonts/glyphicons-halflings-regular.ttf') format('truetype'),
> url('../fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular')
> format('svg');
> }
Of course the fonts exist at /src/main/webapp/fonts (sibling of folder
css) and are in the war file at /fonts.
I tried to use
getResourceSettings().setCssCompressor(new CssUrlReplacer());
in my WebApplication#init but with no difference, the errors are still
there.
What is the correct way of resource handling at java side?
Thank You
Dieter Tremel
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: getPage(pageReference) == null since Wicket 6.10.0
Thank You, will try that. Dieter Am 06.11.2013 17:14, schrieb David Beer: JBoss AS 7 and Wildfly 8 work nicely with Wicket. On 6 November 2013 15:25, Ondrej Zizka ozi...@redhat.com wrote: Try the JBoss EAP 6.1: http://www.jboss.org/jbossas/downloads/ I didn't have much trouble using that with Wicket 6.x. Ondra On 5.11.2013 18:19, Dieter Tremel wrote: Am 12.10.2013 12:19, schrieb Dieter Tremel: Sometimes I have the impression that a Glassfish and wicket are not a couple in great love. Seems that Glassfish and Oracle are not in great love either, since commercial Glassfish is dead, and this is no good future for the open source edition: - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: getPage(pageReference) == null since Wicket 6.10.0
Am 12.10.2013 12:19, schrieb Dieter Tremel: Sometimes I have the impression that a Glassfish and wicket are not a couple in great love. Seems that Glassfish and Oracle are not in great love either, since commercial Glassfish is dead, and this is no good future for the open source edition: https://blogs.oracle.com/theaquarium/entry/java_ee_and_glassfish_server Dieter - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: getPage(pageReference) == null since Wicket 6.10.0
Am 12.10.2013 21:58, schrieb Martin Grigorov: The problem is that most of us use Tomcat/Jetty and we don't test other web containers. Hi, I always saw the decision between full Java EE and Spring Framework, and Spring always made the impression to be a solution for all problems and you have to solve all problems with spring forever. So I didn't want to open this door. Some features of the big application servers where comfortable (CDI, transaction management, container based security) and I watched Adam Bien and started to shout Hallelujah after his videos ;-) Despite that I see the problems of a commitment to a single applications server and would like a small modular solution using Tomcat. My applications are business applications implementing a workflow based on CRUD operations with JPA on open source relational databases. Can you please give me some hints for a minimum stack of doing that with Tomcat without reinventing the wheel: - with or without Spring? - What are key libs (Guice, http://jotm.ow2.org/, ...) - How do you it implement, what are your suggestions? - What is important not to forget? Dieter -- Tremel Computerhttp://www.tremel-computer.de Dieter Tremel mailto:tre...@tremel-computer.de Rebenring 16 Tel +49 871 9357080 84032 Altdorf Fax +49 871 9357081 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
getPage(pageReference) == null since Wicket 6.10.0
Hello wicket-community,
in the last time I had to work on another project, so my wicket-work
paused and I just upgraded to the new versions.
So I was rather astonished that the mechanism I implemented for the
return page after canceling an edit was not working any more, since
getPage(pageref) returned null.
After a lot of tests I know that this came from wicket 6.10.0 on, in
6.9.0 the code was working correctly. I also recognize, that the newer
versions provide a new page id, if I use the URL with the old pageId
manually, so in 6.10.0 the page is expired, whereas in 6.9.0 it is not.
Strange for me.
I use CDI and Glassfish 3.1.2 and have found the issues fixed in 6.10.0,
that could be related:
WICKET-5164 - PageStoreManager.SessionEntry keeps outdated sessionId
when container changes sessionId
WICKET-5309 - No page id appended to some stateful pages using repeaters
Any idea what the problem could be and how I could fix it?
Thank You
Dieter
My code is:
Call of page:
final PageReference pageReference = getPage().getPageReference();
logger.log(Level.INFO, Backpage reference of EntityCrudLink: {0}
({1}), new Object[]{pageReference, pageReference.getPageId()});
setResponsePage(new
EntityEditPage(EntityModelFactory.createEntityModel(editRecord),
crudView, pageReference));
Edit Page:
The PageReference prevPageRef is set in constructor.
Link cancelButton = new Link(cancelButton, new
ResourceModel(CancelLabel)) {
private static final long serialVersionUID = 1L;
@Override
public void onClick() {
IModelString infoModel;
... define infoModel
getSession().info(infoModel.getObject());
setResponsePage(prevPageRef.getPage());
}
};
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: getPage(pageReference) == null since Wicket 6.10.0
Thank you Sven.
I am glad that it is well known and will be fixed in 6.12, and little
bid sad about the hours I spent of studying my code and testing. I
should have asked more early in the mailing list, your support is always
great.
Sometimes I have the impression that a Glassfish and wicket are not a
couple in great love.
Thank you very much
Dieter
Am 12.10.2013 10:47, schrieb Sven Meier:
See WICKET-5380
Sven
On 10/12/2013 10:20 AM, Dieter Tremel wrote:
Hello wicket-community,
in the last time I had to work on another project, so my wicket-work
paused and I just upgraded to the new versions.
So I was rather astonished that the mechanism I implemented for the
return page after canceling an edit was not working any more, since
getPage(pageref) returned null.
After a lot of tests I know that this came from wicket 6.10.0 on, in
6.9.0 the code was working correctly. I also recognize, that the newer
versions provide a new page id, if I use the URL with the old pageId
manually, so in 6.10.0 the page is expired, whereas in 6.9.0 it is not.
Strange for me.
I use CDI and Glassfish 3.1.2 and have found the issues fixed in 6.10.0,
that could be related:
WICKET-5164 - PageStoreManager.SessionEntry keeps outdated sessionId
when container changes sessionId
WICKET-5309 - No page id appended to some stateful pages using repeaters
Any idea what the problem could be and how I could fix it?
Thank You
Dieter
My code is:
Call of page:
final PageReference pageReference = getPage().getPageReference();
logger.log(Level.INFO, Backpage reference of EntityCrudLink: {0}
({1}), new Object[]{pageReference, pageReference.getPageId()});
setResponsePage(new
EntityEditPage(EntityModelFactory.createEntityModel(editRecord),
crudView, pageReference));
Edit Page:
The PageReference prevPageRef is set in constructor.
Link cancelButton = new Link(cancelButton, new
ResourceModel(CancelLabel)) {
private static final long serialVersionUID = 1L;
@Override
public void onClick() {
IModelString infoModel;
... define infoModel
getSession().info(infoModel.getObject());
setResponsePage(prevPageRef.getPage());
}
};
-
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
--
Tremel Computerhttp://www.tremel-computer.de
Dieter Tremel mailto:tre...@tremel-computer.de
Rebenring 16 Tel +49 871 9357080
84032 Altdorf Fax +49 871 9357081
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Google Maps refuses access
Am 14.09.2013 14:36, schrieb Piratenvisier: I don't know from where I got the software wicket.contrib.gmap.api What softwarepackage do you recommend for Google Maps integratiopn Have a look at https://github.com/wicketstuff/core/wiki/Gmap3 Dieter - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: DateTextField, image is displayed on line below
I used
white-space: nowrap;
on the containing element.
Dieter
Am 11.07.2013 23:23, schrieb Delange:
I use css for positioning my fields, but Datatextfield ICON is always
displayed a line below the input
For example:
Orderdate B
date icon
Who can help?
css
.regel{
clear:left;
}
.t1{
display: inline-block;
width: 200px;
float:left;
clear: left;
}
.t2{
display: inline-block;
width: 15px;
float:left;
color: red
}
.t3{
display: inline-block;
width: 100px;
float:left;
}
label class=t2nbsp;/label
div class=t3input wicket:id=besteldatum name=besteldatum
type=text size=9 maxlength=9//div
Is displayed as:
div class=regel
label class=t1Besteldatum/label
label class=t2nbsp;/label
div class=t3input name=besteldatum type=text size=9 maxlength=9
value=05/07/2013 id=id6/
nbsp;
../resource/org.apache.wicket.extensions.yui.calendar.DatePicker/icon1-ver-A9D71378ED9162B2DB5DE040C09D5BDE.gif
/div
/div
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/DateTextField-image-is-displayed-on-line-below-tp4660217.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
wicket-cdi 6.9.0 on Glassfish 4: Warning WELD-001529
Hello, after using wicket 6.9.0 which solved https://issues.apache.org/jira/browse/WICKET-5226 I gave it another try with a quickstart and injecting a simple helloBean, but got some warnings: INFO: WELD-000900 2.0.0 (SP1) WARNING: Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled WARNING: Class 'javax.ejb.PrePassivate' not found, interception based on it is not enabled ... WARNING: No matching SeamConversationContext for store type interface javax.servlet.http.HttpServletRequest, using NOOP instance! WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.cdi.ConversationPropagator which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.cdi.ConversationExpiryChecker which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.cdi.DetachEventEmitter which does not have any appropriate constructor. ... WARNING: WELD-001529 An InjectionTarget implementation is created for a class de.tremel_computer.gf4minimum.HomePage which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.markup.html.basic.Label which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.markup.html.internal.HtmlHeaderContainer which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.markup.html.TransparentWebMarkupContainer which does not have any appropriate constructor. I suppose the first two warnings are a missing dependency, does anybody know which? Any hint how to get rid of the other warnings? Thank You Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-cdi 6.9.0 on Glassfish 4: Warning WELD-001529
I will monitor this and report if I have new knowledge. I am on GlassFish v3.1.2.2 too but took a look how my app runs on Glassfish 4, and, in the first moment thought it was a misuse of wicket-cdi in my code. Additional Information: Seems to be not necessary any more for GF4 to include dependency groupIdorg.jboss.seam.conversation/groupId artifactIdseam-conversation-weld/artifactId version3.0.0.Final/version /dependency if this is active it results in a context is already active exception, without it runs fine. Dieter Am 02.07.2013 17:00, schrieb Paul Bors: If I'm not wrong GlassFish 4 support Java 7: http://docs.oracle.com/javaee/7/api/javax/ejb/PostActivate.html http://docs.oracle.com/javaee/7/api/javax/ejb/PrePassivate.html You might be interested in (which blames it on a project configuration): https://java.net/jira/browse/GLASSFISH-20564 WARNING: Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled I'm still on GlassFish v3.1.2.2 but with the new IE-10 I might have to upgrade as well. Let me know how it goes for you :) ~ Thank you, Paul Bors -Original Message- From: Dieter Tremel [mailto:tre...@tremel-computer.de] Sent: Tuesday, July 02, 2013 10:11 AM To: users@wicket.apache.org Subject: wicket-cdi 6.9.0 on Glassfish 4: Warning WELD-001529 Hello, after using wicket 6.9.0 which solved https://issues.apache.org/jira/browse/WICKET-5226 I gave it another try with a quickstart and injecting a simple helloBean, but got some warnings: INFO: WELD-000900 2.0.0 (SP1) WARNING: Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled WARNING: Class 'javax.ejb.PrePassivate' not found, interception based on it is not enabled ... WARNING: No matching SeamConversationContext for store type interface javax.servlet.http.HttpServletRequest, using NOOP instance! WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.cdi.ConversationPropagator which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.cdi.ConversationExpiryChecker which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.cdi.DetachEventEmitter which does not have any appropriate constructor. ... WARNING: WELD-001529 An InjectionTarget implementation is created for a class de.tremel_computer.gf4minimum.HomePage which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.markup.html.basic.Label which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.markup.html.internal.HtmlHeaderContainer which does not have any appropriate constructor. WARNING: WELD-001529 An InjectionTarget implementation is created for a class org.apache.wicket.markup.html.TransparentWebMarkupContainer which does not have any appropriate constructor. I suppose the first two warnings are a missing dependency, does anybody know which? Any hint how to get rid of the other warnings? Thank You Dieter Tremel - 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 -- Tremel Computerhttp://www.tremel-computer.de Dieter Tremel mailto:tre...@tremel-computer.de Rebenring 16 Tel +49 871 9357080 84032 Altdorf Fax +49 871 9357081 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wiki down
Calling the wiki at https://cwiki.apache.org/WICKET/ results in Not Found The requested URL /WICKET/ was not found on this server. Is this known already? Thank You Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-jasperreports dependency to jasper reports
Am 28.05.2013 21:26, schrieb Martin Grigorov: Merged! Danke! May I ask an additional question, not mainly wicket but a maven problem with the wicketstuff core local replicate. When I build the core or subprojects with netbeans 7.3 maven integration it leads today to the following error: Failed to execute goal on project lightbox2: Could not resolve dependencies for project org.wicketstuff:lightbox2:jar:6.0-SNAPSHOT: Failure to find org.apache.wicket:wicket:pom:6.8.0-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of wicket-snapshots has elapsed or updates are forced - [Help 1] When I change 6.8.0-SNAPSHOT to 6.8.0 in the root pom the build runs without problem. I had the problem before, but could get rid of it by doing a fresh clone, but the error returned without change of configuration. Any hint to improve my maven knowledge would be great. Thank You Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicketstuff-jasperreports dependency to jasper reports
In wicketstuff-jasperreports the dependency to jasper is dependency groupIdjasperreports/groupId artifactIdjasperreports/artifactId /dependency That leads to version 3.5.3 I found http://mvnrepository.com/artifact/net.sf.jasperreports/jasperreports/5.1.0, so the newer version could be used. Is there any reason to keep the older version (repository)? Thank You Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff-jasperreports dependency to jasper reports
Am 28.05.2013 09:39, schrieb Martin Grigorov: You can form wicketstuff/core project and send a pull request with the upgrade. Well, I've made it. With a little luck and lot of horses. ;-) (Silly slogan from a Marlboro cigarette commercial in germany from about 1990) https://github.com/wicketstuff/core/pull/224 Dieter -- Tremel Computerhttp://www.tremel-computer.de Dieter Tremel mailto:tre...@tremel-computer.de Rebenring 16 Tel +49 871 9357080 84032 Altdorf Fax +49 871 9357081 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicketstuff gmap GInfoWindow with Component content
Hello,
I would like to show an info window on clicking on a map marker with
detailed information about an entity, including links and so on. I coded
a special panel for this.
I think therefor I should use the Constructor
public GInfoWindow(GLatLng latLng, Component content)
As I read from the Code
this.content = document.getElementById(' + markupId + ');
contentIsNode = true;
only the id of the component is used and the placement in the window is
done by some javascript, referencing the id in a json structure.
As I didn't find an example and i do not understand where the component
should be rendered in fact, I ask here. Should there be one panel
supported with data by a model of the entity, rendered somehow hidden in
another place?
Any hint for way to do it or a solution welcome.
Thank You
Dieter Tremel
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicketstuff gmap GInfoWindow with Component content
Am 22.03.2013 10:09, schrieb Thijs: There is an example to: https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/gmap3-parent/gmap3-examples/src/main/java/org/wicketstuff/examples/gmap/info/advanced Must have been blind not to recognize it. Thank You Dieter - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Gmap3 Geocoding shows Status 610
I tried to fix it by using the json library from json.org:
dependency
groupIdorg.json/groupId
artifactIdjson/artifactId
version20090211/version
/dependency
I changed GeoCoder.java, GeoCoderException.java, and improved
GeoCoderTest.java which run without complains. Sorry, I never committed
to github or any other open source project. If you think I should do so,
please give me some short instruction what I should do.
Dieter Tremel
The central part of Geocoder is
private final String output = OUTPUT_JSON;
public GLatLng decode(String response) throws GeocoderException {
try {
JSONObject jsonResponse = new JSONObject(response);
GeocoderException.GeocoderStatus status =
GeocoderException.GeocoderStatus.valueOf(jsonResponse.getString(status));
if (status != GeocoderException.GeocoderStatus.OK) {
throw new GeocoderException(status);
}
JSONArray results = jsonResponse.getJSONArray(results);
JSONObject location =
results.getJSONObject(0).getJSONObject(geometry).getJSONObject(location);
return new GLatLng(location.getDouble(lat),
location.getDouble(lng));
} catch (JSONException ex) {
Logger.getLogger(Geocoder.class.getName()).log(Level.SEVERE,
null, ex);
throw new
GeocoderException(GeocoderException.GeocoderStatus.PARSER_ERROR);
}
}
public String encode(final String address) {
//changed since this was Google API V2, see
https://developers.google.com/maps/documentation/geocoding/
//return http://maps.google.com/maps/geo?q=; +
urlEncode(address) + output= + output;
StringBuilder sb = new
StringBuilder(http://maps.googleapis.com/maps/api/geocode/;);
sb.append(output);
sb.append(?);
sb.append(address=).append(urlEncode(address));
sb.append(sensor=false);
return sb.toString();
}
Am 18.03.2013 15:27, schrieb Dieter Tremel:
Am 16.03.2013 22:43, schrieb Vishal Popat:
I am using GMap3 from here:
https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/gmap3-parent/gmap3.
My Geocoding has recently stopped working and is showing Status 610. Google
searching shows that this is all related to GMap2 being deprecated etc
(There maybe other reasons why I am getting a 610).
However, when looking here:
https://github.com/wicketstuff/core/blob/master/jdk-1.6-parent/gmap3-parent/gmap3/src/main/java/org/wicketstuff/gmap/geocoder/Geocoder.java.
The encoding url looks like it is from Gmap v2 (see here:
https://developers.google.com/maps/documentation/geocoding/index), which
would explain the 610.
Am I mistaken?
Hello Vishal,
I have the same problem and think you are right. Geocoder#encode in
Version 6.5.0 uses an old URL and parses the return value as CSV,
whereas https://developers.google.com/maps/documentation/geocoding/ only
talks about JSON and XML return values. The unit test of Geocoder fails
with error code 610.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Gmap3 Geocoding shows Status 610
Am 19.03.2013 13:25, schrieb Martin Grigorov: Welcome to the Open Source community! :-) You can follow the guide at https://help.github.com/articles/fork-a-repo to send a Pull Request with your fix. If you have not time for this then please send me the changes in .patch format and I will apply them for you. Hi Martin, After some drops of sweat I succeeded in https://github.com/wicketstuff/core/pull/203 Hope I did it all well. Would be glad if my changes are accepted and I can contribute. By the way, this is a great community here in this list, I am often surprised how fast and well the users get help. Thank to all for it. Dieter - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Gmap3 Geocoding shows Status 610
Am 16.03.2013 22:43, schrieb Vishal Popat: I am using GMap3 from here: https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/gmap3-parent/gmap3. My Geocoding has recently stopped working and is showing Status 610. Google searching shows that this is all related to GMap2 being deprecated etc (There maybe other reasons why I am getting a 610). However, when looking here: https://github.com/wicketstuff/core/blob/master/jdk-1.6-parent/gmap3-parent/gmap3/src/main/java/org/wicketstuff/gmap/geocoder/Geocoder.java. The encoding url looks like it is from Gmap v2 (see here: https://developers.google.com/maps/documentation/geocoding/index), which would explain the 610. Am I mistaken? Hello Vishal, I have the same problem and think you are right. Geocoder#encode in Version 6.5.0 uses an old URL and parses the return value as CSV, whereas https://developers.google.com/maps/documentation/geocoding/ only talks about JSON and XML return values. The unit test of Geocoder fails with error code 610. Unfortunately I changed a few weeks ago from an own solution to the wicketstuff gmap3 solution for not to reinvent the wheel. Now I will have a look at my solution again. Martin, is there an issue for this or should we open one? Dieter - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicket-cdi fails when netbeans deploys to Glassfish with maven
Hello, at the moment I try to migrate my wicket ant projects to maven, and have a final problem with CDI. I am using netbeans 7.2.1 and Glassfish 3.1.2, when I click run the the war is deployed to glassfish in the pom with mvn.bat -Dnetbeans.deploy=true package and the property netbeans.hint.deploy.servergfv3ee6/netbeans.hint.deploy.server defined in the pom. Don't know how exactly. When I try to use CDI, I get the error: WARNING: StandardWrapperValve[default]: PWC1406: Servlet.service() for servlet default threw exception javax.enterprise.context.ContextNotActiveException: Conversation Context not active when method called on conversation Transient conversation at org.jboss.weld.context.conversation.ConversationImpl.verifyConversationContextActive(ConversationImpl.java:197) at org.jboss.weld.context.conversation.ConversationImpl.touch(ConversationImpl.java:159) at org.jboss.weld.context.conversation.ConversationImpl.init(ConversationImpl.java:72) at org.jboss.weld.bean.builtin.ConversationBean.create(ConversationBean.java:48) at org.jboss.weld.bean.builtin.ConversationBean.create(ConversationBean.java:17) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:107) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:104) at org.jboss.weld.proxies.Conversation$-493077674$Proxy$_$$_WeldClientProxy.isTransient(Conversation$-493077674$Proxy$_$$_WeldClientProxy.java) at org.apache.wicket.cdi.ConversationPropagator.onRequestHandlerExecuted(ConversationPropagator.java:177) I built a small Quickstart and added the injection of a tiny HelloBean in the simplest way, but same problem. Dependency to wicket-cdi 6.4.0 has transient dependency to seam-conversation-spi, which is included in war/WEB-INF/libs. With ant based project, no error. Any idea? Thank You Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket-cdi fails when netbeans deploys to Glassfish with maven
Thanks, Igor, worked instantly. I should have been more precise here. Thank You Dieter Am 09.01.2013 21:17, schrieb Igor Vaynberg: you need to add seam-conversation-your cdi impl.jar as well. -igor On Wed, Jan 9, 2013 at 10:55 AM, Dieter Tremel tre...@tremel-computer.de wrote: Hello, at the moment I try to migrate my wicket ant projects to maven, and have a final problem with CDI. I am using netbeans 7.2.1 and Glassfish 3.1.2, when I click run the the war is deployed to glassfish in the pom with mvn.bat -Dnetbeans.deploy=true package and the property netbeans.hint.deploy.servergfv3ee6/netbeans.hint.deploy.server defined in the pom. Don't know how exactly. When I try to use CDI, I get the error: WARNING: StandardWrapperValve[default]: PWC1406: Servlet.service() for servlet default threw exception javax.enterprise.context.ContextNotActiveException: Conversation Context not active when method called on conversation Transient conversation at org.jboss.weld.context.conversation.ConversationImpl.verifyConversationContextActive(ConversationImpl.java:197) at org.jboss.weld.context.conversation.ConversationImpl.touch(ConversationImpl.java:159) at org.jboss.weld.context.conversation.ConversationImpl.init(ConversationImpl.java:72) at org.jboss.weld.bean.builtin.ConversationBean.create(ConversationBean.java:48) at org.jboss.weld.bean.builtin.ConversationBean.create(ConversationBean.java:17) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:107) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:104) at org.jboss.weld.proxies.Conversation$-493077674$Proxy$_$$_WeldClientProxy.isTransient(Conversation$-493077674$Proxy$_$$_WeldClientProxy.java) at org.apache.wicket.cdi.ConversationPropagator.onRequestHandlerExecuted(ConversationPropagator.java:177) I built a small Quickstart and added the injection of a tiny HelloBean in the simplest way, but same problem. Dependency to wicket-cdi 6.4.0 has transient dependency to seam-conversation-spi, which is included in war/WEB-INF/libs. With ant based project, no error. Any idea? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Asking for user confirmation - Wicket 6
Am 15.11.2012 18:47, schrieb Sven Meier:
ajaxCallListener.onPrecondition(return confirm('are you sure'?););
I made a test and found the small Typo, should be:
ajaxCallListener.onPrecondition(return confirm('are you sure?'););
Dieter
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: String Resources associated with entity classes
Hello Bas, Am 27.10.2012 23:04, schrieb Bas Gooren: So just to confirm: Say you have an entity House, you'll have House.class House.properties Yes. The beginning of my book example author properties file is (German naming): # Entity Autor LabelPlural=Autoren Label=Autor Title=Autor Description=Autor autornrLabel=Autornr autornrTitle=Autornr autornrDescription=Eindeutige Nummer des Autors ... for other fields 1) where in the properties file you have a key Label with a value? 2) and in wicket you say getString(House.Label), or new ResourceModel(House.Label)? If this is the case, write a custom string resource loader, which takes the first part of the resource key, and checks if there is a matching entity with associated property file. Then use the other parts of the property key for the actual lookup in the property file. Thank you, I didn't have the idea of putting the Entity class name as part of the key, so it can be significant for caching. I modified my custom string resource loader as you suggested and added the EntityClassName. to my ResourceModels and it works! Thank You Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
String Resources associated with entity classes
For every JPA entity class I have a associated properties file in a package called resources under the package of the entity classes. In the files the display label, title, description of the entity and it's attributes are given for internationalization. The keys in the files are not necessarily different for different classes, each class uses a Label key for it's display label. I tried to include this in the wicket resource mechanism by adding a ResourceLoader that uses a BundleStringResourceLoader for each entity class, which is used when a component or it's ancestor implement a EntityClassHolder Interface and can give an entity class. But this does not work, since the String Resources are cached for the first hit entity class, and the cache gives the reply for all other entity classes. So my idea was not sufficient :-( Of course I can write my own mechanism of getting the strings from the properties encapsulated in a model. But wickets resource handling is so sophisticated, that I suppose there is a more elegant way, I do not see. How would you implement resource loading fore files associated to entity classes, not to component hierarchy? Thank You Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket with JPA and container managed transactions
Am 08.10.2012 17:37, schrieb Martin Grigorov: The JNDI lookup just done for you in normal JavaEE setup as well. So I think your code is OK. Thank you Martin for your useful answers. I posted a little more generic solution of an AbstractEjbModel in my blog in http://hotchpotch-blog.de/2012/10/09/wrapping-eines-ejb-in-ein-loadabledetachablemodel/ (only in german language). If I have some more time I will have a look at javaee-inject. That solution of packing EJB into CDI bean I could not make run, perhaps my code hasn't been smart enough in this tests. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicket with JPA and container managed transactions
Moving from JSF to Wicket 6.1.0 I am used to having all JPA operations in a EJB facade to use the container's (Glassfish 3.2.1) transaction management. I use and know wicket-cdi for injection, which works fine. Unfortunately, if I inject an EJB in a wicket page, the serialization checks of wicket complain that it is not serializable. This is true for EJB, I suppose since they are proxied by EJBLocalObjectInvocationHandlerDelegate. Frustrated I have read the thread around http://markmail.org/message/4esc7m5subft5ngu My thinking is blocked at this point. If I can't use jpa with container managed transactions wicket how is the simpliest way do achieve it? All examples I googled and also these in the book Wicket in Action are only reading data or using Spring, what I do not want to do. Thank you for any hint Dieter Tremel - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket with JPA and container managed transactions
Am 08.10.2012 15:14, schrieb Martin Grigorov: Are you aware of https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/javaee-inject-parent ? Hi Martin, I know this lib an had a look at it. If I am right, it is just another way of injection. In my running example of implementing a data provider the injection already works and a have a beautiful rendered result of my data. But after the request the error around serialization is: SEVERE: Error serializing object class de.tremel_computer.buchbeispiel.wicket.BuecherPage [object=[Page class = de.tremel_computer.buchbeispiel.wicket.BuecherPage, id = 0, render count = 1]] org.apache.wicket.core.util.io.SerializableChecker$WicketNotSerializableException: Unable to serialize class: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate Field hierarchy is: 0 [class=de.tremel_computer.buchbeispiel.wicket.BuecherPage, path=0] private java.lang.Object org.apache.wicket.MarkupContainer.children [class=[Ljava.lang.Object;] java.lang.Object org.apache.wicket.Component.data[2] [class=org.apache.wicket.extensions.markup.html.repeater.data.table.DefaultDataTable, path=0:datatable] private java.lang.Object org.apache.wicket.MarkupContainer.children [class=[Ljava.lang.Object;] java.lang.Object org.apache.wicket.Component.data[1] [class=org.apache.wicket.markup.html.WebMarkupContainer, path=0:datatable:body] private java.lang.Object org.apache.wicket.MarkupContainer.children [class=org.apache.wicket.extensions.markup.html.repeater.data.table.DataTable$1, path=0:datatable:body:rows] private final org.apache.wicket.markup.repeater.data.IDataProvider org.apache.wicket.markup.repeater.data.DataViewBase.dataProvider [class=de.tremel_computer.wicketcrud.modeling.EntityDataProvider] private de.tremel_computer.wicketcrud.controller.AbstractFacade de.tremel_computer.wicketcrud.modeling.EntityDataProvider.facade [class=de.tremel_computer.buchbeispiel.jpa.facade.__EJB31_Generated__BuchFacade__IntfBean__] private de.tremel_computer.buchbeispiel.jpa.facade.__EJB31_Generated__BuchFacade__Intf__ de.tremel_computer.buchbeispiel.jpa.facade.__EJB31_Generated__BuchFacade__IntfBean__.__ejb31_delegate [class=$Proxy182] protected java.lang.reflect.InvocationHandler java.lang.reflect.Proxy.h [class=com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate] - field that is not serializable I suppose with javaee-inject-parent I would have the same error after rendering. Thank You Dieter -- Tremel Computerhttp://www.tremel-computer.de Dieter Tremel mailto:tre...@tremel-computer.de Rebenring 16 Tel +49 871 9357080 84032 Altdorf Fax +49 871 9357081 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket with JPA and container managed transactions
Am 08.10.2012 15:34, schrieb Martin Grigorov: javaee-inject uses wicket-ioc and injects a serializable Proxy instead of the EJB bean itself that was returned by the container. This is the same as how Spring and Guice work. See the response of heapifyman. The simplest would be use only CDI in your Wicket code. Hide any usage of EJBs behind CDI. Thank You both for details, I will try some tests in both directions. Dieter - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket with JPA and container managed transactions
I found a different solution I would like to post for discussion:
I encapsulated the Facade in a LoadableDetachableModel like this:
/**
* Model for JPA facade beans.
* @author Dieter Tremel tre...@tremel-computer.de
*/
public class EntityFacadeModelE extends JPAEntity extends
LoadableDetachableModelAbstractFacadeE {
private Class? extends JPAEntity entityClass;
public EntityFacadeModel(Class? extends JPAEntity entityClass) {
this.entityClass = entityClass;
}
@Override
protected AbstractFacadeE load() {
AbstractFacadeE result = null;
try {
InitialContext ctx = new InitialContext();
result = (AbstractFacadeE) ctx.lookup(java:module/ +
entityClass.getSimpleName() + Facade);
} catch (NamingException ex) {
Logger.getLogger(EntityFacadeModel.class.getName()).log(Level.SEVERE, null,
ex);
}
return result;
}
}
I hope the JNDI lookup is a not too expensive operation, is it?
In the page I build this like:
EntityDataProviderBuch buchProvider = new EntityDataProvider(new
EntityFacadeModelBuch(Buch.class));
DefaultDataTableBuch, String dTable = new
DefaultDataTable(datatable, columns, buchProvider, 10);
And in the EntityDataProvider I have overwritten:
@Override
public void detach() {
facadeModel.detach();
super.detach();
}
As a result there are no serialization errors in my trial. The lookup
will be called once per request.
What do you think?
Dieter
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
