I have a little chunk of re-usable code I wrote in some of our more modern
apps that I've been asked to add to a couple apps we have that are very old.
they're still on wicket 1.4 and the boss doesn't want to invest in upgrading
them wholesale, but just wants this one feature put i
In that case a Wicket Model keeps a hard reference to the Hibernate entity
that keeps a reference to the Spring class.
You might need to use LoadableDetachableModel.
Look around these classes:
[class=it.loginet.petrol.presentation.sinottico.CachedDataProviderModel]
Hello Martin,
absolutely Hibernate is not injecting classes anywhere in Wicket classes.
Interceptor is used to inject a Spring-configured class, ViaggioService,
into a specific domain class, Viaggio.java.
This code builds a DataTable of Viaggio entities inside the page that throws
the NotSerializa
Hi Leonardo,
How Hibernate Interceptor injects classes in Wicket classes ?!
Wicket serializes the Page instance and everything in it, i.e. components,
their models, etc.
For some reason you pass non-serializable instance of one of your
Viaggio*** classes to a Wicket component/model.
Show us the
Hi Martin,
actually ViaggioService comes from a domain class, ViaggioRete, where is
injected through a custom Hibernate Interceptor.
At the moment, it seems I have to let all my code implement the Serializable
interface, but it doesn't sound as the correct option. Futhermore, I got
stuck on Spring
The problem is in these classes:
[class=it.loginet.petrol.presentation.sinottico.CachedDataProviderModel]
private final java.lang.Object
it.loginet.commons.wicket.repeater.DefaultSortableDataProvider$1.val$object
[class=it.loginet.petrol.domain.viaggio.ViaggioRete]
Actually field "stampeFactory" implements Spring interface
'org.springframework.beans.factory.config.ServiceLocatorFactoryBean', which
allows us to retrieve beans as prototypes but it's not Serializable (spring
version is 3.2.2.RELEASE).
I don't think I can use @SpringBean in this situation, as my
xtends Serializable
>
>
> On Sun, Jan 21, 2018 at 8:48 PM, Leonardo D'Alimonte <
> leonardo.dalimo...@loginet.it> wrote:
>
>> Hi everyone,
>> I'm working on the migration of our WebApplication from Wicket 1.4 to
>> Wicket
>> 6, I don
It seems the problem is caused by the fact
java.lang.reflect.InvocationHandler interface does not extends Serializable
On Sun, Jan 21, 2018 at 8:48 PM, Leonardo D'Alimonte <
leonardo.dalimo...@loginet.it> wrote:
> Hi everyone,
> I'm working on the migration of our WebA
Hi everyone,
I'm working on the migration of our WebApplication from Wicket 1.4 to Wicket
6, I don't understand why with the new version I'm getting this exception;
BEGIN
21/01/2018 14:24:37,925 ERROR -JavaSerializer - Error serializi
The Apache Wicket team announces that support for Apache Wicket 1.4.x
ends on 16 November 2015.
On the same day Wicket 1.5.x enters "security fixes" maintenance mode.
This means that after 16 October 2015:
- no more releases from the 1.4.x branch
- bugs affecting only the 1.4.x branc
ep 11, 2015 at 11:37 AM, stevenb wrote:
> Hello
>
> I am in the middle of upgrading a quite large Wicket 1.4 application.
> The goal is Wicket 6, but we decided to upgrade in steps, first to 1.5.13,
> and then to 6
>
> We are almost ready with the first step, but one of
Hello
I am in the middle of upgrading a quite large Wicket 1.4 application.
The goal is Wicket 6, but we decided to upgrade in steps, first to 1.5.13,
and then to 6
We are almost ready with the first step, but one of the last problems is the
following :
We have a loginpage, and when we hit
Hi,
On Thu, Mar 14, 2013 at 3:56 PM, anotherUser <
juan.dellagn...@theiaconsulting.com> wrote:
> Hi this my first post here, let's see my problem:
>
Welcome !
> i am adding a AjaxSubmitLink in a Listview like this:
>
> AjaxSubmitLink lnkAgregar = new AjaxSubmitLink("lnkDetalle", form) {
>
>
Hi this my first post here, let's see my problem:
i am adding a AjaxSubmitLink in a Listview like this:
AjaxSubmitLink lnkAgregar = new AjaxSubmitLink("lnkDetalle", form) {
@Override
protected void onSubmit(AjaxRequestTarget art, Form form) {
}
};
ln
llo,
>
> We are currently involved in a migration effort from Wicket 1.4 to Wicket
> 6. As it currently stands, we are heavily leveraging the various
> DecoratingHeaderResponses available in Wicket 1.4 to inject resource
> dependencies, aggregate resources into collections of similar type
wnloads a file) in an
>> onsubmit of a wicket form.
>>
>> We used to do this (with Wicket 1.4):
>>
>> Get the WebResponse
>> Fill it with the ZIP contents
>>
>> throw new AbortException();
>>
>> The ZIP contents to be returned depends on the
> We used to do this (with Wicket 1.4):
>
> Get the WebResponse
> Fill it with the ZIP contents
>
> throw new AbortException();
>
> The ZIP contents to be returned depends on the contents filled in by the
> user in a wicket form.
>
> However, AbortException does not
Hi,
We have some code that returns zip output (e.g. downloads a file) in an
onsubmit of a wicket form.
We used to do this (with Wicket 1.4):
Get the WebResponse
Fill it with the ZIP contents
throw new AbortException();
The ZIP contents to be returned depends on the contents filled in by the
Tried the mapper.
It looks like it behaves exactly as overriding isVersioned to return false
at the wanted page...
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/wicket-1-4-to-1-5-migration-page-id-in-urls-issue-how-to-remove-for-certain-pages-tp4650445p4650544.html
S
Hi Sam,
I wrote a custom MountedMapper for the project I'm currently working on.
All it does, is not rendering the page version info for pages. For all
other components it is still turned on. IMHO this mimics the pre-1.5
behavior. We've been using it in production for quite a while now and it
work
Thank you very much Jeremy!
It was a good read through, very informative!
I already browsed through Ivan's post but deemed it unrelevant to my
problem on the first read.
After reading the second post, then reading Ivan's post again, I now
understand the page versioning system a lot better :)
Sadly
Hi,
Sadly I didn't find any similar thread on nabble or stackoverflow...
In wicket 1.4 I had a mount for /devices that lead to a page that shows a
data table with some filtering options.
The page is stateful - mainly because of the filtering options.
when you filter the url changes to /d
Thanks a lot.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-4-newSession-id-tp4650337p4650339.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: us
Hi,
Because there is no active session yet.
You have to call session.bind() before that.
On Tue, Jul 3, 2012 at 4:56 PM, dpmihai wrote:
> In my WebApplication is there possible to know the session id inside
> newSession method?
>
> public Session newSession(Request request, Response response) {
In my WebApplication is there possible to know the session id inside
newSession method?
public Session newSession(Request request, Response response) {
Session session = super.newSession(request, response);
...
String id = session.getId(); // returns null;
}
--
Vie
then to 6.0.0-beta2.
>
> On Tue, Jul 3, 2012 at 1:14 PM, Vit Rozkovec wrote:
> > Hi,
> > what is the best approach when migrating from wicket 1.4.x?
> > Wait for stable 6.0 version and then start migration or migrate to 1.5.x
> > version?
> >
> > All my pr
at 1:14 PM, Vit Rozkovec wrote:
> Hi,
> what is the best approach when migrating from wicket 1.4.x?
> Wait for stable 6.0 version and then start migration or migrate to 1.5.x
> version?
>
> All my projects now use 1.4.x with Hibernate via Databinder. I want to save
> myself
Hi,
what is the best approach when migrating from wicket 1.4.x?
Wait for stable 6.0 version and then start migration or migrate to 1.5.x
version?
All my projects now use 1.4.x with Hibernate via Databinder. I want to
save myself the effort to do a double migration and would rather wait
and
I made it by reading cookies in my AuthenticatedWebApplication in
@Override
public Session newSession(Request request, Response response) {
Session session = super.newSession(request, response);
HttpSer
See wicket-examples project.
It has an example with rememberMe functionality.
On Mon, Jun 18, 2012 at 5:16 PM, dpmihai wrote:
> Hi.
>
> My problem is not how to read the cookie. I do not know WHERE to read it,
> because my authentication is done from LoginPanel / LoginValidator, and I do
> not wa
Hi.
My problem is not how to read the cookie. I do not know WHERE to read it,
because my authentication is done from LoginPanel / LoginValidator, and I do
not want my LoginPanel to be shown anymore.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-4-Remember-L
CookieUtils (1.5+) is the new name of CookieValuePersister (until 1.4.x)
On Mon, Jun 18, 2012 at 5:09 PM, Thomas Götz wrote:
> Have a look at org.apache.wicket.util.cookies.CookieUtils#load(final String
> key).
>
> Cheers,
> -Tom
>
>
> --
Have a look at org.apache.wicket.util.cookies.CookieUtils#load(final String
key).
Cheers,
-Tom
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Hi.
I have a wicket 1.4 application with a AuthenticatedWebSession with
authenticate(String username, String password) method. I use annotations to
allow for seeing some components : @AuthorizeAction(action = Action.RENDER,
roles = Roles.ADMIN) for example.
I want when user logs in to save a
Thanks for looking into this. It seems to be a deployment issue. The way I
did it is right for Wicket 1.5.
Now I am facing an even bigger problem. I will post another one regarding
"redirect loop".
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Loop-populateItem
Could you please provide a quickstart?
-Tom
On 31.05.2012, 00:32 paulstar wrote:
> in Wicket 1.4, this works fine:
>
> this.form.add(new Loop("ccformfields", ccformfields.size())
> {
> @Override
>
in Wicket 1.4, this works fine:
this.form.add(new Loop("ccformfields", ccformfields.size())
{
@Override
protected void populateItem(LoopItem item)
{
With the 1.4.x release, I want to override the auto complete text field
functionality. On 'selection', I want to be able to redirect to some
page.
It looks like there is a place to override this functionality but it
allows 'javascript' functions and not 'wicket' logic? Can I add
'setResponseP
On 02/20/2012 03:49 AM, Emmanouil Batsis (Manos) wrote:
On 02/19/2012 10:56 PM, Jorge Rodrigez wrote:
You just need to add/remove an item to your data source.
Next time you rerender the grid it will show/hide the added/removed
Any custom datasource examples out there? Essentially I'd like to b
On 02/19/2012 10:56 PM, Jorge Rodrigez wrote:
You just need to add/remove an item to your data source.
Next time you rerender the grid it will show/hide the added/removed
Any custom datasource examples out there? Essentially I'd like to bind
the grid to a POJO collection member.
Manos
-
You just need to add/remove an item to your data source.
Next time you rerender the grid it will show/hide the added/removed
item/row.
On Sun, Feb 19, 2012 at 6:46 PM, Emmanouil Batsis (Manos) wrote:
> Subject says it all... currently using inmethod from wicketstuff but there
> is no add/remove r
Subject says it all... currently using inmethod from wicketstuff but
there is no add/remove row in the 1.4.x versions.
Manos
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-
On Tue, Feb 7, 2012 at 5:28 PM, Thomas Singer wrote:
> It looks like Wicket 1.5 is a so radical change to 1.4 that it better would
> have been named Wicket 2.
The whole request processing part has been rewritten. The whole URL
generation/parsing has been rewritten. But that is the biggest change,
Hi Tom,
I have to admit that migration to 1.5 looks daunting at first, but there
aren't so many radical changes actually.
>Maybe it will require the use of a different programming language?
Don't give us any ideas ;).
Sven
Am 07.02.2012 17:28, schrieb Thomas Singer:
It looks like Wicket 1.
The String path is from a business object.
Tom
On 07.02.2012 17:48, Martijn Dashorst wrote:
> On Tue, Feb 7, 2012 at 4:57 PM, Thomas Singer wrote:
>>> IRequestHandler handler =
>>> Application.get().getRootRequestMapper().mapRequest(request);
>>
>> Requires a Request instance, but I just have a
On Tue, Feb 7, 2012 at 4:57 PM, Thomas Singer wrote:
>> IRequestHandler handler =
>> Application.get().getRootRequestMapper().mapRequest(request);
>
> Requires a Request instance, but I just have a path String...
Where do you get the path string from?
Anyways, typically you can get at the Reques
It looks like Wicket 1.5 is a so radical change to 1.4 that it better would
have been named Wicket 2. Nevertheless, creating an intermediate version
which deprecated the old classes and methods but information/code about how
to migrate to the new API would have MUCH better approach. If 1.4 to 1.5
r
e used.
>>>
>>> Looking at your code, probably you'd rather want to use a
>>> RequestHandler or RequestMapper. It is not easy looking at the snippet
>>> what the use case is you actually want to achieve.
>>>
>>> Martijn
>>>
>>
I think you need to create your own subclass of WebMarkupContainer which
overrides Component#newMarkupSourcingStrategy() to return the proper
IMarkupSourcingStrategy.
On 07/02/2012 10:46 AM, Thomas Singer wrote:
We subclassed WebMarkupContainerWithAssociatedMarkup and used it as
Component. Ne
We subclassed WebMarkupContainerWithAssociatedMarkup and used it as
Component. Neither of your suggested IMarkupSourcingStrategy implementations
is a Component. What should I do? Thanks in advance.
Tom
On 07.02.2012 13:26, Martijn Dashorst wrote:
> On Tue, Feb 7, 2012 at 1:18 PM, Thomas Singer
On Tue, Feb 7, 2012 at 1:18 PM, Thomas Singer wrote:
> The migration guide mentions WebMarkupContainerWithAssociatedMarkup in the
> section TabbedPanel, but there is not such class in Wicket 1.5 any more.
See IMarkupSourcingStrategy and its implementations.
Martijn
--
Become a Wicket expert, l
probably you'd rather want to use a
>> RequestHandler or RequestMapper. It is not easy looking at the snippet
>> what the use case is you actually want to achieve.
>>
>> Martijn
>>
>> On Tue, Feb 7, 2012 at 11:39 AM, Thomas Singer wrote:
>>> Foll
The migration guide mentions WebMarkupContainerWithAssociatedMarkup in the
section TabbedPanel, but there is not such class in Wicket 1.5 any more.
Tom
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional
r. It is not easy looking at the snippet
> what the use case is you actually want to achieve.
>
> Martijn
>
> On Tue, Feb 7, 2012 at 11:39 AM, Thomas Singer wrote:
>> Following Wicket 1.4 code:
>>
>> final RequestParameters parameters =
On Tue, Feb 7, 2012 at 11:44 AM, Martin Grigorov wrote:
>> does not compile in Wicket 1.5: RequestParameters is unknown,
>> RequestCycle.get().getProcessor() is unknown, IBookmarkablePageRequestTarget
>> is unknown, the migration guide is no help.
>
> And it wont get any better until people like y
> And it wont get any better until people like you improve it with their
> findings...
> The wiki is community based.
I may add my information to this wiki page, but then a competent person has
to review and correct it. Or should I just add the missing/changed
classes/methods stubs to the wiki to
t to use a
RequestHandler or RequestMapper. It is not easy looking at the snippet
what the use case is you actually want to achieve.
Martijn
On Tue, Feb 7, 2012 at 11:39 AM, Thomas Singer wrote:
> Following Wicket 1.4 code:
>
> final RequestParameters parameters = new RequestParameters();
> pa
dated the migration guide to simplify the task for their
users.
Tom
On 07.02.2012 11:44, Martin Grigorov wrote:
> On Tue, Feb 7, 2012 at 12:39 PM, Thomas Singer wrote:
>> Following Wicket 1.4 code:
>>
>> final RequestParameters parameters = new RequestParameters();
>>
On Tue, Feb 7, 2012 at 12:39 PM, Thomas Singer wrote:
> Following Wicket 1.4 code:
>
> final RequestParameters parameters = new RequestParameters();
> parameters.setParameters(new HashMap());
>
> String path = ...
> parameters.setPath(path);
> final IReq
Following Wicket 1.4 code:
final RequestParameters parameters = new RequestParameters();
parameters.setParameters(new HashMap());
String path = ...
parameters.setPath(path);
final IRequestTarget requestTarget = RequestCycle.get().getProcessor()
.getRequestCodingStrategy
Wicket 1.4 code:
final class FooFilter extends AbstractMarkupFilter {
public MarkupElement nextTag() throws ParseException {
ComponentTag tag = (ComponentTag)getParent().nextTag();
...
}
}
Should I replace it with
final class FooFilter extends AbstractMarkupFilter {
protected
markupSettings.setMarkupFactory(
new MarkupFactory() {
...
}
);
Please update the migration page.
On Tue, Feb 7, 2012 at 11:43 AM, Thomas Singer wrote:
> We have following code in our WebApplication's init method:
>
> final IMarkupSettings markupSettings = getMarkupSettings();
> markup
We have following code in our WebApplication's init method:
final IMarkupSettings markupSettings = getMarkupSettings();
markupSettings.setMarkupParserFactory(new IMarkupParserFactory() {
public MarkupParser newMarkupParser(MarkupResourceStream resource) {
final MarkupParser parser =
IMarkupFragment markup = component.getMarkup();
MarkupStream stream = new MarkupStream(markup);
On Tue, Feb 7, 2012 at 7:54 AM, vineet semwal
wrote:
> use MarkupContainer#getAssociatedMarkupStream(boolean)
>
> On Tue, Feb 7, 2012 at 11:13 AM, Thomas Singer wrote:
>> MarkupContainer.getMarkupStre
use MarkupContainer#getAssociatedMarkupStream(boolean)
On Tue, Feb 7, 2012 at 11:13 AM, Thomas Singer wrote:
> MarkupContainer.getMarkupStream()
>
> does not exist any more in Wicket 1.5.
>
> Tom
>
>
> On 07.02.2012 06:37, Jenny Brown wrote:
>> I'm still a beginner myself, but upon looking at the
MarkupContainer.getMarkupStream()
does not exist any more in Wicket 1.5.
Tom
On 07.02.2012 06:37, Jenny Brown wrote:
> I'm still a beginner myself, but upon looking at the Javadocs for
> MarkupContainer and MarkupStream, I am not sure where exactly the code is
> giving you trouble. Compile err
I'm still a beginner myself, but upon looking at the Javadocs for
MarkupContainer and MarkupStream, I am not sure where exactly the code is
giving you trouble. Compile error? Runtime exception? Can you be more
specific?
On Mon, Feb 6, 2012 at 11:14 PM, Thomas Singer wrote:
> Does nobody have
Does nobody have an idea? This code prevents me from making progress in
converting our application to Wicket 1.5.
Tom
On 06.02.2012 18:06, Thomas Singer wrote:
> I need help for converting our application from Wicket 1.4 to 1.5. We have
> following code:
>
> MarkupContain
its not unfortunate,its a good thing ,will help you in retrieving url
for dynamic resources.
yeah you can leave it as null for static package resources
On Mon, Feb 6, 2012 at 11:17 PM, Thomas Singer wrote:
> Unfortunately, a new parameter for PageParameters was added. Is passing null
> the same
Unfortunately, a new parameter for PageParameters was added. Is passing null
the same as in 1.4?
Tom
On 06.02.2012 18:29, vineet semwal wrote:
> RequestCycle#urlFor still exists,that needs to be corrected..
>
> On Mon, Feb 6, 2012 at 10:44 PM, Thomas Singer wrote:
>> According to https://cwiki
RequestCycle#urlFor still exists,that needs to be corrected..
On Mon, Feb 6, 2012 at 10:44 PM, Thomas Singer wrote:
> According to https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
>
> org.apache.wicket.RequestCycle.urlFor
>
> has been renamed to
>
> org.apache.wicket.request.cycle.Re
According to https://cwiki.apache.org/WICKET/migration-to-wicket-15.html
org.apache.wicket.RequestCycle.urlFor
has been renamed to
org.apache.wicket.request.cycle.RequestCycle.renderUrlFor
but there is no such method "renderUrlFor".
Tom
--
I need help for converting our application from Wicket 1.4 to 1.5. We have
following code:
MarkupContainer container = ...
...
MarkupStream markupStream = container.getMarkupStream();
if (markupStream == null) {
return null;
}
Class tagMarkupClass = markupStream.atTag
Hi Dan,
Thank you for your reply, I had resolved it by writing the below code
get("body").add(new AjaxEventBehavior("onload") {
/**
*
*/
private static final long seria
Hi, Raju. See if adding this to your Wicket component's constructor does
what you want:
add(new HeaderContributor(new IHeaderContributor() {
@Override
public void renderHead(IHeaderResponse response) {
response.renderOnDomReadyJavascript("alert('ready')");
}
}));
On Wed, Dec 7, 2011 at 8:25 PM, r
Hi,
On Wed, Nov 30, 2011 at 1:23 PM, Clint Checketts wrote:
> Right Martin, so your code allows me to select the children to refresh via
> Ajax.
>
> My question was how can trigger the logic processing in the ParentClass
> automatically. As you noted in the code, the child panels will have to
> r
Right Martin, so your code allows me to select the children to refresh via
Ajax.
My question was how can trigger the logic processing in the ParentClass
automatically. As you noted in the code, the child panels will have to
remember to call the parent.update(t) line. I'm fine with that solution,
b
Hi Clint,
I'd recommend to look in AjaxRequestTarget itself.
It has addChildren(parentInstance, Child.class) method with update all
children with type Child of this parent.
Check also AjaxRequestTarget.IListener.
Or add ParentClass#update(AjaxRequestTarget) so you can do:
AnotherClass#onEvent(ART
I want to create a parent panel that will have several child panels. I'm
making it so the parent panel will automatically add child components to
the AjaxRequestTarget via its logic and detecting which ones it detects
need to update. I can see how to make it work great if the AjaxLink calls
the par
ction=this.request.url + (this.request.url.indexOf("?")>-1 ? "&" :
"?") + "wicket:ajax=true";
form.method="post";
form.enctype="multipart/form-data";
form.encoding="multipart/form-data";
do you think this solution is fine? If it is, can this
no need, fixed in trunk (1.5.2)
-igor
2011/10/19 Yves-Marie LAINÉ :
> Ok. I'll try to check what happens in 1.5.1 in this case, and then create a
> ticket.
>
> Thanks !
>
> 2011/10/19 Martin Grigorov
>
>> Hi,
>>
>> 2011/10/19 Yves-Marie LAINÉ :
>> > Hi All,
>> >
>> > Yesterday, i wrote a Page t
Ok. I'll try to check what happens in 1.5.1 in this case, and then create a
ticket.
Thanks !
2011/10/19 Martin Grigorov
> Hi,
>
> 2011/10/19 Yves-Marie LAINÉ :
> > Hi All,
> >
> > Yesterday, i wrote a Page that need to ajax replace a component, so with
> > outputMarkupId at true. This componen
Hi,
2011/10/19 Yves-Marie LAINÉ :
> Hi All,
>
> Yesterday, i wrote a Page that need to ajax replace a component, so with
> outputMarkupId at true. This component has to know the markupId when
> onInitialize is called (depending of a component used by it that create a
> javascript)
>
> I know that
Hi All,
Yesterday, i wrote a Page that need to ajax replace a component, so with
outputMarkupId at true. This component has to know the markupId when
onInitialize is called (depending of a component used by it that create a
javascript)
I know that when we replace Components, the markupId of the r
any component can implement IMarkupResourceStreamProvider and return
whatever markup it wants wicket to use. If you need a fine-tuned
control over the caching mechanism for this markup you can also let
your components implement IMarkupCacheKeyProvider.
-igor
On Wed, Sep 28, 2011 at 8:05 PM, Brow
I remember we discussed it before:
http://apache-wicket.1842946.n4.nabble.com/Wicket-MashUpContainer-td1893282.html
2011/9/29 Brown, Berlin [GCG-PFS] :
> Does anyone have an article on how to add dynamic content such that the
> content isn't defined in the markup at compile time. It is generat
Does anyone have an article on how to add dynamic content such that the
content isn't defined in the markup at compile time. It is generated at
runtime.
For example.
Old Way - Listing1
...
With dynamic content - Listing2
...
I could use an offline, compil
A Wicket 1.4.17 application with its Filter mapped to /foo/* is being
redirect to root path after a form submit.
Does anyone have any idea on what can be going wrong?
Thanks
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Sun, Feb 27, 2011 at 7:56 PM, Fernando O. wrote:
>
> > Hi All
> > I've been trying to find the answer to my problems in Google but I
> couldn't
> > find it.
> >
> > I'm using wicket 1.4 rc2 (yeah, I suppose I should migrate to 1.5) but
> >
find the answer to my problems in Google but I couldn't
> find it.
>
> I'm using wicket 1.4 rc2 (yeah, I suppose I should migrate to 1.5) but
> anyway my problem is that I don't want wicket to cache my pages. Is there
> any way to do this?
> In fact what I would love
Hi All
I've been trying to find the answer to my problems in Google but I couldn't
find it.
I'm using wicket 1.4 rc2 (yeah, I suppose I should migrate to 1.5) but
anyway my problem is that I don't want wicket to cache my pages. Is there
any way to do this?
In fact what I wou
> Attach a web markup container to the body tag. Override
> isTransparentResolver and return true. This gets you a component that you
> can add to the ajax request target to repaint the entire body.
Thanks, I added a wrapping for it (since WicketPortlet strips out the
body tag) and it seemingl
> What if I try to extend org.apache.wicket.markup.html.basic.Label?
>
> Will it work when I extended MessageLabel?
Yes, except you need to be explicit about using a ResourceModel that
MessageLabel did for you. If you pass in the key as before then you just use
new ResourceModel(key) in the cal
the label i showed you does what the old message label did.
-igor
On Sun, Nov 21, 2010 at 11:43 PM, andrea.castello
wrote:
>
> Hi Igor, thanks for your answer, but I think it doesn't fit my situation.
> To explain better, I post the code similar to the class that must be changed
> in order to be
What if I try to extend org.apache.wicket.markup.html.basic.Label?
Will it work when I extended MessageLabel?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/MessageLabel-vanished-in-Wicket-1-4-x-tp3050632p3053186.html
Sent from the Users forum mailing list archive a
Hi Igor, thanks for your answer, but I think it doesn't fit my situation.
To explain better, I post the code similar to the class that must be changed
in order to be upgraded to 1.4.13.
---
import org.apache.wicket.markup.resolver.WicketMessageResolver.Mes
Attach a web markup container to the body tag. Override
isTransparentResolver and return true. This gets you a component that you
can add to the ajax request target to repaint the entire body.
Jeremy Thomerson
http://wickettraining.com
-- sent from my "smart" phone, so please excuse spelling, form
In the portlet context it is advantageous to just repaint one particular
portlet instead of the whole page when interacting with it. However, Pages do
not have Ajax-able DOM ids to use, since a Page generally handles the whole
HTML page in the non-portlet case. Calling target.addComponent(getPag
new Label("message", new ResourceModel("key"));
-igor
On Fri, Nov 19, 2010 at 8:33 AM, andrea.castello
wrote:
>
> Hello all,
>
> I've to upgrade a web application built on Wikcet 1.3.6 to wicket 1.4.13.
>
> In my webapp I have a class which extends
> WicketMessageResolver.MessageLabel.
> When I
1 - 100 of 539 matches
Mail list logo
