Re: The Apache Software Foundation Announces Apache Wicket™ 6.0.0
Thank you all for this new version!
Il 05/09/2012 18:53, Martijn Dashorst ha scritto:
"With great pleasure we announce the availability of Apache Wicket 6.0.0"
-- Martijn Dashorst, Vice President, Apache Wicket
Apache Wicket v6.0.0 is the 6th major release of the popular open
source Java web framework. Numerous enhancements make Apache Wicket
v6.0.0 a solid choice for web development:
- Out-of-the box JQuery integration
- Complete control over AJAX requests
- Improved event registration in browsers
- Support for large datasets in components
- Dependency management for client side javascript libraries
- Experimental support for websockets
Additional features include a customizable client-side API, improved
feedback messages, correct packaging for OSGi compatibility and
improved initialization of plugins. Highlights include:
Java 6 required -This release moves the minimum required Java version
to Java 6. This means that Wicket applications running on earlier Java
versions meaning to upgrade, also need to upgrade their Java runtime.
Revamped Wicket AJAX now leverages JQuery - Wicket's custom AJAX
JavaScript library has been re-implemented using JQuery. This makes it
easier to integrate JQuery plugins into Wicket applications. With the
new AJAX implementation it is possible to provide your own version of
JQuery should the need arise, or even to replace the whole Wicket
client side AJAX implementation.
AJAX Attributes - With the new and improved AJAX implementation, you
can alter any aspect of an AJAX request through AjaxRequestAttributes.
For example you can specify that the request should be executed using
POST instead of GET, or that the AJAX request should be multi-part,
etc. See the migration guide or the JavaDoc of AjaxRequestAttributes
for all possible options.
Browser event registration replaces inline events - Wicket now uses
JavaScript event registration instead of inline attributes for AJAX
components. This enables multiple event listeners to be attached to a
markup tag, cleans up the rendered markup considerably and reduces the
amount of generated markup.
IDataProvider now uses long instead of int - The IDataProvider
interface and implementations now use long instead of int for index
and size parameters to better line up with the Java Persistence API
and other persistency frameworks. Big data is now possible with
Wicket!
${label} replaces ${input} in feedback messages - Previous Wicket
versions used the input that was provided by users in error messages
when validations failed. This led to error messages like "1234a is not
a valid number". In Wicket 6 the feedback messages use the label of
the invalid form component instead. You can set the label by calling
setLabel() on the form component. If no label is provided, Wicket
defaults to displaying the component identifier. This changes the
error message to "Phonenumber is not a valid number".
Resources can declare dependencies - It is now much easier to create
resource contributions with dependencies, for example a JQuery plugin
can declare a dependency on JQuery and other resources such as
embedded style sheets. Users of such resources don’t have to provide
these dependencies themselves, and the dependencies are linked in the
appropriate order.
Packaged resources will use minimized version automatically - When a
minimized JavaScript resource is available (filename.min.js – add the
.min part to the filename before the extension), Wicket will
automatically use the minimized version when running in deployment
mode, while using the non-minimized version for development mode.
OSGi compatible packaging - Wicket's packaging has been made
compatible with OSGi bundles by moving some classes to different
packages. The full list can be found in our migration guide. This
makes it much easier to deploy Wicket applications in an OSGi
environment.
Experimental websocket implementations - This release also includes
two experimental websocket implementations: one using Atmosphere as a
bridge for browsers and containers that don't support websockets
natively and one for containers and browsers that have native
websocket support.
The complete set of changes is available in the migration guide at
http://s.apache.org/wicket-6.0-migration
Availability and Oversight
As with all Apache products, Apache Wicket v6.0.0 is released under
the Apache License v2.0, and is overseen by a self-selected team of
active contributors to the project. A Project Management Committee
(PMC) guides the Project's day-to-day operations, including community
development and product releases. Apache Wicket source code,
documentation, and related resources are available at
http://wicket.apache.org/
"Apache", "Wicket", "Apache Wicket", and "ApacheCon" are trademarks of
The Apache Software Foundation. All other brands and trademarks are
the property of their respective owners.
-
To unsubscribe, e-mail: users-unsub
Re: The Apache Software Foundation Announces Apache Wicket™ 6.0.0
Good job -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/The-Apache-Software-Foundation-Announces-Apache-Wicket-6-0-0-tp4651780p4651798.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: The Apache Software Foundation Announces Apache Wicket™ 6.0.0
Here are a few articles which may be useful for you: http://wicketinaction.com/2012/07/whats-new-in-wicket-6/ http://wicketinaction.com/2012/07/wicket-6-javascript-improvements/ http://wicketinaction.com/2012/07/wicket-6-native-websockets/ http://wicketinaction.com/2012/07/wicket-6-resource-management/ On Thu, Sep 6, 2012 at 10:05 AM, Decebal Suiu wrote: > Good job > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/The-Apache-Software-Foundation-Announces-Apache-Wicket-6-0-0-tp4651780p4651798.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: The Apache Software Foundation Announces Apache Wicket™ 6.0.0
Congratulations and thanks for all the effort!
Best regards / Met vriendelijke groet,
Kees van Dieren
Squins | IT, Honestly
Oranjestraat 23
2983 HL Ridderkerk
The Netherlands
Mobile: +31 (0)6 30413841
www.squins.com
http://twitter.com/keesvandieren
Chamber of commerce Rotterdam: 24435130
Boeken voor school en werk bestel je op studieboekencenter.nl
2012/9/5 Martijn Dashorst
> "With great pleasure we announce the availability of Apache Wicket 6.0.0"
> -- Martijn Dashorst, Vice President, Apache Wicket
>
> Apache Wicket v6.0.0 is the 6th major release of the popular open
> source Java web framework. Numerous enhancements make Apache Wicket
> v6.0.0 a solid choice for web development:
>
> - Out-of-the box JQuery integration
> - Complete control over AJAX requests
> - Improved event registration in browsers
> - Support for large datasets in components
> - Dependency management for client side javascript libraries
> - Experimental support for websockets
>
> Additional features include a customizable client-side API, improved
> feedback messages, correct packaging for OSGi compatibility and
> improved initialization of plugins. Highlights include:
>
> Java 6 required -This release moves the minimum required Java version
> to Java 6. This means that Wicket applications running on earlier Java
> versions meaning to upgrade, also need to upgrade their Java runtime.
>
> Revamped Wicket AJAX now leverages JQuery - Wicket's custom AJAX
> JavaScript library has been re-implemented using JQuery. This makes it
> easier to integrate JQuery plugins into Wicket applications. With the
> new AJAX implementation it is possible to provide your own version of
> JQuery should the need arise, or even to replace the whole Wicket
> client side AJAX implementation.
>
> AJAX Attributes - With the new and improved AJAX implementation, you
> can alter any aspect of an AJAX request through AjaxRequestAttributes.
> For example you can specify that the request should be executed using
> POST instead of GET, or that the AJAX request should be multi-part,
> etc. See the migration guide or the JavaDoc of AjaxRequestAttributes
> for all possible options.
>
> Browser event registration replaces inline events - Wicket now uses
> JavaScript event registration instead of inline attributes for AJAX
> components. This enables multiple event listeners to be attached to a
> markup tag, cleans up the rendered markup considerably and reduces the
> amount of generated markup.
>
> IDataProvider now uses long instead of int - The IDataProvider
> interface and implementations now use long instead of int for index
> and size parameters to better line up with the Java Persistence API
> and other persistency frameworks. Big data is now possible with
> Wicket!
>
> ${label} replaces ${input} in feedback messages - Previous Wicket
> versions used the input that was provided by users in error messages
> when validations failed. This led to error messages like "1234a is not
> a valid number". In Wicket 6 the feedback messages use the label of
> the invalid form component instead. You can set the label by calling
> setLabel() on the form component. If no label is provided, Wicket
> defaults to displaying the component identifier. This changes the
> error message to "Phonenumber is not a valid number".
>
> Resources can declare dependencies - It is now much easier to create
> resource contributions with dependencies, for example a JQuery plugin
> can declare a dependency on JQuery and other resources such as
> embedded style sheets. Users of such resources don’t have to provide
> these dependencies themselves, and the dependencies are linked in the
> appropriate order.
>
> Packaged resources will use minimized version automatically - When a
> minimized JavaScript resource is available (filename.min.js – add the
> .min part to the filename before the extension), Wicket will
> automatically use the minimized version when running in deployment
> mode, while using the non-minimized version for development mode.
>
> OSGi compatible packaging - Wicket's packaging has been made
> compatible with OSGi bundles by moving some classes to different
> packages. The full list can be found in our migration guide. This
> makes it much easier to deploy Wicket applications in an OSGi
> environment.
>
> Experimental websocket implementations - This release also includes
> two experimental websocket implementations: one using Atmosphere as a
> bridge for browsers and containers that don't support websockets
> natively and one for containers and browsers that have native
> websocket support.
>
> The complete set of changes is available in the migration guide at
> http://s.apache.org/wicket-6.0-migration
>
> Availability and Oversight
>
> As with all Apache products, Apache Wicket v6.0.0 is released under
> the Apache License v2.0, and is overseen by a self-selected team of
> active contributors to the project. A Project Management Committee
> (PMC) guides the Project's day-to-day op
WiQuery 6.0.0 has been released!
We from WiQuery are happy to announce the release of WiQuery 6.0.0! Unlike WiQuery 1.5 this release has become smaller. All of the resource management present in WiQuery 1.5 has been removed because Wickets resource management has been totally revamped and works nearly the same. This considerably decreases the footprint of WiQuery. Not only in LOC but also in performance. This allows us to start focusing completely on providing users with a JQuery statement API and JQuery UI components. For backward compatibility purposes some of the 1.5 API has been marked deprecated instead of removing it completely. For example: all Behaviors in WiQuery will check if the statement() function is still used and if so use the new approach to render. Our artifacts can be found at maven central. See listing here: http://mvnrepository.com/artifact/org.odlabs.wiquery/ Happy querying! Hielke Hoeve - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: WiQuery 6.0.0 has been released!
Awesome ! I am impatient to use it in my next Wicket project ! Cheers Julien Roche On Thu, Sep 6, 2012 at 12:23 PM, Hielke Hoeve wrote: > We from WiQuery are happy to announce the release of WiQuery 6.0.0! > > Unlike WiQuery 1.5 this release has become smaller. All of the resource > management present in WiQuery 1.5 has been removed because Wickets resource > management has been totally revamped and works nearly the same. This > considerably decreases the footprint of WiQuery. Not only in LOC but also > in performance. This allows us to start focusing completely on providing > users with a JQuery statement API and JQuery UI components. > > For backward compatibility purposes some of the 1.5 API has been marked > deprecated instead of removing it completely. For example: all Behaviors in > WiQuery will check if the statement() function is still used and if so use > the new approach to render. > > Our artifacts can be found at maven central. See listing here: > http://mvnrepository.com/artifact/org.odlabs.wiquery/ > > Happy querying! > > Hielke Hoeve > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
[CVE-2012-3373] Apache Wicket XSS vulnerability via manipulated URL parameter
Severity: Important Vendor: The Apache Software Foundation Versions Affected: Apache Wicket 1.4.x and 1.5.x Description: https://wicket.apache.org/2012/09/06/cve-2012-3373.html It is possible to inject JavaScript statements into an ajax link by adding an encoded null byte to a URL pointing to a Wicket app. This could be done by sending a legitimate user a manipulated URL and tricking the user into clicking on it. This vulnerability is fixed in - Apache Wicket 1.4.21 https://wicket.apache.org/2012/09/05/wicket-1.4.21-released.html - Apache Wicket 1.5.8 https://wicket.apache.org/2012/08/24/wicket-1.5.8-released.html Apache Wicket 6.0.0 is not affected. Credit: This issue was reported by Thomas Heigl. Apache Wicket Team - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Wicket and Javascript UI Libraries' components
Hi, I am a newbie. So far I have used PHP with some javascript libraries: Prototype, YUI, Dojo. I started with Wicket 1.4.x. As I see Wicket has its own ui componenets. What is not clear for me how can I use/integrate an external Javascript libraries. Any help is appreciated, Regards gia -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-and-Javascript-UI-Libraries-components-tp4651804.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket and Javascript UI Libraries' components
Hi Gia, There are few good libraries that integrate Wicket with JavaScript libraries (mostly jQuery). See http://code.google.com/p/wiquery/, http://code.google.com/p/wicket-jquery-ui/, http://code.google.com/p/jqwicket/, ... If you don't use jQuery then use there code as inspiration. On Thu, Sep 6, 2012 at 3:30 PM, gia wrote: > Hi, > > I am a newbie. > So far I have used PHP with some javascript libraries: Prototype, YUI, Dojo. > I started with Wicket 1.4.x. As I see Wicket has its own ui componenets. > What is not clear for me how can I use/integrate an external Javascript > libraries. > > Any help is appreciated, > > Regards > > gia > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Wicket-and-Javascript-UI-Libraries-components-tp4651804.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 1.5 migration questions
In 1.4 I had the following classes in com.myco.app.res package: GlobalJavascriptResourceReference extends JavaScriptResourceReference GlobalCompressedResourceReference extends PackageResourceReference GlobalResourceScope And Application had the following code: getSharedResources().putClassAlias(GlobalResourceScope.class, "global") The caller would add resources as follows: new GlobalJavascriptResourceReference(GlobalResourceScope.class, "js/common.js"); new GlobalCompressedResourceReference(GlobalResourceScope.class, "css/styles.css"); How should I port this to 1.5 so that I can still access http://../global/js/common.js and http://../global/js/styles.css? Thanks, Alec On Tue, Sep 4, 2012 at 5:10 PM, Martin Grigorov wrote: > On Tue, Sep 4, 2012 at 11:17 PM, Alec Swan wrote: >> Well, mountPackage did not work for me either. >> >> Basically, what I want to do is access ALL resources in >> com.myco.app.res package with "global" URL prefix. For example, access >> a JavaScript file as global/events.js instead of >> ../wicket/resource/com.myco.app.res.GlobalResourceScope/events.js URL. >> In 1.4 it was simple with >> putClassAlias(com.myco.app.res.GlobalResourceScope, "global"). >> >> How can I do this with 1.5? > > Why #mountResource() didn't work for you ? > >> >> Thanks, >> >> Alec >> >> On Tue, Sep 4, 2012 at 10:59 AM, Alec Swan wrote: >>> Tom, >>> >>> I have com.myco.app.res.GlobalResourceScope.class and events.js in the >>> same package. So, putClassAlias(GlobalResourceScope.class, "global") >>> in 1.4 would allow me to access http://../app/global/events.js in the >>> browser. >>> >>> It seems like in 1.5 this is similar to mountPackage(String, Class>> extends Page>) which means I have to change GlobalResourceScope class >>> to extend Page, right? Why does it need to be a Page? >>> >>> Thanks, >>> >>> Alec >>> >>> On Tue, Sep 4, 2012 at 9:42 AM, Thomas Götz wrote: I didn't get your usecase exactly yet, but maybe this will help you: http://wicketinaction.com/2011/07/wicket-1-5-mounting-resources/ Cheers, -Tom On 04.09.2012, at 17:33, Alec Swan wrote: > I saw the link explaining how to migrate > "SharedResources#putClassAlias(GlobalResourceScope.class, "global")" > before but was found it confusing because "global" and "images" > aliases 1.4 version were replaced with "imgres" in 1.5 example. > > All I need to do is use "global" in place of GlobalResourceScope.class > in the URLs. How do I do this in 1.5? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 1.5 migration questions
extend PackageResourceReference and override its #getName() to read
the name from the request path/parameters
mountResource("/global", new MyPRR())
On Thu, Sep 6, 2012 at 7:57 PM, Alec Swan wrote:
> In 1.4 I had the following classes in com.myco.app.res package:
>
> GlobalJavascriptResourceReference extends JavaScriptResourceReference
> GlobalCompressedResourceReference extends PackageResourceReference
> GlobalResourceScope
>
> And Application had the following code:
> getSharedResources().putClassAlias(GlobalResourceScope.class, "global")
>
> The caller would add resources as follows:
> new GlobalJavascriptResourceReference(GlobalResourceScope.class,
> "js/common.js");
> new GlobalCompressedResourceReference(GlobalResourceScope.class,
> "css/styles.css");
>
> How should I port this to 1.5 so that I can still access
> http://../global/js/common.js and http://../global/js/styles.css?
>
> Thanks,
>
> Alec
>
> On Tue, Sep 4, 2012 at 5:10 PM, Martin Grigorov wrote:
>> On Tue, Sep 4, 2012 at 11:17 PM, Alec Swan wrote:
>>> Well, mountPackage did not work for me either.
>>>
>>> Basically, what I want to do is access ALL resources in
>>> com.myco.app.res package with "global" URL prefix. For example, access
>>> a JavaScript file as global/events.js instead of
>>> ../wicket/resource/com.myco.app.res.GlobalResourceScope/events.js URL.
>>> In 1.4 it was simple with
>>> putClassAlias(com.myco.app.res.GlobalResourceScope, "global").
>>>
>>> How can I do this with 1.5?
>>
>> Why #mountResource() didn't work for you ?
>>
>>>
>>> Thanks,
>>>
>>> Alec
>>>
>>> On Tue, Sep 4, 2012 at 10:59 AM, Alec Swan wrote:
Tom,
I have com.myco.app.res.GlobalResourceScope.class and events.js in the
same package. So, putClassAlias(GlobalResourceScope.class, "global")
in 1.4 would allow me to access http://../app/global/events.js in the
browser.
It seems like in 1.5 this is similar to mountPackage(String, Class>>> extends Page>) which means I have to change GlobalResourceScope class
to extend Page, right? Why does it need to be a Page?
Thanks,
Alec
On Tue, Sep 4, 2012 at 9:42 AM, Thomas Götz wrote:
> I didn't get your usecase exactly yet, but maybe this will help you:
> http://wicketinaction.com/2011/07/wicket-1-5-mounting-resources/
>
> Cheers,
>-Tom
>
>
> On 04.09.2012, at 17:33, Alec Swan wrote:
>
>> I saw the link explaining how to migrate
>> "SharedResources#putClassAlias(GlobalResourceScope.class, "global")"
>> before but was found it confusing because "global" and "images"
>> aliases 1.4 version were replaced with "imgres" in 1.5 example.
>>
>> All I need to do is use "global" in place of GlobalResourceScope.class
>> in the URLs. How do I do this in 1.5?
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>
>>
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket 1.5 migration questions
But I want JavaScript files to be compresses by
JavaScriptResourceReference and CSS be served as
PackageResourceReference. How do I mount them both under /global URL
suffix?
On Thu, Sep 6, 2012 at 12:02 PM, Martin Grigorov wrote:
> extend PackageResourceReference and override its #getName() to read
> the name from the request path/parameters
> mountResource("/global", new MyPRR())
>
> On Thu, Sep 6, 2012 at 7:57 PM, Alec Swan wrote:
>> In 1.4 I had the following classes in com.myco.app.res package:
>>
>> GlobalJavascriptResourceReference extends JavaScriptResourceReference
>> GlobalCompressedResourceReference extends PackageResourceReference
>> GlobalResourceScope
>>
>> And Application had the following code:
>> getSharedResources().putClassAlias(GlobalResourceScope.class, "global")
>>
>> The caller would add resources as follows:
>> new GlobalJavascriptResourceReference(GlobalResourceScope.class,
>> "js/common.js");
>> new GlobalCompressedResourceReference(GlobalResourceScope.class,
>> "css/styles.css");
>>
>> How should I port this to 1.5 so that I can still access
>> http://../global/js/common.js and http://../global/js/styles.css?
>>
>> Thanks,
>>
>> Alec
>>
>> On Tue, Sep 4, 2012 at 5:10 PM, Martin Grigorov wrote:
>>> On Tue, Sep 4, 2012 at 11:17 PM, Alec Swan wrote:
Well, mountPackage did not work for me either.
Basically, what I want to do is access ALL resources in
com.myco.app.res package with "global" URL prefix. For example, access
a JavaScript file as global/events.js instead of
../wicket/resource/com.myco.app.res.GlobalResourceScope/events.js URL.
In 1.4 it was simple with
putClassAlias(com.myco.app.res.GlobalResourceScope, "global").
How can I do this with 1.5?
>>>
>>> Why #mountResource() didn't work for you ?
>>>
Thanks,
Alec
On Tue, Sep 4, 2012 at 10:59 AM, Alec Swan wrote:
> Tom,
>
> I have com.myco.app.res.GlobalResourceScope.class and events.js in the
> same package. So, putClassAlias(GlobalResourceScope.class, "global")
> in 1.4 would allow me to access http://../app/global/events.js in the
> browser.
>
> It seems like in 1.5 this is similar to mountPackage(String, Class extends Page>) which means I have to change GlobalResourceScope class
> to extend Page, right? Why does it need to be a Page?
>
> Thanks,
>
> Alec
>
> On Tue, Sep 4, 2012 at 9:42 AM, Thomas Götz wrote:
>> I didn't get your usecase exactly yet, but maybe this will help you:
>> http://wicketinaction.com/2011/07/wicket-1-5-mounting-resources/
>>
>> Cheers,
>>-Tom
>>
>>
>> On 04.09.2012, at 17:33, Alec Swan wrote:
>>
>>> I saw the link explaining how to migrate
>>> "SharedResources#putClassAlias(GlobalResourceScope.class, "global")"
>>> before but was found it confusing because "global" and "images"
>>> aliases 1.4 version were replaced with "imgres" in 1.5 example.
>>>
>>> All I need to do is use "global" in place of GlobalResourceScope.class
>>> in the URLs. How do I do this in 1.5?
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>>
>>> --
>>> Martin Grigorov
>>> jWeekend
>>> Training, Consulting, Development
>>> http://jWeekend.com
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
How to specify the html text for span
Hi - I have a MultiLineLabel as following
this.form.add(new MultiLineLabel("myLabel").add(new
SimpleAttributeModifier("title", tooltipMsg)));
Now on the html side, I have smething like following:
Now, when the page renders is replaced to null by wicket. I want to
have there as the span css background image would apply only if
something is there in span. Can you please suggest how can i achieve this?
Please provide any example.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-specify-the-html-text-for-span-tp4651812.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: How to specify the html text for span
Hard to guess the problem when your markup didn't come through :/.
Sven
On 09/06/2012 08:26 PM, jam.ntk wrote:
Hi - I have a MultiLineLabel as following
this.form.add(new MultiLineLabel("myLabel").add(new
SimpleAttributeModifier("title", tooltipMsg)));
Now on the html side, I have smething like following:
Now, when the page renders is replaced to null by wicket. I want to
have there as the span css background image would apply only if
something is there in span. Can you please suggest how can i achieve this?
Please provide any example.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-specify-the-html-text-for-span-tp4651812.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: How to specify the html text for span
here is the mark up: -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/How-to-specify-the-html-text-for-span-tp4651812p4651814.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: The Apache Software Foundation Announces Apache Wicket™ 6.0.0
Very very nice, very very greatest job thx Duto - Duto -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/The-Apache-Software-Foundation-Announces-Apache-Wicket-6-0-0-tp4651780p4651815.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How to specify the html text for span
On Thu, Sep 6, 2012 at 8:26 PM, jam.ntk wrote:
> Hi - I have a MultiLineLabel as following
>
> this.form.add(new MultiLineLabel("myLabel").add(new
Pass some non-null model to the label above.
See its constructors.
> SimpleAttributeModifier("title", tooltipMsg)));
>
> Now on the html side, I have smething like following:
>
>
>
> Now, when the page renders is replaced to null by wicket. I want to
> have there as the span css background image would apply only if
> something is there in span. Can you please suggest how can i achieve this?
> Please provide any example.
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/How-to-specify-the-html-text-for-span-tp4651812.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: The Apache Software Foundation Announces Apache Wicket™ 6.0.0
Nice Job! Thanks to all! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/The-Apache-Software-Foundation-Announces-Apache-Wicket-6-0-0-tp4651780p4651817.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Add an invisible component to an AjaxRequestTarget target
Hi, We have partial page updates all over a page. So panels and components all over the place that need Ajax updates. We're using an Interface on those components and with an IVisitor we traverse the component tree and add every component to the target that has this interface. But during development we see that we get errors in the ajax debug log when these components have an invisible state. These components themselves can have this state but some of the times, the parent component is invisible. In these cases when such a hidden component is added to the AjaxRequestTarget we get an error in the ajax debug log. Adding the isVisible check before adding the component to the target could save us in some situations but not all (as it might get visible or invisible) at a later state. How can I prevent these components from being added to the AjaxRequestTarget? Or from the error being thrown? I had hoped that a component being in an invisible state (somewhere in the tree) wouldn't get rendered. It's not really a problem in a 'deployment' situation, but it's not 'nice' either. Thijs - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Add an invisible component to an AjaxRequestTarget target
isVisibleInHierarchy() will make sure all parents are visible as well -igor On Thu, Sep 6, 2012 at 1:27 PM, Thijs Vonk wrote: > Hi, > > We have partial page updates all over a page. So panels and components all > over the place that need Ajax updates. > We're using an Interface on those components and with an IVisitor we > traverse the component tree and add every component to the target that has > this interface. > > But during development we see that we get errors in the ajax debug log when > these components have an invisible state. These components themselves can > have this state but some of the times, the parent component is invisible. In > these cases when such a hidden component is added to the AjaxRequestTarget > we get an error in the ajax debug log. > > Adding the isVisible check before adding the component to the target could > save us in some situations but not all (as it might get visible or > invisible) at a later state. > How can I prevent these components from being added to the > AjaxRequestTarget? Or from the error being thrown? I had hoped that a > component being in an invisible state (somewhere in the tree) wouldn't get > rendered. It's not really a problem in a 'deployment' situation, but it's > not 'nice' either. > > > Thijs > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Migration to 1.5: 'X' is not a valid Serializable
I just ran into another problem with type resolution. In fact, it looks like a bug in org.apache.wicket.util.lang.Objects#convertValue. The call convertValue(nonNullNonArrayValue, Object.class) will always return null if nonNullNonArrayValue is a value that is not null and not an array! Is that a legitimate bug? Thanks, Alec On Wed, Sep 5, 2012 at 1:12 AM, dpmihai wrote: > see this: > http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-ListMultipleChoice-add-Serializable-values-td4585991.html#a4586026 > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Migration-to-1-5-X-is-not-a-valid-Serializable-tp4651757p4651764.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Add an invisible component to an AjaxRequestTarget target
OK thnx will give it a try On 6/9/12 22:39, Igor Vaynberg wrote: isVisibleInHierarchy() will make sure all parents are visible as well -igor On Thu, Sep 6, 2012 at 1:27 PM, Thijs Vonk wrote: Hi, We have partial page updates all over a page. So panels and components all over the place that need Ajax updates. We're using an Interface on those components and with an IVisitor we traverse the component tree and add every component to the target that has this interface. But during development we see that we get errors in the ajax debug log when these components have an invisible state. These components themselves can have this state but some of the times, the parent component is invisible. In these cases when such a hidden component is added to the AjaxRequestTarget we get an error in the ajax debug log. Adding the isVisible check before adding the component to the target could save us in some situations but not all (as it might get visible or invisible) at a later state. How can I prevent these components from being added to the AjaxRequestTarget? Or from the error being thrown? I had hoped that a component being in an invisible state (somewhere in the tree) wouldn't get rendered. It's not really a problem in a 'deployment' situation, but it's not 'nice' either. Thijs - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Migration to 1.5: 'X' is not a valid Serializable
The fix for this is the same as for the "X is not a valid Serializable", specifically: new EditableLabel(..).setType(String.class) Is there anybody who thinks that requiring setType(..) call on all components which models don't resolve to a supported type is huge problem? Can this be fixed in 1.5.9? Alec On Thu, Sep 6, 2012 at 2:41 PM, Alec Swan wrote: > I just ran into another problem with type resolution. In fact, it > looks like a bug in org.apache.wicket.util.lang.Objects#convertValue. > The call convertValue(nonNullNonArrayValue, Object.class) will always > return null if nonNullNonArrayValue is a value that is not null and > not an array! > > Is that a legitimate bug? > > Thanks, > > Alec > > On Wed, Sep 5, 2012 at 1:12 AM, dpmihai wrote: >> see this: >> http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-ListMultipleChoice-add-Serializable-values-td4585991.html#a4586026 >> >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Migration-to-1-5-X-is-not-a-valid-Serializable-tp4651757p4651764.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Migration to 1.5: 'X' is not a valid Serializable
Besides calling #setType() do you actually use generics with your models and components? See also: http://wicket.apache.org/apidocs/1.5/org/apache/wicket/markup/html/form/Form Component.html#setType(java.lang.Class) And the model changes done in 1.4: https://cwiki.apache.org/WICKET/migrating-to-wicket-14.html#MigratingtoWicke t1.4-Modelchanges ~ Thank you Paul Bors -Original Message- From: Alec Swan [mailto:alecs...@gmail.com] Sent: Thursday, September 06, 2012 5:18 PM To: users@wicket.apache.org Subject: Re: Migration to 1.5: 'X' is not a valid Serializable The fix for this is the same as for the "X is not a valid Serializable", specifically: new EditableLabel(..).setType(String.class) Is there anybody who thinks that requiring setType(..) call on all components which models don't resolve to a supported type is huge problem? Can this be fixed in 1.5.9? Alec On Thu, Sep 6, 2012 at 2:41 PM, Alec Swan wrote: > I just ran into another problem with type resolution. In fact, it > looks like a bug in org.apache.wicket.util.lang.Objects#convertValue. > The call convertValue(nonNullNonArrayValue, Object.class) will always > return null if nonNullNonArrayValue is a value that is not null and > not an array! > > Is that a legitimate bug? > > Thanks, > > Alec > > On Wed, Sep 5, 2012 at 1:12 AM, dpmihai wrote: >> see this: >> http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-ListMultipleCho >> ice-add-Serializable-values-td4585991.html#a4586026 >> >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Migration-to-1-5-X-is-not- >> a-valid-Serializable-tp4651757p4651764.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Migration to 1.5: 'X' is not a valid Serializable
> Besides calling #setType() do you actually use generics with your models and > components? Sorry, don't quite understand the question. I am not calling setType() hence the problems with type detection in Wicket. Why is it important if I use generics if they are only compile-time syntactic sugar? > See also: > http://wicket.apache.org/apidocs/1.5/org/apache/wicket/markup/html/form/Form > Component.html#setType(java.lang.Class) I don't call setType() and the type passed to Objects#convertValue is Object.class, not String.class, as you would assume from the JavaDoc that String.class would be used. > And the model changes done in 1.4: > https://cwiki.apache.org/WICKET/migrating-to-wicket-14.html#MigratingtoWicke > t1.4-Modelchanges I am migrating from 1.4, so I was using information from this link. Thanks, Alec - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Migration to 1.5: 'X' is not a valid Serializable
>From inside Wicket 1.5.8 the FormComponent:1112
protected void convertInput()
{
// No generics and the type is null
if (typeName == null)
{
try
{
convertedInput =
convertValue(getInputAsArray());
}
...
}
// Via generics
else
{
final IConverter converter =
getConverter(getType());
...
}
}
Thus if you use generics your problem would most likely go away, otherwise
you would have to suffer a bit and you should porb call setType() so Wicket
would know what implementation of IConverter to use.
~ Thank you,
Paul Bors
-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com]
Sent: Thursday, September 06, 2012 6:13 PM
To: users@wicket.apache.org
Subject: Re: Migration to 1.5: 'X' is not a valid Serializable
> Besides calling #setType() do you actually use generics with your
> models and components?
Sorry, don't quite understand the question. I am not calling setType() hence
the problems with type detection in Wicket. Why is it important if I use
generics if they are only compile-time syntactic sugar?
> See also:
> http://wicket.apache.org/apidocs/1.5/org/apache/wicket/markup/html/for
> m/Form
> Component.html#setType(java.lang.Class)
I don't call setType() and the type passed to Objects#convertValue is
Object.class, not String.class, as you would assume from the JavaDoc that
String.class would be used.
> And the model changes done in 1.4:
> https://cwiki.apache.org/WICKET/migrating-to-wicket-14.html#Migratingt
> oWicke
> t1.4-Modelchanges
I am migrating from 1.4, so I was using information from this link.
Thanks,
Alec
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: The Apache Software Foundation Announces Apache Wicket™ 6.0.0
Thanks for your great job
Re: Wicket and Javascript UI Libraries' components
Thank you Martin -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-and-Javascript-UI-Libraries-components-tp4651804p4651828.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: How to specify the html text for span
thanks I used the webmarkupcontainer instead of multilinelabel to solve this issue. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/How-to-specify-the-html-text-for-span-tp4651812p4651829.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
