[PAXWICKET-293] Make sure that there are no race conditions between listener and executor

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-294] Guard against various curious exceptions

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-295] Adapt page factory behavior to original one

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-296] Upgrade to wiquery 1.2.4

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[maven-release-plugin] prepare release wicket-0.8.0
[maven-release-plugin] prepare for next development iteration
[PAXWICKET-298] Small improvement in method checks.

(cherry picked from commit bbe355795d2ca48323ca56f6833d8a0245cd7470)

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-165] Update to wicket 1.5.4.

At least the very first approach. The sources are compiling right now
and various examples are working again. Still ways to go...

(cherry picked from commit f486d0de6223d6772c3f5743c07563622debb4b5)

Conflicts:

	service/src/main/java/org/ops4j/pax/wicket/internal/PaxWicketPageFactory.java

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-165] All tests, except the itests, are running again

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-300] Upgrade to wiquery 1.5.3

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-165] Adapt all examples to latest wicket version

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-301] fix that init-params are ignored at applications

the problem was that we simply forgot to include them into the startup
process of the application. This had been fixed by adding the old param
to the new application again.

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
(cherry picked from commit 163628fc80cda4a02c97f08f81f7680d356b5b82)

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-158] Corrected changelog for 0.8.0 version

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-305] Fix NPE when defining a Wicket application in a bundle without any .class resource

While I think it's quite a rare usecase to do this it's still a valid
problem which is fixed by this patch.

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
(cherry picked from commit c41d3a7b87ebadb1b228ffd5b8a45544b778e535)

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-306] NPE during bean resolvement failure handling

This one was an especially pitty one since the NPE was thrown during the creation
of the error message hiding the real problem. Many thanks to Sebastian
Gonzalez Oyuela for spotting this one.

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
(cherry picked from commit 3da298bbc21f9392242f6d9cccf2c7cd1c1cc1c4)

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-307] Fixed serialization warning problem

The big problem was that the serialisizable checker used directly from
pax-wicket does not take into account that bundle-context and bundle are
serializable (with our own method, but still). This leads to REALLY
annoying error messages.

The additional problem was that we're not able to modifiy the wicket
SerializableChecker by extension: (a) the class was final and (b) there
where no extension points at the right places.

This patch adds a copy of the wicket SerializiableChecker, adds
additional extension points and:

(a) removes the final modfier
(b) adds a validateAdditionalSerializableConditions method which can be
overwritten (optionally) and extends the validation if an object is
serializable
(c) adds an additionalObjectReplacements method which is called during
the replaceObject stream method and allows to hook this process too.

With this patched class we're finally able to modfiy the the
SerializableChecker by errrors in the OutputStream to print the real,
internal errors. This should make working with PW ways easier.

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
(cherry picked from commit 5545ed3dcd6dd5439f700aa2047af6914ea2c223)

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-313] Upgrade to wicket 1.5.5

(Might take some additional few hours for 1.5.5 to reach m2 central)

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-165] Fixed final integration tests

Boah, I cant believe it. Finally really all of them ran green for me
again!

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-314] Upgrade to pax-logging 1.6.5

Signed-off-by: Andreas Pieber <anpieber@gmail.com>
[PAXWICKET-241] Upgrade itests to pax-exam 2.4.0.RC1

This patch sets the itests to version 2.4.0.RC1

Signed-off-by: Andreas Pieber <anpieber@gmail.com>