Re: [ANNOUNCE] Apache Wicket 1.3 released
yeah, baby, yeah!!! way to go everyone! Martijn Dashorst-4 wrote: > > Starting the new year with a bang the Wicket Team has released Apache > Wicket 1.3. With this release comes a lot of great successes, but most > of all the team wanted to express their wishes to everyone for a happy > new year. > > You can download Apache Wicket 1.3 here: > > http://wicket.apache.org/getting-wicket.html > > Apache Wicket is one of the fastest growing Java open source component > based web frameworks. With a focus on producing valid html and a > logical separation between design and code. Within minutes you can > start to enjoy throwing out tag soup, complex components and high > maintenance overhead for a simple POJO + html data model. > > See the Apache Wicket website for more information: > > http://wicket.apache.org > > Take a look at some of the following highlights or skip to the bottom > and get started now. > > * last JDK-1.4 release (next release will be Java 5 based) > * first Apache release: renamed packages to org.apache.wicket > * simplified several core APIs > * now works with zero-config behind a proxy server using relative URLs > * added Google Guice support > * use your Wicket pages directly in a portal without changing a line > of code (JSR-168/JSR-286 support) > * switched logging API from commons-logging to slf4j > * integrate velocity templates as panels in your pages > * YUI-calendar and Joda time based date picker (wicket-datetime) > * contribute new javascript dependencies to the page header using an > Ajax requeset > * improved, more robust header contributions > * scale to extremely large numbers of users with stateless pages and > components > * improved AjaxTree/AjaxTreeTable > * hybrid URL encoding to make search engines and your users happy > * create form panels and use them anywhere without worrying about the > nesting of form tags > * minimized session use by storing component hierarchy in file system > (DiskPageStore) > > Get started today by downloading Wicket using this link: > > http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 > > The distribution contains all the Wicket libraries, and all the source > code including the examples project. In the root of the download you > will find a README document with full instructions. > > Migrate your Wicket 1.2 application to Wicket 1.3 using our migration > guide: > > http://cwiki.apache.org/WICKET/migrate-12.html > > Best wishes from the Wicket Team and a prosperous 2008! > > - The Wicket Team > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-ANNOUNCE--Apache-Wicket-1.3-released-tp14585070p14593193.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCE] Apache Wicket 1.3 released
Congratulations on this release. 1.4 in february? Alex On Jan 2, 2008 11:56 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > Starting the new year with a bang the Wicket Team has released Apache > Wicket 1.3. With this release comes a lot of great successes, but most > of all the team wanted to express their wishes to everyone for a happy > new year. > > You can download Apache Wicket 1.3 here: > >http://wicket.apache.org/getting-wicket.html > > Apache Wicket is one of the fastest growing Java open source component > based web frameworks. With a focus on producing valid html and a > logical separation between design and code. Within minutes you can > start to enjoy throwing out tag soup, complex components and high > maintenance overhead for a simple POJO + html data model. > > See the Apache Wicket website for more information: > >http://wicket.apache.org > > Take a look at some of the following highlights or skip to the bottom > and get started now. > > * last JDK-1.4 release (next release will be Java 5 based) > * first Apache release: renamed packages to org.apache.wicket > * simplified several core APIs > * now works with zero-config behind a proxy server using relative URLs > * added Google Guice support > * use your Wicket pages directly in a portal without changing a line > of code (JSR-168/JSR-286 support) > * switched logging API from commons-logging to slf4j > * integrate velocity templates as panels in your pages > * YUI-calendar and Joda time based date picker (wicket-datetime) > * contribute new javascript dependencies to the page header using an > Ajax requeset > * improved, more robust header contributions > * scale to extremely large numbers of users with stateless pages and > components > * improved AjaxTree/AjaxTreeTable > * hybrid URL encoding to make search engines and your users happy > * create form panels and use them anywhere without worrying about the > nesting of form tags > * minimized session use by storing component hierarchy in file system > (DiskPageStore) > > Get started today by downloading Wicket using this link: > >http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 > > The distribution contains all the Wicket libraries, and all the source > code including the examples project. In the root of the download you > will find a README document with full instructions. > > Migrate your Wicket 1.2 application to Wicket 1.3 using our migration > guide: > >http://cwiki.apache.org/WICKET/migrate-12.html > > Best wishes from the Wicket Team and a prosperous 2008! > > - The Wicket Team > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Ways of making components in a page optional?
On Wed, 02 Jan 2008, Paolo Di Tommaso wrote:
> An easy trick to avoid this is to use a Panel/Fragment instantiating just a
> WebMarkupContainer when you don't want to display/create the full component.
Ah, you mean something like
add(new WebmarkupContainer("myComplexComponent"));
at construction and then later on
replace(new MyComplexComponent("myComplexComponent"))
?
That's an interesting idea, thanks!
Best wishes,
Timo
--
Timo Rantalaiho
Reaktor Innovations Oyhttp://www.ri.fi/ >
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: MyWebApplication, SpringWebApplication + AuthenticatedWebApplication
The wiki has a section on spring integration. You put a line in your app's
init() method to accomplish this. It should be easy to find.
-Original Message-
From: Korbinian Bachl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 02, 2008 1:44 PM
To: users@wicket.apache.org
Subject: MyWebApplication, SpringWebApplication +
AuthenticatedWebApplication
Hi,
usually my WebApp is based on Wicket-Auth-Roles, so I do:
MyWebApp extends AuthenticatedWebApplication {
Lately I played around with spring 2.5 a bit and so used
MyWebApp extends SpringWebApplication {
but how can I now integrate a SpringWebApplication to use Wicket-Auth-Roles?
The only way I currently see is to copy'n paste the content of the
SpringWebApplication into MyWebApp and let it extend
AuthenticatedWebApplication - but copy'n paste is not my preferable way
however...
Any ideas?
Best,
Korbinian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
MyWebApplication, SpringWebApplication + AuthenticatedWebApplication
Hi,
usually my WebApp is based on Wicket-Auth-Roles, so I do:
MyWebApp extends AuthenticatedWebApplication {
Lately I played around with spring 2.5 a bit and so used
MyWebApp extends SpringWebApplication {
but how can I now integrate a SpringWebApplication to use Wicket-Auth-Roles?
The only way I currently see is to copy'n paste the content of the
SpringWebApplication into MyWebApp and let it extend
AuthenticatedWebApplication - but copy'n paste is not my preferable way
however...
Any ideas?
Best,
Korbinian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCE] Apache Wicket 1.3 released
Congratulations to the Wicket team for an outstanding job! We have just released our first product based on Wicket 1.2.6 and we are hard at work on the next version, based on 1.3. Julian -- View this message in context: http://www.nabble.com/-ANNOUNCE--Apache-Wicket-1.3-released-tp14585070p14587048.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DropDownChoice with -1 value
If you create a properties file for the page class and use dot notation
matching your page hierarchy but leave the last value as null you can set
the default value:
For example:
theForm.birthdayMonth.null=M
theForm.birthdayYear.null=Y
theForm.birthdayDay.null=D
See if that helps..
J
On Jan 2, 2008 2:14 PM, Juliano Gaio <[EMAIL PROTECTED]> wrote:
> Hello Everybody
>
> I'm using wicket.markup.html.form.DropDownChoice and it
> works fine until now, when I got a suspicious behavior (maybe bug)
>
> Into database I have one data called "TEMP CUSTOMER" that has
> id = -1 (it's business logic of our client, that data came through
> database importation, and I can not update that data)
>
> Following my code:
>
> List relations = relationManager.list();
> final DropDownChoice ddRelations = new DropDownChoice("relation", (
> task.getRelation() == null) ? new Model() : new Model(task.getRelation()),
> relations, new IChoiceRenderer() {
>public Object getDisplayValue(Object object) {
> return ((Relation) object).getName();
>}
>public String getIdValue(Object object, int index) {
> return String.valueOf(((Relation) object).getId());
>}
> });
> form.add(ddRelations);
>
>
> and HERE is the source code generate on html :
>
>
> Choose one
> TEMP CUSTOMER
> CUSTOMER 1
> CUSTOMER 2 .. and so on ...
>
> As you can see, there are two options with selected attribute,
> therefore always "TEMP CUSTOMER" will be selected.
>
> When I saw this, I though why in all other dropdownchoices
> that I had already implemented following the same sample are working very
> well ?
> I had no doubts, and I changed the TEMP CUSTOMER id
> on database to "1" and ... sup.. the dropdownchoice works fine.
>
> But I can't change that data, so I rollback, and also the
> problem rollback.
>
> I ask to you , experts guys, if I put a negative value into a
> dropdownchoice, it will be the default value if none is selected ?
> How I can do "Choose one" be the default value in this specific case ?
> Any idea to solve this problem ?
>
> Thank you
>
> Best Regards
>
> Juliano
>
Re: Old Wicket QuickStart
dammit :-) Cheers /FLemming ps: Should we arrange on a wicket meeting in copenhagen, now that 1.3.0 is released -> Nino, Frank ? On Jan 2, 2008 10:11 PM, Flemming Boller <[EMAIL PROTECTED]> wrote: > Hi > > First of all, congrats with the new release, great work! > > I am behind a corporate firewall that "infect" downloading of jarfiles, so > I like the "old" wicket quickstart :-) > > I have updated the old "Wicket QuickStart" zip file for use with 1.3.0. > > I have only set it up with Eclipse and with JDK 1.4, so the jar file for > jmx is > excluded in the classpath together with wicke-velocity. > > You can download it from my homepage, if you need it > > http://boller.dk/wicket-quickstart-1.3.0.zip > > Cheers and > > > > > > >
Old Wicket QuickStart
Hi First of all, congrats with the new release, great work! I am behind a corporate firewall that "infect" downloading of jarfiles, so I like the "old" wicket quickstart :-) I have updated the old "Wicket QuickStart" zip file for use with 1.3.0. I have only set it up with Eclipse and with JDK 1.4, so the jar file for jmx is excluded in the classpath together with wicke-velocity. You can download it from my homepage, if you need it http://boller.dk/wicket-quickstart-1.3.0.zip Cheers and
[ANNOUNCE] Apache Wicket 1.3 released
Starting the new year with a bang the Wicket Team has released Apache Wicket 1.3. With this release comes a lot of great successes, but most of all the team wanted to express their wishes to everyone for a happy new year. You can download Apache Wicket 1.3 here: http://wicket.apache.org/getting-wicket.html Apache Wicket is one of the fastest growing Java open source component based web frameworks. With a focus on producing valid html and a logical separation between design and code. Within minutes you can start to enjoy throwing out tag soup, complex components and high maintenance overhead for a simple POJO + html data model. See the Apache Wicket website for more information: http://wicket.apache.org Take a look at some of the following highlights or skip to the bottom and get started now. * last JDK-1.4 release (next release will be Java 5 based) * first Apache release: renamed packages to org.apache.wicket * simplified several core APIs * now works with zero-config behind a proxy server using relative URLs * added Google Guice support * use your Wicket pages directly in a portal without changing a line of code (JSR-168/JSR-286 support) * switched logging API from commons-logging to slf4j * integrate velocity templates as panels in your pages * YUI-calendar and Joda time based date picker (wicket-datetime) * contribute new javascript dependencies to the page header using an Ajax requeset * improved, more robust header contributions * scale to extremely large numbers of users with stateless pages and components * improved AjaxTree/AjaxTreeTable * hybrid URL encoding to make search engines and your users happy * create form panels and use them anywhere without worrying about the nesting of form tags * minimized session use by storing component hierarchy in file system (DiskPageStore) Get started today by downloading Wicket using this link: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 The distribution contains all the Wicket libraries, and all the source code including the examples project. In the root of the download you will find a README document with full instructions. Migrate your Wicket 1.2 application to Wicket 1.3 using our migration guide: http://cwiki.apache.org/WICKET/migrate-12.html Best wishes from the Wicket Team and a prosperous 2008! - The Wicket Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DropDownChoice with -1 value
Hello Everybody
I'm using wicket.markup.html.form.DropDownChoice and it
works fine until now, when I got a suspicious behavior (maybe bug)
Into database I have one data called "TEMP CUSTOMER" that has
id = -1 (it's business logic of our client, that data came through
database importation, and I can not update that data)
Following my code:
List relations = relationManager.list();
final DropDownChoice ddRelations = new DropDownChoice("relation",
(task.getRelation() == null) ? new Model() : new Model(task.getRelation()),
relations, new IChoiceRenderer() {
public Object getDisplayValue(Object object) {
return ((Relation) object).getName();
}
public String getIdValue(Object object, int index) {
return String.valueOf(((Relation) object).getId());
}
});
form.add(ddRelations);
and HERE is the source code generate on html :
Choose one
TEMP CUSTOMER
CUSTOMER 1
CUSTOMER 2 .. and so on ...
As you can see, there are two options with selected attribute,
therefore always "TEMP CUSTOMER" will be selected.
When I saw this, I though why in all other dropdownchoices
that I had already implemented following the same sample are working very well
?
I had no doubts, and I changed the TEMP CUSTOMER id
on database to "1" and ... sup.. the dropdownchoice works fine.
But I can't change that data, so I rollback, and also the
problem rollback.
I ask to you , experts guys, if I put a negative value into a
dropdownchoice, it will be the default value if none is selected ?
How I can do "Choose one" be the default value in this specific case ?
Any idea to solve this problem ?
Thank you
Best Regards
Juliano
Re: Wicket Page lifecyle management (session perspective)
On Wed, 19 Dec 2007, Ravi_116 wrote: > Our application also has login page with user credentials. The Engine (our > domain service class) class is injected with user credentials. > Unfortunately, the Page class seems to be instantiated only once (even when > logging in as two seperate users). Is there a way to either inject a new > Engine class for same page class or create a new Page per user ? Different sessions have different page instances, so probably you need to invalidate the Wicket Session in between the logins. This way you should have exactly one Page instance per user. Best wishes, Timo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ways of making components in a page optional?
An easy trick to avoid this is to use a Panel/Fragment instantiating just a WebMarkupContainer when you don't want to display/create the full component. That's all Paolo On Jan 2, 2008 7:06 PM, Timo Rantalaiho <[EMAIL PROTECTED]> wrote: > On Tue, 18 Dec 2007, wfaler wrote: > > Hmm, haven't tried that. That might work - sometimes you just don't > check all > > the methods thoroughly enough.. :) > > Yep, as far as I know the Wicket Way (TM) of making > components optional is controlling their visibility. This > need becomes more obvious when you consider that (except > repeaters) there is a 1:1 correspondence between HTML > elements with wicket:id and Wicket components, and it > wouldn't be nice to need to change the HTML files runtime :) > > One consequence is that all components of the page always > get constructed even if they are not visible, so on one hand > you don't want to do heavy work in the constructor of such > component but on other hand you get more fail-fast with > regard to component creation. > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oyhttp://www.ri.fi/ > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: WicketTester trouble resubmitting a form
On Tue, 18 Dec 2007, Dan Kaplan wrote:
> IModel model = new Model() {
> public void setObject(Object obj) {
> name = obj.toString();
> }
> };
This is suspicious, I think that you should also override
getObject() to return name. Otherwise the model works a bit
strangely (always returns null).
> public void testResubmit() {
> //note: tester initialized in parent
> tester.startPage(new Test());
> FormTester ft1 = tester.newFormTester("form");
> ft1.setValue("name", "");
> ft1.submit();
> tester.assertRenderedPage(Test.class);
>
> FormTester ft2 = tester.newFormTester("form");
> ft2.setValue("name", "testcity");
> ft2.submit();
> tester.assertNoErrorMessage();//it fails here
> tester.assertRenderedPage(Test.class);
> }
Could it be that WicketTester does not clear the error
message at any point? You could try clearing it explicitly
in between the submits and / or find out if it is a
WicketTester bug.
Best wishes,
Timo
--
Timo Rantalaiho
Reaktor Innovations Oyhttp://www.ri.fi/ >
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ways of making components in a page optional?
On Tue, 18 Dec 2007, wfaler wrote: > Hmm, haven't tried that. That might work - sometimes you just don't check all > the methods thoroughly enough.. :) Yep, as far as I know the Wicket Way (TM) of making components optional is controlling their visibility. This need becomes more obvious when you consider that (except repeaters) there is a 1:1 correspondence between HTML elements with wicket:id and Wicket components, and it wouldn't be nice to need to change the HTML files runtime :) One consequence is that all components of the page always get constructed even if they are not visible, so on one hand you don't want to do heavy work in the constructor of such component but on other hand you get more fail-fast with regard to component creation. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oyhttp://www.ri.fi/ > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Senior Java Developer Opportunity
Good Morning Everyone, I came across this web site & thought it might be beneficial in tracking down talent in the Wicket world. I have a 9+ month contract available in the West Los Angeles area offering a competitive rate & a near immediate start date. The ideal candidate will bring solid experience developing Java-based solutions along with experience with Wicket or similar framework (Tapestry etc.). I would welcome the opportunity to tell you more, so please ring me up at your earliest convenience. I thank you in advance & look forward to your call! Happy New Year! Kristi Principal dSquared Consulting, LLC Office: 602.441.4260 ext. 71 Mobile: 602.510.2058 Fax: 602.288.7828 http://www.dsquaredjobs.com http://www.dsquaredjobs.com/>
RE: Can't Find/Load Properties Files
I overrode resourceKey() but still no luck. I subclassed StringValidator
instead, and am now getting the message I want.
Thanks again for your help.
Shelli
-Original Message-
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 01, 2008 11:00 AM
To: users@wicket.apache.org
Subject: Re: Can't Find/Load Properties Files
not sure why it does that. PatternValidator already extends StringValidator.
go ahead and override resourceKey() and return "MyPatternValidator"
-igor
On Dec 31, 2007 9:45 AM, Shelli D. Orton <[EMAIL PROTECTED]> wrote:
> Thanks for replying!
>
> I did as you suggested and added the messages to MyApp.properties. I now
> get the proper message for com.my.company.MyStringValidator. However
> there's still a problem with the pattern validator. I am expecting my
> message to be displayed as defined in MyApp.properties:
>
> MyPatternValidator=${input} contains invalid characters.
>
> Instead, I get the wicket/Application.properties message:
>
> PatternValidator='${input}' does not match pattern '${pattern}'
>
> Is this related to the same issue you mentioned? I suppose I could make
> MyPatternValidator a subclass of StringValidator, but would prefer to have
> it subclass PatternValidator.
>
> Thanks again!
> Shelli
>
>
> -Original Message-
> From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 28, 2007 5:03 PM
> To: users@wicket.apache.org
> Subject: Re: Can't Find/Load Properties Files
>
> we do not currently check ValidatorClassName.properties files, there
> is an rfe open for that in jira and will go into 1.3.1 or 1.4.0.
>
> for now i would put those new properties into yourapplication.properties
>
> -igor
>
>
> On Dec 28, 2007 1:36 PM, Shelli D. Orton <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I asked a variation of this question recently but didn't get a response.
> I'm still stumped, so am trying again. I am using Wicket 1.2.6 and Tomcat
> 5.0.28 and have created 2 custom validators:
> >
> > com.my.company.MyPatternValidator
> > com.my.company.MyStringValidator
> >
> > where MyPatternValidator extends PatternValidator and MyStringValidator
> extends StringValidator. I have also created properties files for each
> class within a directory structure that match the classpath:
> >
> > com/my/company/MyPatternValidator.properties
> > com/my/company/MyStringValidator.properties
> >
> >
> > The class that extends PatternValidator uses the default message from
> Application.properties instead of the message defined in its properties
> file. The logs show that the Wizard and Application resources are being
> loaded:
> >
> > Dec 28, 2007 2:31:24 PM wicket.resource.PropertiesFactory
> loadPropertiesFileAndWatchForChanges
> > INFO: Loading properties files from
>
file:/C:/tomcat-5.0.28/work/Catalina/localhost/myApp/loader/wicket/extension
> s/wizard/Wizard.properties
> > Dec 28, 2007 2:31:34 PM wicket.resource.PropertiesFactory
> loadPropertiesFileAndWatchForChanges
> > INFO: Loading properties files from
>
file:/C:/tomcat-5.0.28/work/Catalina/localhost/myApp/loader/wicket/Applicati
> on.properties
> >
> > The other that extends StringValidator throws this exception:
> >
> > java.util.MissingResourceException: Unable to find resource:
> MyStringValidator for component: wizard:form:view:service.name
> >
> > I have checked and tomcat-5.0.28/work/Catalina/localhost/myApp also
> contains /com/my/company/MyPatternValidator.properties and
> /com/my/company/MyStringValidator.properties files.
> >
> > Can somebody please explain to me (or point me to a resource) how to set
> up properties files in Wicket so that they can be found? Any help is
> greatly appreciated!
> >
> > Shelli
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Intercept pages and support for pages opened in new windows/tabs
Happy New Year all. I'm running into a problem with the use of intercept pages together with wicket 1.2.x's support for opening pages in new tabs/windows. Basically, if someone has a tab open to our site and then opens a link in another tab which causes the user to be redirected to an intercept page, it will redirect one extra time to create a new page map (that redirect happening through javascript). Unfortunately, this causes wicket to lose track of the original destination of the intercept, thus the intercept no longer works. Has anyone run into this? Any solutions? A bug perhaps? Or just a nuance? Thanks in advance, Meetesh
Re: jetty and eclipse
On Jan 2, 2008 2:48 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > why dont you follow the directions on this page [1], it works for me every > time > > http://wicket.apache.org/quickstart.html Alternatively, you could look at http://chillenious.wordpress.com/2007/12/23/and-finally-here-is-a-new-eclipse-jetty-plugin/ Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wickettester and session?
On Jan 2, 2008 2:28 PM, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]> wrote: > Bump on this one.. If no-one is reacting, you can best open a JIRA issue for it. It helps to have a test case that proves the issue attached to it. Cheers, Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OutOfMemoryError: Java heap space - AppendingStringBuffer
Take a look at this: http://cwiki.apache.org/WICKET/best-practices-and-gotchas.html#BestPracticesandGotchas-AnonymousInnerclasses On 12/28/07, Artur W. <[EMAIL PROTECTED]> wrote: > > Hello Everybody! > > > I just got OutOfMemoryError in our production application (wicket 1.3rc2). > Any ideas what was the reason? > > > Artur > > java.lang.OutOfMemoryError: Java heap space at > org.apache.wicket.util.string.AppendingStringBuffer.expandCapacity(AppendingStringBuffer.java:158) > at > org.apache.wicket.util.string.AppendingStringBuffer.append(AppendingStringBuffer.java:376) > at > org.apache.wicket.util.string.AppendingStringBuffer.append(AppendingStringBuffer.java:344) > at > org.apache.wicket.protocol.http.BufferedWebResponse.write(BufferedWebResponse.java:113) > at org.apache.wicket.markup.ComponentTag.writeOutput(ComponentTag.java:661) > at org.apache.wicket.Component.renderComponentTag(Component.java:3768) at > org.apache.wicket.Component.renderComponent(Component.java:2410)at > org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1354) at > org.apache.wicket.Component.render(Component.java:2256) at > org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1240) at > org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1407) > at > org.apache.wicket.MarkupContainer.renderAssociatedMarkup(MarkupContainer.java:631) > at > org.apache.wicket.markup.html.panel.Panel.onComponentTagBody(Panel.java:112) > at org.apache.wicket.Component.renderComponent(Component.java:2419) at > org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1354) at > org.apache.wicket.Component.render(Component.java:2256) at > org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1240) at > org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1407) > at > org.apache.wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:1344) > at org.apache.wicket.Component.renderComponent(Component.java:2419) at > org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1354) at > org.apache.wicket.Component.render(Component.java:2256) at > org.apache.wicket.markup.repeater.AbstractRepeater.renderChild(AbstractRepeater.java:119) > at > org.apache.wicket.markup.repeater.AbstractRepeater.onRender(AbstractRepeater.java:100) > at org.apache.wicket.Component.render(Component.java:2256) at > org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1240) at > org.apache.wicket.MarkupContainer.renderComponentTagBody(MarkupContainer.java:1407) > at > org.apache.wicket.MarkupContainer.onComponentTagBody(MarkupContainer.java:1344) > at org.apache.wicket.Component.renderComponent(Component.java:2419) at > org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1354) at > org.apache.wicket.Component.render(Component.java:2256) at > org.apache.wicket.MarkupContainer.autoAdd(MarkupContainer.java:222) > -- > View this message in context: > http://www.nabble.com/OutOfMemoryError%3A-Java-heap-space---AppendingStringBuffer-tp14525029p14525029.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Eduardo Issao Ito Summa Technologies "Discipline is never an end in itself, only a means to an end" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating from Wicket1.2 to Wicket1.3
http://cwiki.apache.org/WICKET/migrate-13.html yyj wrote: I am using Wicket1.2. and want to migrate from wicket1.2 to wicket1.3. what the changes should be done in web.xml to access the project in tomcat? I have created web.xml for wicket1.3 with the respected changes but it gives error 'The requested resource (Servlet LoginApplication is not available) is not available.' . I am using Tomcat5.0. and JDK1.5 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrating from Wicket1.2 to Wicket1.3
Did you look in the application logs to see if there are any exceptions happening? How can we diagnose your problem when you don't provide the web.xml? Martijn On Jan 2, 2008 2:07 PM, yyj <[EMAIL PROTECTED]> wrote: > > I am using Wicket1.2. and want to migrate from wicket1.2 to wicket1.3. > what > the changes should be done in web.xml to access the project in tomcat? I > have created web.xml for wicket1.3 with the respected changes but it gives > error 'The requested resource (Servlet LoginApplication is not available) > is > not available.' . I am using Tomcat5.0. and JDK1.5 > -- > View this message in context: > http://www.nabble.com/Migrating-from-Wicket1.2-to-Wicket1.3-tp14578086p14578086.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-rc2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/
Migrating from Wicket1.2 to Wicket1.3
I am using Wicket1.2. and want to migrate from wicket1.2 to wicket1.3. what the changes should be done in web.xml to access the project in tomcat? I have created web.xml for wicket1.3 with the respected changes but it gives error 'The requested resource (Servlet LoginApplication is not available) is not available.' . I am using Tomcat5.0. and JDK1.5 -- View this message in context: http://www.nabble.com/Migrating-from-Wicket1.2-to-Wicket1.3-tp14578086p14578086.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: @AuthorizeInstanciation and several roles
Thanks for responding, we always try to improve. On Jan 2, 2008 11:20 AM, Sébastien Piller <[EMAIL PROTECTED]> wrote: > > Well, with swarm I do need to define the policy files, which isn't trivial > for me (I never saw this kind of syntax before). True, policy file is not a trivial task especially for a big app the policy can grow to several thousands of lines. As for the syntax, it is the same as for a Jaas policy file, but if you never worked with jaas that is not going to help you much. On the other hand swarm is flexible enough for you to swap in you own "policy file" implementation, whether it is stored in a database or in a policy file with a completely different syntax. If you use java 1.5 you might even put something together that gets the information from annotations on your wicket pages. > And there is a lot of new classes/interfaces in this api (SwarmWebApp, > Principal, SwarmActionFactory, LoginContext, ...) with no much > documentation. Sure there are new classes every framework extension has them, they are here to help you with the grunt work, they are not your enemies. What documentation are you missing? every class has javadoc, there are several wiki pages with information, including how to get started http://wicketstuff.org/confluence/display/STUFFWIKI/Wicket-Security, There is an examples project (which could benefit from imprvements, no arguments there). > It's not easy to transform an AuthenticatedWebApp in a > SwarmWebApp. Well that is because they both have a very different approach on how to do things. Personally i have not worked much with wicket-auth-roles but perhaps a step by step conversion would be helpful to some people. > > I think wicket-auth-roles is more clear and easy to use (just to put an > annotation and implement getRoles in the session). It's trivial and looks > pretty. When I need to, I manually enable/disable the links. It's easy to > implement with my layout. That is your opinion, i have however seen loads of questions about wicket-auth-roles on the mailing list as well, and thats ok there will always be questions about frameworks, and some users will get along better with product A and some with product B. Personally i feel wicket-auth-roles is to simple to get the job done for the type of applications we build, but if it suits your needs then by all means go for it. > > I think some clear and simple examples using swarm with users extracted > from a db will be a very good improvement. (with login page, normal pages, > securized pages and several security levels) There are already several simple examples, but apparently you would like to see a full blown app, we'll see if we can build one. http://wicketstuff.org/confluence/display/STUFFWIKI/Wicket-Security+Examples > > If so, I might upgrade my app to use swarm. But for now it looks too > complicated for just autorizing instantiation. > > And last but not least, swarm/wasp are both in version 0.1 beta, I'd prefer > to wait for a stable release or at least a rc. (my app will be in production > soon) version 0.2 beta should be out soon, and for what its worth so is our app and we still use it. Don't let the 0.1 fool you i don't believe in starting version numbers from 1.0. Besides you did know that wicket-auth-roles is a demo project? ;) Anyway, thanks for this insight. I'll try to do something with it. Maurice - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: @AuthorizeInstanciation and several roles
Well, with swarm I do need to define the policy files, which isn't
trivial for me (I never saw this kind of syntax before).
And there is a lot of new classes/interfaces in this api (SwarmWebApp,
Principal, SwarmActionFactory, LoginContext, ...) with no much
documentation. It's not easy to transform an AuthenticatedWebApp in a
SwarmWebApp.
I think wicket-auth-roles is more clear and easy to use (just to put an
annotation and implement getRoles in the session). It's trivial and
looks pretty. When I need to, I manually enable/disable the links. It's
easy to implement with my layout.
I think some clear and simple examples using swarm with users extracted
from a db will be a very good improvement. (with login page, normal
pages, securized pages and several security levels)
If so, I might upgrade my app to use swarm. But for now it looks too
complicated for just autorizing instantiation.
And last but not least, swarm/wasp are both in version 0.1 beta, I'd
prefer to wait for a stable release or at least a rc. (my app will be
in production soon)
Thanks
Maurice Marrink a écrit :
Hi,
I'm wondering what exactly about swarm you find difficult or too complex.
Perhaps we can make some improvements.
preventing pages in swarm to be constructed is as complex as extending
SecureWebPage.
Off course you need to create a policy for those 3 types of users,
containing you're secure pages.
About hiding links to pages people are not supposed to come, it will
spare your users from hitting the access denied page.
It tends to annoy people: if the app knows i'm not allowed to go there
then why can i click on that link anyway, etc.
Maurice
On Dec 31, 2007 1:05 AM, Pills <[EMAIL PROTECTED]> wrote:
Hello,
I'm using the wicket-auth-roles package to allow or restrict access to some
pages. I need to autorize the instanciation of some pages to several roles.
Is it possible to write something like:
@AuthorizeInstanciation("poweruser,admin,sysadmin")
class Mypage extends WebPage {...}
and something like this in my authenticated session:
public Roles getRoles() {
return new Roles(new String[] {"poweruser","admin","sysadmin"});
}
If it's possible, what is the right syntax?
PS: I've read a bit about wasp/swarm, but it looks too much complicated for
my needs (I just need to prevent some components to be instantiated for some
kinds of users). Hiding/showing links and such fonctionnality is not needed
Thank you ;)
--
View this message in context: http://www.nabble.com/%40AuthorizeInstanciation-and-several-roles-tp14552711p14552711.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: {wicket 1.3 rc1}testing ajaxbutton...
Hi Timo
It was a bug in rc 1 I think, was fixed rc2 as I remember.
Timo Rantalaiho wrote:
On Fri, 14 Dec 2007, Nino Saturnino Martinez Vazquez Wael wrote:
If I try to execute the event I just get an null pointer exeception like
this:
wicketTester.executeAjaxEvent("form:ajaxButton", "onclick");
Should I just check if theres ajax present? And the process the form
using the formtester?
Hi, are you sure that the path "form:ajaxButton" is correct?
So if you do
AjaxButton button = (AjaxButton)
wicketTester.getComponentFromLastRenederedPage("form:ajaxButton");
Assert.notNull(button);
does it pass?
What is the stack trace? Is request cycle initialized?
Are you sure that "onclick" is the correct event?
Best wishes,
Timo
--
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: @AuthorizeInstanciation and several roles
Hi,
I'm wondering what exactly about swarm you find difficult or too complex.
Perhaps we can make some improvements.
preventing pages in swarm to be constructed is as complex as extending
SecureWebPage.
Off course you need to create a policy for those 3 types of users,
containing you're secure pages.
About hiding links to pages people are not supposed to come, it will
spare your users from hitting the access denied page.
It tends to annoy people: if the app knows i'm not allowed to go there
then why can i click on that link anyway, etc.
Maurice
On Dec 31, 2007 1:05 AM, Pills <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I'm using the wicket-auth-roles package to allow or restrict access to some
> pages. I need to autorize the instanciation of some pages to several roles.
> Is it possible to write something like:
>
> @AuthorizeInstanciation("poweruser,admin,sysadmin")
> class Mypage extends WebPage {...}
>
> and something like this in my authenticated session:
>
> public Roles getRoles() {
> return new Roles(new String[] {"poweruser","admin","sysadmin"});
> }
>
> If it's possible, what is the right syntax?
>
> PS: I've read a bit about wasp/swarm, but it looks too much complicated for
> my needs (I just need to prevent some components to be instantiated for some
> kinds of users). Hiding/showing links and such fonctionnality is not needed
>
> Thank you ;)
> --
> View this message in context:
> http://www.nabble.com/%40AuthorizeInstanciation-and-several-roles-tp14552711p14552711.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
