Hi,
On Wed, Jun 12, 2013 at 5:24 AM, grazia grazia.russolass...@gmail.comwrote:
I am using the wicket poi api to generate an excel file from a
PageableListView.
I just run into a bug in lines 67-76 of TableComponentAsXlsHandler.java:
cellExplorer becomes null already at the second
In trying to migrate from wicket 1.4 to 1.5, all my setResponsePage calls
get red in Eclipse. e.g:
setResponsePage(WelcomePage.class, parameters);
gets the error message:
The method setResponsePage(ClassC, PageParameters) in the type Component
is not applicable for the arguments
Hi,
The method is still there:
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/Component.java?source=cc#L3168
Try to build with javac/Maven or any other tool but Eclipse.
On Wed, Jun 12, 2013 at 2:22 PM, terjeeit terje.eit...@gmail.com wrote:
In trying
I created a quickstart but didn't create a ticket yet, because I found out
that ComponentRenderer expects to get a component whose markupId equals to
ComponentRenderer.COMP_ID.
Is this a bug or a feature? Is there some way to render the markup of an
existing component that has an arbitrary
Hi,
This can be relaxed. Please file a ticket.
On Wed, Jun 12, 2013 at 2:55 PM, harmoniaa
edvard.fons...@nitorcreations.com wrote:
I created a quickstart but didn't create a ticket yet, because I found out
that ComponentRenderer expects to get a component whose markupId equals to
Thanks, yeah I figured it was still there. It was the packet-structure that
didin`t update correctly. What before was:org.apache.wicket.PageParameters
is now: org.apache.wicket.request.mapper.parameter.PageParameters
appearently.
--
View this message in context:
Have you tried changing AjaxRequestAttributes#setAllowDefault(true) and
#setEventPropagation(BUBBLE) ?
Otherwise please create a quickstart so we can debug the problem.
Regards
Sven
On 06/12/2013 03:43 PM, divad91 wrote:
Anyone notice the same problem ?
Martin, thanks but I've already try that, and it does not work because
when ComponentTagwriteOutput() finally writes the attribute, it will
escape characters. Thanks anyway
On Tue, Jun 11, 2013 at 3:11 PM, Martin Grigorov mgrigo...@apache.org wrote:
Hi,
textField.setEscapeModelStrings(false)
I like the simplicity of Mockito and got it working in my unit tests, but now I
find myself mocking more services than I wanted.
Wicket Page Teste allows you to inject your mocks on top of the SpringBeans, is
that possible with Mockito?
http://WicketPageTest.sourceforge.net/
In other words I
Hi Paul,
Not sure if I got you right but you might check out:
https://bitbucket.org/kubek2k/springockito/wiki/Home
Best regards
Andi
2013/6/12 Paul Bors p...@bors.ws:
I like the simplicity of Mockito and got it working in my unit tests, but now
I find myself mocking more services than I
Thanks Sven, I had not tested the setEventPropagation(BUBBLE), only the
setAllowDefault(true).
It's working perfectly right now !
@Override
protected void updateAjaxAttributes(AjaxRequestAttributes attributes) {
attributes.setAllowDefault(true);
Hello,
I created a single page that shows some data using DataView. I then added a
form and allow a filter argument to be passed in. The problem I'm getting
is that the first time a search is done, the search value is added to the
URL for the page. Subsequent searches are ignored due to the query
I have a FormComponentPanel with an AjaxLink. The link's onClick() method
runs a database search based on criteria that are found in a half dozen
form fields (string, drop downs, etc.). My problem is that the form's
model is not updated because the link does not submit the form. And I
can't
Why not use two different forms, one for searching and the other for the
save fields?
You can even nest the first one into the other.
Sven
On 06/12/2013 09:09 PM, Richard W. Adams wrote:
I have a FormComponentPanel with an AjaxLink. The link's onClick() method
runs a database search based on
Well, first, HTML doesn't allow nested forms, per the w3.org site. Second,
the search fields need to be part of the overall form, because they (along
with the other fields) are persisted if the user presses the Save button.
From: Sven Meier s...@meiers.net
To: users@wicket.apache.org
On Wed, Jun 12, 2013 at 3:26 PM, Richard W. Adams rwada...@up.com wrote:
Well, first, HTML doesn't allow nested forms, per the w3.org site. Second,
the search fields need to be part of the overall form, because they (along
with the other fields) are persisted if the user presses the Save
Hi guys,
My name is Mike Pence. I think that I have dipped into this list a time or two
in the past, but I am here, this time, with serious intent to use Wicket for a
very big project -- big both in terms of how many users it will have, and big
in its impact.
I have been doing Rails for the
Hi,
I am a Wicket user since v1.3. The main application I develop using it is
SRMvision (free trial available at demo.srmvision.com, slow because of the
virtual machine that sits under). We have leveraged the component nature of
Wicket to apply good practices and it has proven being a very good
I found a solution that worked.
I didn't realize that by adding the value passed in to a PageParameters
object and then setting the response page I was telling Wicket to add that
to the URL. I got rid of that.
I changed my form to this use the CompoundPropertyModel:
Form? form = new
Ok thanks again for helping out! :)
Well I found that 'options.$trigger.attr(id)' from parameters returns id
of link pressed (did not try yet on wicket side, but I think it should work)
and 'key' returns which context menu was pressed. Now my links represents
users and context menu some actions to
Wicketeers,
I'm attempting to develop a reusable context menu component. I'm nearly there,
but having a few issues, and thought I might share in the hope I might get some
help. I realise that another person (bronius) is also having a go at this, but
his implementation isn't using
21 matches
Mail list logo
