Re: Apache Wicket releases Wicket 1.5
Martin Grigorov-4 wrote:
http://repo1.maven.org/maven2/org/apache/wicket/wicket-extensions/1.5.0/
http://repo1.maven.org/maven2/org/wicketstuff/wicketstuff-jasperreports/1.5-RC7/
WicketStuff 1.5.0 will be released soon. But since Wicket 1.5.0 is
actually RC7 without code changes they are fully compatible.
Thanks, Martin!
For now we are using the wicketstuff-jasperreports 1.5-RC7 and application
is working.
But all of our integration tests fails with the following exception:
testLoginFormWrongAuthentication(br.gov.to.secad.seg.view.LoginPageTest)
Time elapsed: 0.008 sec ERROR!
java.lang.IllegalStateException: Application name can only be set once.
at org.apache.wicket.Application.setName(Application.java:846)
at
org.apache.wicket.util.tester.BaseWicketTester.init(BaseWicketTester.java:291)
at
org.apache.wicket.util.tester.BaseWicketTester.init(BaseWicketTester.java:241)
at
org.apache.wicket.util.tester.WicketTester.init(WicketTester.java:192)
at br.gov.to.secad.seg.view.LoginPageTest.setUp(LoginPageTest.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
And every test has the following class header:
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations =
{classpath:applicationContext-dataSource.xml,
classpath:applicationContext-jpa.xml})
@TransactionConfiguration(transactionManager = transactionManager,
defaultRollback = false)
public class LoginPageTest {
private WicketTester tester;
@Autowired
private ApplicationContext ctx;
@Autowired
private SEGApplication myWebApplication;
@Before
public void setUp() {
tester = new WicketTester(myWebApplication);
}
@Test
@Transactional
@Rollback(true)
public void testRenderMyPage() {
tester.startPage(LoginPage.class);
tester.assertRenderedPage(LoginPage.class);
//tester.assertComponent(login, LoginComponent.class);
}
I've search in the google and wicket user list, but didn't find any
information about this problem.
Any tip here?
Regards,
Gilberto
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3813838.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: Apache Wicket releases Wicket 1.5
Congratulations! Thanks Wicket team! Here[1], we have an template application(used for every new module) based in the 1.14.17 version. I would like to migrate that template but it depends on wicket-extensions[2] and wicketstuff-jasperreports[3] both are not released yet as you can see. Is there one release date for theses sub-projects? Regards, Gilberto blog.gilbertoca.com www.secad.to.gov.br [1] www.secad.to.gov.br [2] http://mvnrepository.com/artifact/org.apache.wicket/wicket-extensions/1.5-RC5.1 [3] http://mvnrepository.com/artifact/org.wicketstuff/wicketstuff-jasperreports/1.5-RC7 -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3808375.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: Apache Wicket releases Wicket 1.5
http://repo1.maven.org/maven2/org/apache/wicket/wicket-extensions/1.5.0/ http://repo1.maven.org/maven2/org/wicketstuff/wicketstuff-jasperreports/1.5-RC7/ WicketStuff 1.5.0 will be released soon. But since Wicket 1.5.0 is actually RC7 without code changes they are fully compatible. On Mon, Sep 12, 2011 at 10:21 PM, gilbertoca gilbert...@gmail.com wrote: Congratulations! Thanks Wicket team! Here[1], we have an template application(used for every new module) based in the 1.14.17 version. I would like to migrate that template but it depends on wicket-extensions[2] and wicketstuff-jasperreports[3] both are not released yet as you can see. Is there one release date for theses sub-projects? Regards, Gilberto blog.gilbertoca.com www.secad.to.gov.br [1] www.secad.to.gov.br [2] http://mvnrepository.com/artifact/org.apache.wicket/wicket-extensions/1.5-RC5.1 [3] http://mvnrepository.com/artifact/org.wicketstuff/wicketstuff-jasperreports/1.5-RC7 -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3808375.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: Apache Wicket releases Wicket 1.5
very very nice. Thx for all your hard works Best regards Duto - Duto -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3800920.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: Apache Wicket releases Wicket 1.5
Thanks to all the contributors for their hard work! It's been a long wait, so we're very keen to upgrade sometime later this year. Well done! Cheers, Per -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3801433.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: Apache Wicket releases Wicket 1.5
Congratulations! Thank you for this great Framework.
Martijn Dashorst dasho...@apache.org schrieb:
The Apache Wicket team is proud to announce the immediate availability of the
newest release of their component oriented open source Java web framework.
Apache Wicket 1.5 has been in development for the last two years and brings
many improvements over previous versions.
Downloading Apache Wicket 1.5
-
You can download the release here:
http://www.apache.org/dyn/closer.cgi/wicket/1.5.0
Or use this in your Maven POM to upgrade to the new version:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version1.5.0/version
/dependency
Please note that Wicket’s main artifact ID has been renamed to wicket-core.
You will need to upgrade all modules (i.e. wicket, wicket-extensions,
wicket-ioc, wicket-spring, etc) to 1.5.0. It is not possible to mix previous
versions of Wicket with modules of this release.
Most notable changes
With this release the Wicket team has revised many of its internals. A
short list:
- HTML5 components added: EmailTextField, NumberTextField, UrlTextField and
RangeTextField
- New inter-component events (explained below)
- Minimum required servlet API is servlet-api 2.5
- All standard validators now extend Behavior to allow for client side
validations
- IBehavior has been removed and AbstractBehavior has been deprecated, you
should now extend Behavior instead
- Simplified the request cycle processing and made it more extensible
- URL handling is now in one place
- Wicket’s rendering code has been greatly simplified
- Improved browser caching support
- ClientSideImageMap replaces old ImageMap
- Better support for running behind proxies with x-forwarded-for header
- Request cycle listeners make it easier to integrate frameworks in your
Wicket application
- Consistent naming: methods with Javascript in the name have been renamed to
use proper capitalization: JavaScript
- Switching to HTTPS is as simple as configuring a new root mapper to make
Wicket HTTPS aware and annotating a page with @RequireHttps
A longer list of changes and improvements can be found in our migration
guide.
Inter-component events
--
Wicket 1.5 offers a simple, yet flexible, way for component to communicate
with each other in a decoupled manner. The two major interfaces that
facilitate this are:
/**
* Objects that can send events
*/
public interface IEventSource {
T void send(IEventSink sink, Broadcast broadcast, T payload);
}
and
/**
* Objects that can receive events
*/
public interface IEventSink
{
/**
* Called when an event is sent to this sink
*/
void onEvent(IEvent? event);
}
The classes that implement these interfaces, and can thus participate in the
event mechanism are: Component, RequestCycle, Session, and Application.
The mechanism allows for different event broadcast methods defined here:
/**
* Defines the event broadcast type.
*/
public enum Broadcast {
BREADTH,
DEPTH,
BUBBLE,
EXACT;
}
There is an example in wicket-examples which demonstrates the usage of this.
Applications can register custom event dispatchers in FrameworkSettings; the
dispatchers can be used to build custom event delivery mechanisms. For example
a custom IEventDispatcher mechanism can route events to annotated methods, for
example:
public class MyComponent extends Component {
@OnEvent
private void onUserAdded(UserAddedEvent event) {...}
}
where UserAddedEvent is the event payload object.
The default Component#onEvent method will be called even if custom dispatchers
are registered.
A default event is raised whenever Wicket begins to create an AJAX response.
The payload of the event is the AjaxRequestTarget used for event. Sample
implementation:
// component that always adds itself to the ajax response
public class MyCompo
Re: Apache Wicket releases Wicket 1.5
Congratulations and thanks a lot!
On Thu, Sep 8, 2011 at 9:08 AM, Hans Lesmeister
hans.lesmeis...@lessy-software.de wrote:
Congratulations! Thank you for this great Framework.
Martijn Dashorst dasho...@apache.org schrieb:
The Apache Wicket team is proud to announce the immediate availability of
the
newest release of their component oriented open source Java web framework.
Apache Wicket 1.5 has been in development for the last two years and brings
many improvements over previous versions.
Downloading Apache Wicket 1.5
-
You can download the release here:
http://www.apache.org/dyn/closer.cgi/wicket/1.5.0
Or use this in your Maven POM to upgrade to the new version:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version1.5.0/version
/dependency
Please note that Wicket’s main artifact ID has been renamed to wicket-core.
You will need to upgrade all modules (i.e. wicket, wicket-extensions,
wicket-ioc, wicket-spring, etc) to 1.5.0. It is not possible to mix
previous
versions of Wicket with modules of this release.
Most notable changes
With this release the Wicket team has revised many of its internals. A
short list:
- HTML5 components added: EmailTextField, NumberTextField, UrlTextField and
RangeTextField
- New inter-component events (explained below)
- Minimum required servlet API is servlet-api 2.5
- All standard validators now extend Behavior to allow for client side
validations
- IBehavior has been removed and AbstractBehavior has been deprecated, you
should now extend Behavior instead
- Simplified the request cycle processing and made it more extensible
- URL handling is now in one place
- Wicket’s rendering code has been greatly simplified
- Improved browser caching support
- ClientSideImageMap replaces old ImageMap
- Better support for running behind proxies with x-forwarded-for header
- Request cycle listeners make it easier to integrate frameworks in your
Wicket application
- Consistent naming: methods with Javascript in the name have been renamed
to
use proper capitalization: JavaScript
- Switching to HTTPS is as simple as configuring a new root mapper to make
Wicket HTTPS aware and annotating a page with @RequireHttps
A longer list of changes and improvements can be found in our migration
guide.
Inter-component events
--
Wicket 1.5 offers a simple, yet flexible, way for component to communicate
with each other in a decoupled manner. The two major interfaces that
facilitate this are:
/**
* Objects that can send events
*/
public interface IEventSource {
T void send(IEventSink sink, Broadcast broadcast, T payload);
}
and
/**
* Objects that can receive events
*/
public interface IEventSink
{
/**
* Called when an event is sent to this sink
*/
void onEvent(IEvent? event);
}
The classes that implement these interfaces, and can thus participate in
the
event mechanism are: Component, RequestCycle, Session, and Application.
The mechanism allows for different event broadcast methods defined here:
/**
* Defines the event broadcast type.
*/
public enum Broadcast {
BREADTH,
DEPTH,
BUBBLE,
EXACT;
}
There is an example in wicket-examples which demonstrates the usage of
this.
Applications can register custom event dispatchers in FrameworkSettings;
the
dispatchers can be used to build custom event delivery mechanisms. For
example
a custom IEventDispatcher mechanism can route events to annotated methods,
for
example:
public class MyComponent extends Component {
@OnEvent
private void onUserAdded(UserAddedEvent event) {...}
}
where UserAddedEvent is the event payload object.
The default Component#onEvent method will be called even if custom
dispatchers
are registered.
A default event is raised whenever Wicket begins to create an AJAX
response.
The payload of the event is the AjaxRequestTarget used for event. Sample
implementation:
// component that always adds itself to the ajax response
public class MyCompo
Re: Apache Wicket releases Wicket 1.5
Thank you wicket team for all your work and effort!!! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3798223.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: Apache Wicket releases Wicket 1.5
Thank you WTeam! =) *Bruno Borges* (21) 7672-7099 *www.brunoborges.com* On Thu, Sep 8, 2011 at 6:00 AM, rebecca rivka.shis...@gmail.com wrote: Thank you wicket team for all your work and effort!!! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3798223.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: Apache Wicket releases Wicket 1.5
Thanks a lot wicketers! Wicket is a really great and smart piece of
software!
Regards,
Peter.
--
http://jetsli.de news reader for geeks
The Apache Wicket team is proud to announce the immediate availability of the
newest release of their component oriented open source Java web framework.
Apache Wicket 1.5 has been in development for the last two years and brings
many improvements over previous versions.
Downloading Apache Wicket 1.5
-
You can download the release here:
http://www.apache.org/dyn/closer.cgi/wicket/1.5.0
Or use this in your Maven POM to upgrade to the new version:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version1.5.0/version
/dependency
Please note that Wicket’s main artifact ID has been renamed to wicket-core.
You will need to upgrade all modules (i.e. wicket, wicket-extensions,
wicket-ioc, wicket-spring, etc) to 1.5.0. It is not possible to mix previous
versions of Wicket with modules of this release.
Most notable changes
With this release the Wicket team has revised many of its internals. A
short list:
- HTML5 components added: EmailTextField, NumberTextField, UrlTextField and
RangeTextField
- New inter-component events (explained below)
- Minimum required servlet API is servlet-api 2.5
- All standard validators now extend Behavior to allow for client side
validations
- IBehavior has been removed and AbstractBehavior has been deprecated, you
should now extend Behavior instead
- Simplified the request cycle processing and made it more extensible
- URL handling is now in one place
- Wicket’s rendering code has been greatly simplified
- Improved browser caching support
- ClientSideImageMap replaces old ImageMap
- Better support for running behind proxies with x-forwarded-for header
- Request cycle listeners make it easier to integrate frameworks in your
Wicket application
- Consistent naming: methods with Javascript in the name have been renamed to
use proper capitalization: JavaScript
- Switching to HTTPS is as simple as configuring a new root mapper to make
Wicket HTTPS aware and annotating a page with @RequireHttps
A longer list of changes and improvements can be found in our migration
guide.
Inter-component events
--
Wicket 1.5 offers a simple, yet flexible, way for component to communicate
with each other in a decoupled manner. The two major interfaces that
facilitate this are:
/**
* Objects that can send events
*/
public interface IEventSource {
T void send(IEventSink sink, Broadcast broadcast, T payload);
}
and
/**
* Objects that can receive events
*/
public interface IEventSink
{
/**
* Called when an event is sent to this sink
*/
void onEvent(IEvent? event);
}
The classes that implement these interfaces, and can thus participate in the
event mechanism are: Component, RequestCycle, Session, and Application.
The mechanism allows for different event broadcast methods defined here:
/**
* Defines the event broadcast type.
*/
public enum Broadcast {
BREADTH,
DEPTH,
BUBBLE,
EXACT;
}
There is an example in wicket-examples which demonstrates the usage of this.
Applications can register custom event dispatchers in FrameworkSettings; the
dispatchers can be used to build custom event delivery mechanisms. For example
a custom IEventDispatcher mechanism can route events to annotated methods, for
example:
public class MyComponent extends Component {
@OnEvent
private void onUserAdded(UserAddedEvent event) {...}
}
where UserAddedEvent is the event payload object.
The default Component#onEvent method will be called even if custom dispatchers
are registered.
A default event is raised whenever Wicket begins to create an AJAX response.
The payload of the event is the AjaxRequestTarget used for event. Sample
implementation:
// component that always adds itself to the ajax response
public class MyComponent extends Component {
public void onEvent(IEvent event) {
if (event.getPayload() instanceof AjaxRequestTarget) {
((AjaxRequestTarget)event.getPayload()).add(this);
}
}
}
-
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: Apache Wicket releases Wicket 1.5
thumbs up :)
-Nino
2011/9/8 Peter Karich peat...@yahoo.de:
Thanks a lot wicketers! Wicket is a really great and smart piece of
software!
Regards,
Peter.
--
http://jetsli.de news reader for geeks
The Apache Wicket team is proud to announce the immediate availability of the
newest release of their component oriented open source Java web framework.
Apache Wicket 1.5 has been in development for the last two years and brings
many improvements over previous versions.
Downloading Apache Wicket 1.5
-
You can download the release here:
http://www.apache.org/dyn/closer.cgi/wicket/1.5.0
Or use this in your Maven POM to upgrade to the new version:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version1.5.0/version
/dependency
Please note that Wicket’s main artifact ID has been renamed to wicket-core.
You will need to upgrade all modules (i.e. wicket, wicket-extensions,
wicket-ioc, wicket-spring, etc) to 1.5.0. It is not possible to mix previous
versions of Wicket with modules of this release.
Most notable changes
With this release the Wicket team has revised many of its internals. A
short list:
- HTML5 components added: EmailTextField, NumberTextField, UrlTextField and
RangeTextField
- New inter-component events (explained below)
- Minimum required servlet API is servlet-api 2.5
- All standard validators now extend Behavior to allow for client side
validations
- IBehavior has been removed and AbstractBehavior has been deprecated, you
should now extend Behavior instead
- Simplified the request cycle processing and made it more extensible
- URL handling is now in one place
- Wicket’s rendering code has been greatly simplified
- Improved browser caching support
- ClientSideImageMap replaces old ImageMap
- Better support for running behind proxies with x-forwarded-for header
- Request cycle listeners make it easier to integrate frameworks in your
Wicket application
- Consistent naming: methods with Javascript in the name have been renamed
to
use proper capitalization: JavaScript
- Switching to HTTPS is as simple as configuring a new root mapper to make
Wicket HTTPS aware and annotating a page with @RequireHttps
A longer list of changes and improvements can be found in our migration
guide.
Inter-component events
--
Wicket 1.5 offers a simple, yet flexible, way for component to communicate
with each other in a decoupled manner. The two major interfaces that
facilitate this are:
/**
* Objects that can send events
*/
public interface IEventSource {
T void send(IEventSink sink, Broadcast broadcast, T payload);
}
and
/**
* Objects that can receive events
*/
public interface IEventSink
{
/**
* Called when an event is sent to this sink
*/
void onEvent(IEvent? event);
}
The classes that implement these interfaces, and can thus participate in the
event mechanism are: Component, RequestCycle, Session, and Application.
The mechanism allows for different event broadcast methods defined here:
/**
* Defines the event broadcast type.
*/
public enum Broadcast {
BREADTH,
DEPTH,
BUBBLE,
EXACT;
}
There is an example in wicket-examples which demonstrates the usage of this.
Applications can register custom event dispatchers in FrameworkSettings; the
dispatchers can be used to build custom event delivery mechanisms. For
example
a custom IEventDispatcher mechanism can route events to annotated methods,
for
example:
public class MyComponent extends Component {
@OnEvent
private void onUserAdded(UserAddedEvent event) {...}
}
where UserAddedEvent is the event payload object.
The default Component#onEvent method will be called even if custom
dispatchers
are registered.
A default event is raised whenever Wicket begins to create an AJAX response.
The payload of the event is the AjaxRequestTarget used for event. Sample
implementation:
// component that always adds itself to the ajax response
public class MyComponent extends Component {
public void onEvent(IEvent event) {
if (event.getPayload() instanceof AjaxRequestTarget) {
((AjaxRequestTarget)event.getPayload()).add(this);
}
}
}
-
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:
Re: Apache Wicket releases Wicket 1.5
I think this version represents a very important step for the evolution
of Wicket. With 1.5 many of the core entities have been re-engineered
and the result is a great piece of software!
The Apache Wicket team is proud to announce the immediate availability of the
newest release of their component oriented open source Java web framework.
Apache Wicket 1.5 has been in development for the last two years and brings
many improvements over previous versions.
Downloading Apache Wicket 1.5
-
You can download the release here:
http://www.apache.org/dyn/closer.cgi/wicket/1.5.0
Or use this in your Maven POM to upgrade to the new version:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version1.5.0/version
/dependency
Please note that Wicket’s main artifact ID has been renamed to wicket-core.
You will need to upgrade all modules (i.e. wicket, wicket-extensions,
wicket-ioc, wicket-spring, etc) to 1.5.0. It is not possible to mix previous
versions of Wicket with modules of this release.
Most notable changes
With this release the Wicket team has revised many of its internals. A
short list:
- HTML5 components added: EmailTextField, NumberTextField, UrlTextField and
RangeTextField
- New inter-component events (explained below)
- Minimum required servlet API is servlet-api 2.5
- All standard validators now extend Behavior to allow for client side
validations
- IBehavior has been removed and AbstractBehavior has been deprecated, you
should now extend Behavior instead
- Simplified the request cycle processing and made it more extensible
- URL handling is now in one place
- Wicket’s rendering code has been greatly simplified
- Improved browser caching support
- ClientSideImageMap replaces old ImageMap
- Better support for running behind proxies with x-forwarded-for header
- Request cycle listeners make it easier to integrate frameworks in your
Wicket application
- Consistent naming: methods with Javascript in the name have been renamed to
use proper capitalization: JavaScript
- Switching to HTTPS is as simple as configuring a new root mapper to make
Wicket HTTPS aware and annotating a page with @RequireHttps
A longer list of changes and improvements can be found in our migration
guide.
Inter-component events
--
Wicket 1.5 offers a simple, yet flexible, way for component to communicate
with each other in a decoupled manner. The two major interfaces that
facilitate this are:
/**
* Objects that can send events
*/
public interface IEventSource {
T void send(IEventSink sink, Broadcast broadcast, T payload);
}
and
/**
* Objects that can receive events
*/
public interface IEventSink
{
/**
* Called when an event is sent to this sink
*/
void onEvent(IEvent? event);
}
The classes that implement these interfaces, and can thus participate in the
event mechanism are: Component, RequestCycle, Session, and Application.
The mechanism allows for different event broadcast methods defined here:
/**
* Defines the event broadcast type.
*/
public enum Broadcast {
BREADTH,
DEPTH,
BUBBLE,
EXACT;
}
There is an example in wicket-examples which demonstrates the usage of this.
Applications can register custom event dispatchers in FrameworkSettings; the
dispatchers can be used to build custom event delivery mechanisms. For example
a custom IEventDispatcher mechanism can route events to annotated methods, for
example:
public class MyComponent extends Component {
@OnEvent
private void onUserAdded(UserAddedEvent event) {...}
}
where UserAddedEvent is the event payload object.
The default Component#onEvent method will be called even if custom dispatchers
are registered.
A default event is raised whenever Wicket begins to create an AJAX response.
The payload of the event is the AjaxRequestTarget used for event. Sample
implementation:
// component that always adds itself to the ajax response
public class MyComponent extends Component {
public void onEvent(IEvent event) {
if (event.getPayload() instanceof AjaxRequestTarget) {
((AjaxRequestTarget)event.getPayload()).add(this);
}
}
}
-
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: Apache Wicket releases Wicket 1.5
Congratulations to new 1.5 version. M. Am 08.09.2011 00:17, schrieb Martijn Dashorst: The Apache Wicket team is proud to announce the immediate availability of the newest release of their component oriented open source Java web framework. Apache Wicket 1.5 has been in development for the last two years and brings many improvements over previous versions. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Apache Wicket releases Wicket 1.5
Congratulations, it's a Wicket! Great work! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3799758.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: Apache Wicket releases Wicket 1.5
Woohoo! Thanks to all involved in making this happen. Now I can start working in our migration! -Nelson Segura - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Apache Wicket releases Wicket 1.5
Congratulations and thanks for great work :) Kailash Yadav -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3800719.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
Apache Wicket releases Wicket 1.5
The Apache Wicket team is proud to announce the immediate availability of the
newest release of their component oriented open source Java web framework.
Apache Wicket 1.5 has been in development for the last two years and brings
many improvements over previous versions.
Downloading Apache Wicket 1.5
-
You can download the release here:
http://www.apache.org/dyn/closer.cgi/wicket/1.5.0
Or use this in your Maven POM to upgrade to the new version:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version1.5.0/version
/dependency
Please note that Wicket’s main artifact ID has been renamed to wicket-core.
You will need to upgrade all modules (i.e. wicket, wicket-extensions,
wicket-ioc, wicket-spring, etc) to 1.5.0. It is not possible to mix previous
versions of Wicket with modules of this release.
Most notable changes
With this release the Wicket team has revised many of its internals. A
short list:
- HTML5 components added: EmailTextField, NumberTextField, UrlTextField and
RangeTextField
- New inter-component events (explained below)
- Minimum required servlet API is servlet-api 2.5
- All standard validators now extend Behavior to allow for client side
validations
- IBehavior has been removed and AbstractBehavior has been deprecated, you
should now extend Behavior instead
- Simplified the request cycle processing and made it more extensible
- URL handling is now in one place
- Wicket’s rendering code has been greatly simplified
- Improved browser caching support
- ClientSideImageMap replaces old ImageMap
- Better support for running behind proxies with x-forwarded-for header
- Request cycle listeners make it easier to integrate frameworks in your
Wicket application
- Consistent naming: methods with Javascript in the name have been renamed to
use proper capitalization: JavaScript
- Switching to HTTPS is as simple as configuring a new root mapper to make
Wicket HTTPS aware and annotating a page with @RequireHttps
A longer list of changes and improvements can be found in our migration
guide.
Inter-component events
--
Wicket 1.5 offers a simple, yet flexible, way for component to communicate
with each other in a decoupled manner. The two major interfaces that
facilitate this are:
/**
* Objects that can send events
*/
public interface IEventSource {
T void send(IEventSink sink, Broadcast broadcast, T payload);
}
and
/**
* Objects that can receive events
*/
public interface IEventSink
{
/**
* Called when an event is sent to this sink
*/
void onEvent(IEvent? event);
}
The classes that implement these interfaces, and can thus participate in the
event mechanism are: Component, RequestCycle, Session, and Application.
The mechanism allows for different event broadcast methods defined here:
/**
* Defines the event broadcast type.
*/
public enum Broadcast {
BREADTH,
DEPTH,
BUBBLE,
EXACT;
}
There is an example in wicket-examples which demonstrates the usage of this.
Applications can register custom event dispatchers in FrameworkSettings; the
dispatchers can be used to build custom event delivery mechanisms. For example
a custom IEventDispatcher mechanism can route events to annotated methods, for
example:
public class MyComponent extends Component {
@OnEvent
private void onUserAdded(UserAddedEvent event) {...}
}
where UserAddedEvent is the event payload object.
The default Component#onEvent method will be called even if custom dispatchers
are registered.
A default event is raised whenever Wicket begins to create an AJAX response.
The payload of the event is the AjaxRequestTarget used for event. Sample
implementation:
// component that always adds itself to the ajax response
public class MyComponent extends Component {
public void onEvent(IEvent event) {
if (event.getPayload() instanceof AjaxRequestTarget) {
((AjaxRequestTarget)event.getPayload()).add(this);
}
}
}
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Apache Wicket releases Wicket 1.5
On Thu, 8 Sep 2011 00:17:25 +0200 Martijn Dashorst dasho...@apache.org wrote: The Apache Wicket team is proud to announce the immediate availability of the newest release of their component oriented open source Java web framework. Apache Wicket 1.5 has been in development for the last two years and brings many improvements over previous versions. Congratulations! And thanks to the Wicket team for the good work. Carl-Eric www.wicketbuch.de - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Apache Wicket releases Wicket 1.5
Hooray!! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Apache-Wicket-releases-Wicket-1-5-tp3797412p3797722.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: Apache Wicket releases Wicket 1.5
Big news! You made my day. Thanks a lot for your great working.
On 9/8/11 5:17 AM, Martijn Dashorst wrote:
The Apache Wicket team is proud to announce the immediate availability of the
newest release of their component oriented open source Java web framework.
Apache Wicket 1.5 has been in development for the last two years and brings
many improvements over previous versions.
Downloading Apache Wicket 1.5
-
You can download the release here:
http://www.apache.org/dyn/closer.cgi/wicket/1.5.0
Or use this in your Maven POM to upgrade to the new version:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version1.5.0/version
/dependency
Please note that Wicket’s main artifact ID has been renamed to wicket-core.
You will need to upgrade all modules (i.e. wicket, wicket-extensions,
wicket-ioc, wicket-spring, etc) to 1.5.0. It is not possible to mix previous
versions of Wicket with modules of this release.
Most notable changes
With this release the Wicket team has revised many of its internals. A
short list:
- HTML5 components added: EmailTextField, NumberTextField, UrlTextField and
RangeTextField
- New inter-component events (explained below)
- Minimum required servlet API is servlet-api 2.5
- All standard validators now extend Behavior to allow for client side
validations
- IBehavior has been removed and AbstractBehavior has been deprecated, you
should now extend Behavior instead
- Simplified the request cycle processing and made it more extensible
- URL handling is now in one place
- Wicket’s rendering code has been greatly simplified
- Improved browser caching support
- ClientSideImageMap replaces old ImageMap
- Better support for running behind proxies with x-forwarded-for header
- Request cycle listeners make it easier to integrate frameworks in your
Wicket application
- Consistent naming: methods with Javascript in the name have been renamed to
use proper capitalization: JavaScript
- Switching to HTTPS is as simple as configuring a new root mapper to make
Wicket HTTPS aware and annotating a page with @RequireHttps
A longer list of changes and improvements can be found in our migration
guide.
Inter-component events
--
Wicket 1.5 offers a simple, yet flexible, way for component to communicate
with each other in a decoupled manner. The two major interfaces that
facilitate this are:
/**
* Objects that can send events
*/
public interface IEventSource {
T void send(IEventSink sink, Broadcast broadcast, T payload);
}
and
/**
* Objects that can receive events
*/
public interface IEventSink
{
/**
* Called when an event is sent to this sink
*/
void onEvent(IEvent? event);
}
The classes that implement these interfaces, and can thus participate in the
event mechanism are: Component, RequestCycle, Session, and Application.
The mechanism allows for different event broadcast methods defined here:
/**
* Defines the event broadcast type.
*/
public enum Broadcast {
BREADTH,
DEPTH,
BUBBLE,
EXACT;
}
There is an example in wicket-examples which demonstrates the usage of this.
Applications can register custom event dispatchers in FrameworkSettings; the
dispatchers can be used to build custom event delivery mechanisms. For example
a custom IEventDispatcher mechanism can route events to annotated methods, for
example:
public class MyComponent extends Component {
@OnEvent
private void onUserAdded(UserAddedEvent event) {...}
}
where UserAddedEvent is the event payload object.
The default Component#onEvent method will be called even if custom dispatchers
are registered.
A default event is raised whenever Wicket begins to create an AJAX response.
The payload of the event is the AjaxRequestTarget used for event. Sample
implementation:
// component that always adds itself to the ajax response
public class MyComponent extends Component {
public void onEvent(IEvent event) {
if (event.getPayload() instanceof AjaxRequestTarget) {
((AjaxRequestTarget)event.getPayload()).add(this);
}
}
}
-
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: Apache Wicket releases Wicket 1.5
Congratulations! The event system is really a bliss. F. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Apache Wicket releases Wicket 1.5
w00t, Wicket FTW!
On 2011-09-08 05:31, Duy Do wrote:
Big news! You made my day. Thanks a lot for your great working.
On 9/8/11 5:17 AM, Martijn Dashorst wrote:
The Apache Wicket team is proud to announce the immediate
availability of the
newest release of their component oriented open source Java web
framework.
Apache Wicket 1.5 has been in development for the last two years and
brings
many improvements over previous versions.
Downloading Apache Wicket 1.5
-
You can download the release here:
http://www.apache.org/dyn/closer.cgi/wicket/1.5.0
Or use this in your Maven POM to upgrade to the new version:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-core/artifactId
version1.5.0/version
/dependency
Please note that Wicket’s main artifact ID has been renamed to
wicket-core.
You will need to upgrade all modules (i.e. wicket, wicket-extensions,
wicket-ioc, wicket-spring, etc) to 1.5.0. It is not possible to mix
previous
versions of Wicket with modules of this release.
Most notable changes
With this release the Wicket team has revised many of its internals. A
short list:
- HTML5 components added: EmailTextField, NumberTextField,
UrlTextField and
RangeTextField
- New inter-component events (explained below)
- Minimum required servlet API is servlet-api 2.5
- All standard validators now extend Behavior to allow for client side
validations
- IBehavior has been removed and AbstractBehavior has been
deprecated, you
should now extend Behavior instead
- Simplified the request cycle processing and made it more extensible
- URL handling is now in one place
- Wicket’s rendering code has been greatly simplified
- Improved browser caching support
- ClientSideImageMap replaces old ImageMap
- Better support for running behind proxies with x-forwarded-for
header
- Request cycle listeners make it easier to integrate frameworks in
your
Wicket application
- Consistent naming: methods with Javascript in the name have been
renamed to
use proper capitalization: JavaScript
- Switching to HTTPS is as simple as configuring a new root mapper
to make
Wicket HTTPS aware and annotating a page with @RequireHttps
A longer list of changes and improvements can be found in our migration
guide.
Inter-component events
--
Wicket 1.5 offers a simple, yet flexible, way for component to
communicate
with each other in a decoupled manner. The two major interfaces that
facilitate this are:
/**
* Objects that can send events
*/
public interface IEventSource {
T void send(IEventSink sink, Broadcast broadcast, T payload);
}
and
/**
* Objects that can receive events
*/
public interface IEventSink
{
/**
* Called when an event is sent to this sink
*/
void onEvent(IEvent? event);
}
The classes that implement these interfaces, and can thus participate
in the
event mechanism are: Component, RequestCycle, Session, and Application.
The mechanism allows for different event broadcast methods defined here:
/**
* Defines the event broadcast type.
*/
public enum Broadcast {
BREADTH,
DEPTH,
BUBBLE,
EXACT;
}
There is an example in wicket-examples which demonstrates the usage
of this.
Applications can register custom event dispatchers in
FrameworkSettings; the
dispatchers can be used to build custom event delivery mechanisms.
For example
a custom IEventDispatcher mechanism can route events to annotated
methods, for
example:
public class MyComponent extends Component {
@OnEvent
private void onUserAdded(UserAddedEvent event) {...}
}
where UserAddedEvent is the event payload object.
The default Component#onEvent method will be called even if custom
dispatchers
are registered.
A default event is raised whenever Wicket begins to create an AJAX
response.
The payload of the event is the AjaxRequestTarget used for event. Sample
implementation:
// component that always adds itself to the ajax response
public class MyComponent extends Component {
public void onEvent(IEvent event) {
if (event.getPayload() instanceof AjaxRequestTarget) {
((AjaxRequestTarget)event.getPayload()).add(this);
}
}
}
-
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:
