There might be breaking changes with Modals. Not sure if you provide support
for the remote function of the Bootstrap Modals.
Marvin Richter
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Wednesday, February 05, 2014 8:54 AM
To: users@wicket.apache.org
Sub
Hey thanks ya sorry i re-edited my post.
But helps. .. never tried using panels in Headers. It failed for me sometime
so I assumed its not the right thing
thanks again, will try it
-
Software documentation is like sex: when it is good, it is very, very good; and
when it is bad, it
Hi,
I'm during migration from Wicket 1.4.x to 6.x and I have the following
problem with WicketTester.
I have some secured page, during its initialization some kind of
AuthorizationException is raised. It should end with displaying standard
AccessDeniedPage. Here is a code fragment from test case:
Try with tester.setExposeExceptions(false) before making the request to the
secured page
Martin Grigorov
Wicket Training and Consulting
On Wed, Feb 5, 2014 at 10:33 AM, Daniel Stoch wrote:
> Hi,
>
> I'm during migration from Wicket 1.4.x to 6.x and I have the following
> problem with WicketTest
It works!
Thanks for your fast replay :)
--
Daniel
On Wed, Feb 5, 2014 at 10:40 AM, Martin Grigorov wrote:
> Try with tester.setExposeExceptions(false) before making the request to the
> secured page
>
> Martin Grigorov
> Wicket Training and Consulting
>
>
> On Wed, Feb 5, 2014 at 10:33 AM, Dan
For fast REPLY, of course ;)
On Wed, Feb 5, 2014 at 10:45 AM, Daniel Stoch wrote:
> It works!
> Thanks for your fast replay :)
>
> --
> Daniel
>
>
> On Wed, Feb 5, 2014 at 10:40 AM, Martin Grigorov wrote:
>
>> Try with tester.setExposeExceptions(false) before making the request to
>> the
>> secu
One more question: what is a difference between these two calls:
1.
tester.startPage(DummyBasePage.class);
Result result = tester.isRenderedPage(DummyBasePage.class);
2.
tester.getRequestCycle().setResponsePage(DummyBasePage.class);
tester.processRequest();
Result result = tes
#processRequest() triggers a new request to the "server"
so first the page is rendered, then a new request to the default
destination is made, so the home page is rendered and "lastRenderedPage"
changes
Martin Grigorov
Wicket Training and Consulting
On Wed, Feb 5, 2014 at 11:39 AM, Daniel Stoch
Ok, but what I should call to render DummyBasePage after calling:
tester.getRequestCycle().setResponsePage(DummyBasePage.class);
without making a new request?
--
Daniel
On Wed, Feb 5, 2014 at 12:01 PM, Martin Grigorov wrote:
> #processRequest() triggers a new request to the "server"
> so firs
You should not use tester.getRequestCycle().setResponsePage(DummyBasePage.
class);
You should do something like:
- in the test code: tester.startPage(Page1.class)
- in your real application code: Page1 or in its components you can use
setResponsePage(Page2.class)
- finally in the test code: teste
Thanks ..so using Panels in the did work out fine. .. using
container !
Though; I want to put custom variables in the META tags; I found it more
complex it to do via Wicket.
Rather used Velocity to accept a MAP of Attributes and generate the META
TAGS and pass that into a FRAGMENT seemed scalable
My panel had all meta tags for all possible data.
Each page constructs some data (a model) depending on the current
functionality.
Then the panel uses the model to populate some of the meta tags and to set
invisible all without data for them.
Martin Grigorov
Wicket Training and Consulting
On Wed
In my real application there are calls to RequestCycle.setResponsePage(...)
which are hidden by more advanced action/navigation framework. So I cannot
simply replace them by component.setResponsePage().
I think that if RequestCycle.setResponsePage(...) is valid for real
application, it should also
Component#setResponsePage() just delegates to
RequestCycle#setResponsePage(). So it is the same.
I'm saying that you should not use tester.getRequestCycle().xyz(). I.e. do
not set the new page in the test code. Set it in the real application code.
Martin Grigorov
Wicket Training and Consulting
Hi there,
I’d like to add something to the AjaxRequestTarget "at the very end“, i.e. I
need to be the last one to add something to the target (because I need to check
some preconditions that might change if the target is manipulated later on).
Reading the Javadoc of
org.apache.wicket.ajax.Ajax
Hi,
org.apache.wicket.ajax.AjaxRequestTarget.IListener#onBeforeRespond() is
called after the action phase (e.g. onEvent, onSubmit) and before the
rendering.
Sounds like what you need.
Martin Grigorov
Wicket Training and Consulting
On Wed, Feb 5, 2014 at 4:09 PM, Tom Götz wrote:
> Hi there,
>
Ok, I was misinterpreting the Javadoc of
org.apache.wicket.ajax.AjaxRequestTarget.IListener#onBeforeRespond: "Triggered
before ajax request target begins its response cycle“. That sounded to me as it
was called *before* the action phase …
Thanks for the hint, I will try that.
Cheers,
-Tom
Hi Everyone,
I maintain a Wicket application running on Tomcat 7.0.39, and I recently
altered $TOMCAT_HOME/conf/context.xml to include a sessionCookieName
parameter. I made a change like this:
This properly changes the session cookie that is used by Wicket to
JESSIONID_MYAPP instead of JS
On Wed 05.02.2014 13:12, Aaron J. Garcia wrote:
> Hi Everyone,
>
> I maintain a Wicket application running on Tomcat 7.0.39, and I recently
> altered $TOMCAT_HOME/conf/context.xml to include a sessionCookieName
> parameter. I made a change like this:
>
>
>
> This properly changes the session c
Timo Schmidt xomit.de> writes:
>
> On Wed 05.02.2014 13:12, Aaron J. Garcia wrote:
> > Hi Everyone,
> >
> > I maintain a Wicket application running on Tomcat 7.0.39, and I recently
> > altered $TOMCAT_HOME/conf/context.xml to include a sessionCookieName
> > parameter. I made a change like this
Use a system property :
System.setProperty("wicket.jsessionid.name", "JSESSIONID_MYAPP");
François Meillet
Formation Wicket - Développement Wicket
Le 5 févr. 2014 à 22:05, Aaron J. Garcia a écrit :
> Timo Schmidt xomit.de> writes:
>
>>
>> On Wed 05.02.2014 13:12, Aaron J. Garcia wrote:
Hey guys,
hope you can help me with this.
I’m currently in the preparation phase of a new Project and evaluating possible
technologies.
What I already know: the Web part will be done with Wicket.
The application will be some kind of management tool for others applications
configuration.
To sup
Hi,
Look in the archives for "plugin" and "IInitializer".
Wicket's IInitializer is very simple solution for this.
Also Decebal Suiu have implemented https://github.com/decebals/wicket-plugin
Martin Grigorov
Wicket Training and Consulting
On Wed, Feb 5, 2014 at 11:17 PM, Richter, Marvin <
marvin
Hi,
I will test this tomorrow.
Martin Grigorov
Wicket Training and Consulting
On Wed, Feb 5, 2014 at 11:09 PM, Francois Meillet <
francois.meil...@gmail.com> wrote:
> Use a system property :
> System.setProperty("wicket.jsessionid.name", "JSESSIONID_MYAPP");
>
>
> François Meillet
> Formation
Martin Grigorov apache.org> writes:
> Hi,
>
> I will test this tomorrow.
>
> Martin Grigorov
> Wicket Training and Consulting
Thanks Martin,
FWIW, I was setting this when running Tomcat:
-Dwicket.jsessionid.name=JSESSIONID_MYAPP
It didn't work with the -D option, so I added it to my class
Hello
What's the difference of PF4J and osgi ?
On Feb 6, 2014 6:37 AM, "Martin Grigorov" wrote:
> Hi,
>
> Look in the archives for "plugin" and "IInitializer".
> Wicket's IInitializer is very simple solution for this.
> Also Decebal Suiu have implemented
> https://github.com/decebals/wicket-plugi
Thanks Martin,
sometimes I’m astonished how fast you reply … ;)
The wicket-plugin project is exactly what I was looking for.
Am 05.02.2014 um 23:37 schrieb Martin Grigorov :
> Hi,
>
> Look in the archives for "plugin" and "IInitializer".
> Wicket's IInitializer is very simple solution for this
Hi users@,
My name is Lewis, I am a committer over on Apache Nutch. I'm writing to the
users@ list in an attempt to interest students in participating in this
years GSoC[0].
The idea is to create a Wicket-based Web Application for Nutch as a GSoC
project.
For those that might be interested, the pro
I am having this same issue in wicket 6.13.0. Any fixes as of yet?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/tinymce-textarea-in-a-modal-window-not-letting-to-type-tp1886534p4664214.html
Sent from the Users forum mailing list archive at Nabble.com.
-
29 matches
Mail list logo
