It still return Non-English version of Calendar even if I try
Locale.English / Locale.US
DatePickerSettings settings = new DatePickerSettings();
settings.setLanguage(DatePickerSettings.getLanguageFromMap(Locale.ENGLISH));
TextField dateField = new TextField(birthDay, new
PropertyModel(account,
That would be:
/**
* The format string that will be used to enter the date in the input
field.
* This format will be honored even if the input field is hidden. Use
* Javascript notation, like '%m/%d/%Y'.
*/
private String ifFormat =
Yes the stateless things are almost in 1.3. I need to finish it up a bit more.I don't know about the final of 1.3 but i guess we can have a beta of 1.3 pretty soon.johan
On 11/10/06, Scott Swank [EMAIL PROTECTED] wrote:
Will Wicket 1.3 have the full stateless functionality of 2.0?If not,what
When I create a page, and this page generate this html code:
script type=text/javascript !--/*--![CDATA[/*!--*/
if (window.name=='') {
window.location=/quickstart/app?wicket:interface=:1::INewBrowserWindowListener;
}
/*--]]*//script
Now, I add a button in the page (a very simple page):
It worked well until I pass parametr with %2F ('/') . The problem is that
HttpServletRequest.getPathInfo() returns the URL that is already decoded
(checked with Jetty 6 and Tomcat 5.5). For nice URLs the getRequestURI() or
getRequestURL() should be used, it seems to return the request as it was
In my case, I have created a TextField component, that is a panel that
contains internally a TextField wicket component. Now, if I add the
method addToField, the user will have two methods:
TextField.add(IBehavior behavior)
TextField.addToField(IBehavior behavior)
I think that this case
Hello all !
I would like to add a CompoundPropertyModel as wizard static page. I have done
so far:
public class StepX extends StaticContentStep {
/**
* Constructor.
*
* @param userModel
*/
public StepX(UserModel userModel)
{
You need to create a Label in the constructor of the given part that passes
the information to it.
e.g:
add(new Label(userModel.userName, userModel.getUserName));
BTW: you can change the Labelname to whatever you want as its not associated
with the content behind it.
e.g:
add(new Label(username,
What version of Wicket do you use?
Regards
Korbinian
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag
von Alberto Bueno
Gesendet: Freitag, 10. November 2006 10:35
An: wicket-user@lists.sourceforge.net
Betreff: [Wicket-user] Problem in
The trunk
What version of Wicket do you use?
Regards
Korbinian
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag
von Alberto Bueno
Gesendet: Freitag, 10. November 2006 10:35
An: wicket-user@lists.sourceforge.net
Betreff:
2.0 ?
or
1.x ?
(sorry, dont know whats in Trunk at the moment you got it)
you might want to use wicket 1.2.3 as this hasnt the behaviour so far...
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag
von Alberto Bueno
Gesendet: Freitag, 10.
If you want to use a CompoundPropertyModel you can do something like the
following in the constructor of the component:
setModel(new CompoundPropertyModel(...)); // where ... is either your
POJO or another model
add(new Label(userModel.userName));
Leave the html unchanged.
Because you did
Hello,
Something is going wrong with my header contributions. A css that was
added like this
add(HeaderContributor.forCss(MyPage.class, MyPage.css));
are only rendered once and then never again.
To be precise:
- I start jetty.
- I request the page (it is bookmarkable).
- I get redirected to
add a bug into jira preferrably with a quickstart-igorOn 11/10/06, Erik van Oosten [EMAIL PROTECTED]
wrote:Hello,Something is going wrong with my header contributions. A css that was
added like thisadd(HeaderContributor.forCss(MyPage.class, MyPage.css));are only rendered once and then never
add a bug into jira with your quickstart-igorOn 11/10/06, Korbinian Bachl [EMAIL PROTECTED]
wrote:2.0 ?or1.x ?(sorry, dont know whats in Trunk at the moment you got it)
you might want to use wicket 1.2.3 as this hasnt the behaviour so far... -Ursprüngliche Nachricht- Von: [EMAIL
Wicket can't do that getParameter conversionIt is tomcats stupid thing that you need to configure that extra in the connector configuration.Others don't have to do that and do follow everything with the encoding the browser sends in.
So if you yourself want to do that then implement your own
On 11/10/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
add a bug into jira preferrably with a quickstart
Or maybe even better a unit test that proves this and that we can put in wicket.
Eelco
-
Using Tomcat but need to do
Ok, I'll try to extract the problem.
Erik.
Eelco Hillenius schreef:
On 11/10/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
add a bug into jira preferrably with a quickstart
Or maybe even better a unit test that proves this and that we can put in
wicket.
Eelco
--
Erik
Yeah. Erik, I see your point for the general case, but Alberto's case
- which I have myself sometimes too - is that you only use a panel
because you have to, but you want the user to view your component as
one of it's embedded elements (in his case the TextField). I think
that's a valid case.
So,
Excellent. We're beginning our big new public web app in the next
month or so and there have been questions about stateless options in
Wicket. It will eventually be a complete rewrite of the web layer for
www.vegas.com. We're considering Wicket Facelets (i.e. JSF).
We can get (nearly) valid
Sounds cool. Good luck!
Alternatively, you could consider 2.0, but that depends on how long
your project will take.
Eelco
On 11/10/06, Scott Swank [EMAIL PROTECTED] wrote:
Excellent. We're beginning our big new public web app in the next
month or so and there have been questions about
I cant notice this behaviour with wicket 1.2.3 so far -
under 1.2.2 i have cases where the JS part misses, not so more under
1.2.3...
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Igor
VaynbergGesendet: Freitag, 10. November 2006 17:57An:
Thanks. The six month time frame on 2.0 probably means that if we go
with Wicket it'll be 1.3 and then an upgrade to 2.0.
On 11/10/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Sounds cool. Good luck!
Alternatively, you could consider 2.0, but that depends on how long
your project will take.
So if you yourself want to do that then implement your own webrequest
Good point... I guess I can extend WebRequest and tell Wicket to use
that... but Can I do similar think for WebResponse?
Yes, in fact doing that making the application hard, or may be
impossible to run at other web container,
Sorry for the misguidance there. Something like this works:
final DateFormat fmt = new
SimpleDateFormat(-MM-dd);
final DateConverter dateConverter = new DateConverter()
{
public DateFormat
Eelco Hillenius wrote:
But as you got from the answers on this thread, URL based
authorization schemes in not something we recommend for Wicket. It'll
basically bring you back to page-level development again, whereas the
whole point of Wicket is to provide a component based paradigm.
We (Martijn and me) spoke there last year, but after doing a couple of
presentations the last year, we're out of time and energy (and money!)
to keep on doing that. We might get more active again in 2007.
But... everyone is more than welcome to take up the initiative, so if
any of you Wicket
I have a custom label component that extends label. In the constructor
it takes a form component that I want it to check if isRequired() at
render time and append * to the text of the label. What would be the
easiest way to do this? The data for the label could be passed in
through various models,
Something like this?
class MyLabel extends Label {
private String text;
public MyLabel(String id, String text, final FormComponent fc) {
super(id, new AbstractReadOnlyModel() {
Object getObject(Component component) {
return text + (fc.isRequired() ? * : );
Probably the easiest thing to do is extend WebComponent instead of
label. Label is a super simple component really. This
protected void onComponentTagBody(final MarkupStream markupStream,
final ComponentTag openTag)
{
replaceComponentTagBody(markupStream, openTag,
That's a good alternative too.
Eelco
On 11/10/06, Erik van Oosten [EMAIL PROTECTED] wrote:
Something like this?
class MyLabel extends Label {
private String text;
public MyLabel(String id, String text, final FormComponent fc) {
super(id, new AbstractReadOnlyModel() {
Thanks for both of your replys!
I think extending WebComponent is the way I'll do it as then I don't
care about the type of model that gets used...
Thanks again!
Cheers,
-js
On 11/10/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Probably the easiest thing to do is extend WebComponent instead
Yeah. There are just multiple problems with URL based authorization.
It works fine for document-oriented sites, but how long ago was it
when we were building those :)
Take for example the use case that you want to hide a panel - but show
the rest of the page - when a user is not authorized for
Hi Rik,
We use Acegi because of its excellent backend features. We do not use
Acegi to do authorization in the frontend, we just give a
username/pasword and ask it for the roles. Acegi gets it out of LDAP for
us, wicket-auth-roles does the authorization. The Acegi filter sets the
Is it possible to take a component such as a Button and make it a
child of a new component so as to wrap it?
class MyPage extends WebPage {
add(new Button(myButton));
public void onBeforeRender() {
visitChildren(new MyVisitor());
}
}
class MyVisitor
您好!
我公司是深圳市税务代理有限公司。我公司现有各种财务所用票据（普通国税发票，地税发票，增值税发票，海关专用缴款书）可以向外优惠代开。欢迎贵公司来电咨询，希望我们有共同合作的机会。如有打扰，请原谅。谢谢！
联系电话：13714839618
联系人：林先生
[EMAIL PROTECTED]
-
Using Tomcat but need to do more?
Ok i committed everything delayed sessions, stateless pages (stateless link and form) andthe SecondLevelCacheStore is now in the 1.3 branch.please start testing :)what more do we want in 1.3 from 2.0?
johanOn 11/10/06, Johan Compagner [EMAIL PROTECTED] wrote:
Yes the stateless things are almost in
not at that time. during the render phase you are not allowed to modify component hierarchy. try doing it in onattach instead.in 2.0 you will need to use a different pattern - we havent built the reparenting mechanism in
2.0 yet - still figuring out what the simplest way is.-igorOn 11/10/06,
Yipee!
Eelco
On 11/10/06, Johan Compagner [EMAIL PROTECTED] wrote:
Ok i committed everything delayed sessions, stateless pages (stateless link
and form) and
the SecondLevelCacheStore is now in the 1.3 branch.
please start testing :)
what more do we want in 1.3 from 2.0?
johan
On
Very cool, I'll have to get Maven set up and give 1.3 a whirl. This
is certainly marvelous timing as far as I'm concerned.
On 11/10/06, Johan Compagner [EMAIL PROTECTED] wrote:
Ok i committed everything delayed sessions, stateless pages (stateless link
and form) and
the SecondLevelCacheStore
Hi Erik,
Yes. So you mean in short: use Acegi for authentication and use
wicket-auth-roles for authorization. That is a good compromise
because you get some of the features of Acegi out-of-the-box, like a
LDAP-server authentication as you mention.
Questions;
Do you use a normal login form
41 matches
Mail list logo
