Hi,
they actually should use the extender constants, but also the new
HttpWhiteboardConstants :)
regards, Achim
2017-06-20 2:22 GMT+02:00 Eben Stewart :
> ok, correct me if I am wrong
>
> in HttpContextTracker (org.ops4j.pax.web.extender.
> whiteboard.internal.tracker)
>
> HttpContextElemen
ok, correct me if I am wrong
in HttpContextTracker
(org.ops4j.pax.web.extender.whiteboard.internal.tracker)
HttpContextElement createHttpContextElement(final
ServiceReference serviceReference, final HttpContext
published) {
String httpContextId =
ServicePropertiesUtils.getStringProperty(s
Sounds good... knowing the history, and the future dev plans, especially if
they make it into the OSGI spec, is always good :D
I'm taking from your comments that the ExtenderConstants are not long term?
It would be better to have an HttpWhiteboardConstants way of doing it?
I think all the anno
All -
I have been struggling with DB connection errors with PAX-JDBC for a while
now, and I couldn't really get my mind around it.
Just today I noticed something really bizar. On a Windows Server, PAX-JDBC
(sometimes) ends up in a loop creating DB connections until the OS runs out
of resources
Hi,
thanks for the sample, will see to it.
regarding the comments/remarks, see my comments inline :)
Achim
2017-06-19 14:50 GMT+02:00 Eben Stewart :
> Attached is a working example, the smallest I could get it (project is
> bndtools under Eclipse)
>
> A few points that threw me off, that did no
Ahh I see most of the changes where from 6.x to 7.x..
But what about the Websocket stuff, as I remember it has been changed alot
in Wicket 8..?
On Mon, Jun 19, 2017 at 2:55 PM, 'Christoph Läubrich' via OPS4J <
ops4j@googlegroups.com> wrote:
> I opened a bug to Wicket 8: https://issues.apache.org
I opened a bug to Wicket 8:
https://issues.apache.org/jira/browse/WICKET-6402 it seems they lost the
OSGi Manifest information in Wicket 8 what is bad. Beside thsi there
seem no API changes that influence Pax-Wicket so once Wicket 8 is
release we can raise the version range instead of supply a
Attached is a working example, the smallest I could get it (project is
bndtools under Eclipse)
A few points that threw me off, that did not seem clear at first (although
they make sense now) - a lot of it had to do with the whiteboard extensions
to get resources and jsp support - I am not aware
Hi Nino,
I created the branch v3.1.x, it is working so far beside the karaf tests
fail with
Server returned HTTP response code: 401 for URL:
http://localhost:8181/issues
any idea what is causing this? If we have sorted this out I think we
should make this the 4.0 version and make wicket 8
Ok great, let me know If I can do something..
On Mon, Jun 19, 2017 at 11:40 AM, 'Christoph Läubrich' via OPS4J <
ops4j@googlegroups.com> wrote:
> Hi Nino,
>
> I'm currently trying to upgrade the master from Wicket 6-->7 to see what
> have changed and will then go on to 7-->8 I think this might br
Hi Nino,
I'm currently trying to upgrade the master from Wicket 6-->7 to see what
have changed and will then go on to 7-->8 I think this might bring some
light into this issue.
Am 22.05.2017 06:55, schrieb nino martinez wael:
Hi
Over 2 months ago I made the last changes to the 4.x.y branch[
Found the issue: The logmessage simply has wrong parameter order and a
missleading logger name, beside this this has no impact on the code
since we scan the classpath for pax-wicket annotations
The real cause for the waring is:
https://stackoverflow.com/questions/12142872/java-lang-classformat
12 matches
Mail list logo
