I think Martin had created an issue about it some weeks ago...
Hi,
I think we could leverage async support built-in in Servlet 3.x. To prevent
developers doing long tasks in the detach method, I would suggest an error
log trace telling the problem.
Regards,
__
Cedric Gatay (@Cedric_Gatay
Hi,
On Wed, Jun 26, 2013 at 10:38 AM, Andrea Del Bene an.delb...@gmail.comwrote:
I think Martin had created an issue about it some weeks ago...
Yes.
For the async dispatching - few weeks ago
(WICKET-5152https://issues.apache.org/jira/browse/WICKET-5152)
, for the twice called #onDetach()
About the twice called #onDetach() - when I found it (WICKET-4012) Igor
explained to me that there is no contract for #onDetach() to be called just
once per request cycle, so it is fine. And usually the impl of #onDetach()
is either empty or something trivial and fast.
But I think we should try
Hi all,
I'd like to discuss where we are with Wicket 7 and what to do next.
At the moment there are just
Hi,
On Wed, Jun 26, 2013 at 1:31 PM, John Sarman johnsar...@gmail.com wrote:
First,
I was able to integrate Weld-api-2.0 with only a few changes to the cdi-1.0
base code which was branched into cdi-1.1 around march.
That being said Martin suggests that the final design be split into
I am currently working on splitting the codebase as you suggested similar
to the websocket structure. However the way the app pom will be is similar
to Atmosphere's requirement of adding the stubs at app level.
The reason for this is because the cdi ref impl may or may not already be
in the app.
On Wed, Jun 26, 2013 at 2:49 PM, John Sarman johnsar...@gmail.com wrote:
I am currently working on splitting the codebase as you suggested similar
to the websocket structure. However the way the app pom will be is similar
to Atmosphere's requirement of adding the stubs at app level.
The
INFO:
validateJarFile(WicketCdiExample-2.0-SNAPSHOT\WEB-INF\lib\el-api-2.2.jar) -
jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/el/Expression.class
More precisely cdi-1.1 has a transitive dependency with el-api-2.2.jar and
it does not get loaded. The app works fine
Hello,
I know this is not on the roadmap right now, but I wanted to bring up
one feature from the wishlist which I recently updated. From the wiki:
Better stateless support
add more stateless components (stateless versions of existing
components)
adopt Ajax stateless behaviors
If you're asking what else could go in, better async support for long
running tasks would be a great addition - perhaps some simple job
management. There are a couple of examples out on the web, and we built
our own a while back, but Id rather the framework provided such support
(with associated
GitHub user jsarman opened a pull request:
https://github.com/apache/wicket/pull/48
Port of wicket-cdi to support cdi-1.1
Package is split up into wicket-cdi-1.1-core and wicket-cdi-1.1-weld.
Placed in wicket-experimental package.
Refactored some classes to use cdi injection
Github user jsarman closed the pull request at:
https://github.com/apache/wicket/pull/47
I just sent a pull request for the refactor Martin described. Also updated
the example code https://github.com/jsarman/WicketCdiExample
Code is setup to work with tomcat 7.
On Wed, Jun 26, 2013 at 8:20 AM, John Sarman johnsar...@gmail.com wrote:
INFO:
On Wed, Jun 26, 2013 at 4:20 AM, Martin Grigorov mgrigo...@apache.org wrote:
Hi all,
I'd like to discuss where we are with Wicket 7 and what to do next.
At the moment there are just
i may be able to help here. ive recently written a descent polling
panel we use to execute long-running sql queries. its not async in the
sense that it does not work via servlet 3 async requests - it polls
with ajax. but, unlike lazyloadpanel we have now this one doesnt block
access to the page,
Hi,
I second what Bertrand said. I think having more statelessness in core
Wicket ajax. I think this is the way to go since it eases deployment of
large instance of our applications. However there is a big pile of work
for this, so if Wicket 7 is said to be released soon, I guess we'd better
On Wed, Jun 26, 2013 at 1:29 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
On Wed, Jun 26, 2013 at 4:20 AM, Martin Grigorov mgrigo...@apache.org
wrote:
Hi all,
I'd like to discuss where we are with Wicket 7 and what to do next.
At the moment there are just
3
Hi,
About stateless ajax behaviors - the Jolira components and behaviors have
been moved to WicketStuff (
https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/stateless-parent)
since two releases. There were two Pull Requests already.
Use them, extend them, polish them and at some
[x] Yes, release Apache Wicket 6.9.0 (non binding)
On Sun, Jun 23, 2013 at 10:01 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
This is a vote to release Apache Wicket 6.9.0
Please download the source distributions found in our staging area
linked below.
I have included the
19 matches
Mail list logo
