I believe https://issues.apache.org/jira/browse/WICKET-5585 is related.
Do you use Wicket 6.16.0 ?
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 4:00 AM, smallufo small...@gmail.com wrote:
sorry , There is no stack trace.
Because it
Hi,
Portlets is grey area for me...
When the problem started appearing ? With Wicket 6.16 or earlier ?
There are no changes in wicketstuff-portlet since a while so I guess it is
a change in Wicket that may broke it.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
Hi,
I am not able to obtain the wicketsession even though sessionFilter has been
added
My requirement
1. Click of button on Page 1 (url : http://localhost:7001/abc/def/). open
editable Pdf form in new window.
2. on click of submit present on pdf form , call a servlet (configured at
I'll try to downgrade step by step. Until recently I didn't use wicket in
portal environment. All I know is that with wicket 1.5 (tested until 1.5.9)
my library was ok in Liferay 6.1. In the mean time I upgraded my library to
wicket 6 but it seems that was not a wise decision :) . I'll post my
Seems that in 6.10.0 to 6.12.0 the url for my AjaxLink is ok
What about 6.11.0 ?
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 12:55 PM, Ciocoiu Elvis elvis.cioc...@everlight.ro
wrote:
Seems that in 6.10.0 to 6.12.0 the url for my AjaxLink is ok
https://github.com/wicketstuff/core/issues/172
this sounds like related but the change has been made in an earlier version
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 1:11 PM, Martin Grigorov mgrigo...@apache.org
wrote:
What about
Yes , I am using 6.16.0
properties
wicket.version6.16.0/wicket.version
wicket-bootstrap.version0.9.4/wicket-bootstrap.version
yuicompressor.version2.4.7/yuicompressor.version
/properties
2014-07-08 14:56 GMT+08:00 Martin Grigorov mgrigo...@apache.org:
I believe
In 6.10, 6.11, 6.12 the url is rendered ok. In 6.13, 6.14, 6.15, 6.16 the
url is wrong.
On Tue, Jul 8, 2014 at 1:17 PM, Martin Grigorov mgrigo...@apache.org
wrote:
https://github.com/wicketstuff/core/issues/172
this sounds like related but the change has been made in an earlier version
Then you will have to debug what happens ...
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 1:28 PM, smallufo small...@gmail.com wrote:
Yes , I am using 6.16.0
properties
wicket.version6.16.0/wicket.version
I have also added Session.get().bind() on page 1.. that also doesnt help
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Not-able-to-get-Wicket-Session-even-though-WicketSessionFilter-has-been-added-tp4666469p4666476.html
Sent from the Users forum mailing list
Oh, sorry.
I read that it is OK in 6.10 and not OK in 6.12.
Here is the changelog for 6.13.0 -
https://issues.apache.org/jira/issues/?jql=project%20%3D%20WICKET%20AND%20fixVersion%20%3D%206.13.0
There are few tickets related to statelessness of the page. I'm not sure
whether it is related but it
Hi,
Put a breakpoint in WicketSessionFilter#doFilter() and see what happens.
Is it called at all ? Is there Session thread local ? Etc.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 1:46 PM, rsi610 rahul.i...@lntinfotech.com wrote:
I
I think I found the problem ... in wicket 6.13
Component.urlFor(final Behavior behaviour, RequestListenerInterface
listener, final PageParameters parameters)
the decision to use BookmarkableListenerInterfaceRequestHandler
or ListenerInterfaceRequestHandler is different from wicket 6.12 where
On Tue, Jul 8, 2014 at 1:58 PM, Ciocoiu Elvis elvis.cioc...@everlight.ro
wrote:
I think I found the problem ... in wicket 6.13
Component.urlFor(final Behavior behaviour, RequestListenerInterface
listener, final PageParameters parameters)
the decision to use
If i use
Application.getPageSettings().setRecreateMountedPagesAfterExpiry(false) my
AjaxLink works but I\m not sure about the implications. Is the
Component.urlFor(...) implementation in wicket 6.13 the correct one?
Thank you
On Tue, Jul 8, 2014 at 1:58 PM, Ciocoiu Elvis
It is the best we have at the moment.
Suggestions how to make it better for Portlets are welcome!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 2:13 PM, Ciocoiu Elvis elvis.cioc...@everlight.ro
wrote:
If i use
Maybe BookmarkableListenerInterfaceRequestHandler should be handled also in
PortletRequestHandler similar to how ListenerInterfaceRequstHandler is
encoded (the BookmarkableListenerInterface... now is just ignored and
mapHandler returns the url without encoding it for portal environment).
Anyway,
Sounds as the Solution !
Play with it and send a Pull Request to https://github.com/wicketstuff/core
if it helps.
Thanks!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 2:28 PM, Ciocoiu Elvis elvis.cioc...@everlight.ro
wrote:
Maybe
Sorry , because the server receives no event.
There is no debug output.
I think it is easy to replicate the error.
just fork bootstrap-samples :
https://github.com/l0rdn1kk0n/wicket-bootstrap/tree/master/bootstrap-samples
and add
LoginModal code :
http://pastebin.com/0qGUFvXP
And the
Sorry, but I have no time to create a demo application for every user with
a problem.
The user should help us a bit too!
Please create a full demo app and explain the steps to reproduce.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 3:32
Hi Lucas,
I think it's a bug, because in my case I have a from when i set values of
some component, then i execute ajaw event to submit the form, wickettester
execute what i want, but after that if i submit the form with
formTester.submit('path'); i'm getting the same the result as if clicked on
-- Forwarded message --
From: Michael Haitz michael.ha...@agilecoders.de
Date: Tue, Jul 8, 2014 at 6:04 PM
Subject: Wicket Bootstrap 0.9.5 is released
To: wicket-bootst...@googlegroups.com
Hi,
Wicket Bootstrap 0.9.5 has been released and soon will be available at
Maven Central.
Hello, I am getting an error:
Missing artifact org.apache.wicket:wicket:pom:6.15.0:compile
This is when I try to update to 6.15.0 from 1.5.5 .. I also get it for
slf4j.. Here are the two errors together:
7/8/14 11:01:51 AM CDT: Missing artifact
org.apache.wicket:wicket:pom:6.15.0:compile
Add
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version${wicket.version}/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-api/artifactId
Hi,
I can see the pom at
http://central.maven.org/maven2/org/apache/wicket/wicket/6.15.0/
Not sure why it fails to resolve.
But as Francois suggested - just use wicket-core:jar instead.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 7:03
I added those, and I still get this:
7/8/14 1:01:35 PM CDT: Refreshing [/sampleproject/pom.xml]
7/8/14 1:01:35 PM CDT: [WARN] Missing POM for
org.apache.wicket:wicket:pom:6.15.0
7/8/14 1:01:35 PM CDT: Downloading
Remove the pom dependency.
wicket-core:jar is enough.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 9:02 PM, eaglei22 jchojnack...@gmail.com wrote:
I added those, and I still get this:
7/8/14 1:01:35 PM CDT: Refreshing
Actually I took out:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket/artifactId
version${wicket.version}/version
typepom/type
/dependency
Which I had left
On Tue, Jul 8, 2014 at 9:05 PM, eaglei22 jchojnack...@gmail.com wrote:
Actually I took out:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket/artifactId
version${wicket.version}/version
I don't understand why it keeps asking for it. If I take it out it's still
looking for it, and when I change to slf4j.version1.6.4/slf4j.version
I get more errors:
7/8/14 1:15:36 PM CDT: Missing artifact
org.slf4j:slf4j-api:jar:${slf4j-api.version}:compile
7/8/14 1:15:36 PM CDT: Missing artifact
slf4j-api.version != slf4j.version
read carefully
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Jul 8, 2014 at 9:16 PM, eaglei22 jchojnack...@gmail.com wrote:
I don't understand why it keeps asking for it. If I take it out it's still
looking for it,
Ah okay, sorry about that. That def makes more sense now. I wasn't 100% sure
how to even read the pom but it makes a lot more sense now.
I still get the error:
Missing artifact org.slf4j:slf4j-api:jar:1.6.4:compile
using:
properties
wicket.version6.15.0/wicket.version
I have gotten all the latest jars installed for the Wicket 6.15. I can verify
this in the Maven Dependencies directory.
For some reason, I feel it is still pointing to an older version of Wicket.
I am getting strange errors with the add method from the MarkupContainer.
Using the quick-start
WicketSessionFilter gets called..Also it has a session with it.
http://apache-wicket.1842946.n4.nabble.com/file/n4666503/WicketSession.jpg
--
View this message in context:
35 matches
Mail list logo