>
> Achim, I still has ClassNotFoundException of my class. This is what I have
> in MANIFEST file.
>
Manifest-Version: 1.0
Bundle-Description: Attaching com.riits.handlers to pax web jetty
Bundle-SymbolicName: com.riits.handlers
Archiver-Version: Plexus Archiver
Built-By: d.pham
Bundle-Manifest
After do some reading. I got a jar file that content my custom handler
class and the manifest has these info below. I am not really sure it is
correct, could someone let me know: ( is my class on the import-package or
export-package ?)
Manifest-Version: 1.0
Bundle-Description: Attaching com.riit
I am googling about fragment bundle now and will post back what I think
later
>
>
--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
---
You received this message because you are subscribed to the Google Groups
"OPS4J" group.
To unsubscribe from this group and s
I am happy to hear there is away to have it works. Could you please point
me to where (document , example...) I can create a fragment bundle which
attaches to the pax-web jetty bundle as you said. I am new to this stuffs,
but I can catch up it quickly.
>
>
--
--
--
OPS4J - h
Hi
good question, something I would need to dig into.
One thing that should always work is to create a fragment bundle which
attaches to the pax-web jetty bundle.
In that case it's a common classloader and therefore is visible.
Otherwise we would need some extra service handling for this.
Again so
I have pax web 6.0.3 and Jetty 9.3.14 in my environment.
>
>
>
--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
---
You received this message because you are subscribed to the Google Groups
"OPS4J" group.
To unsubscribe from this group and stop receiving emails
I have pax web 6.0.3 and Jetty 9.3.14 in my environment.
On Wednesday, December 20, 2017 at 9:18:19 AM UTC-8, dt pham wrote:
>
> I have a very special requirement that I have to write my own Jetty
> Handler. I looked at the IPAccessHandler from Jetty and I successfully
> configure a my-jetty.xml
I have a very special requirement that I have to write my own Jetty
Handler. I looked at the IPAccessHandler from Jetty and I successfully
configure a my-jetty.xml to have pax-web loads it. The IPAccessHandler is
working good on my Talend Karaf runtime. So I kind of want to do the same
as IPAcc
cool,
I'm gonna wait a bit longer for some more feedback, in case.
I'll cut the release latest on the 23rd, unless we need to hurry?
Regards, Achim
2017-12-20 14:40 GMT+01:00 Grzegorz Grzybek :
> Thanks Achim for comment - I'll do my changes in 6.1.1 ;)
>
> regards
> Grzegorz Grzybek
>
> 2017-1
Thanks Achim for comment - I'll do my changes in 6.1.1 ;)
regards
Grzegorz Grzybek
2017-12-20 13:45 GMT+01:00 'Achim Nierbeck' via OPS4J <
ops4j@googlegroups.com>:
> Hi,
>
> afaik we're all set to have a 6.1 release.
> @Grzegorz, I'd say release now with the current set and with 6.1.1 we can
> s
Hi,
afaik we're all set to have a 6.1 release.
@Grzegorz, I'd say release now with the current set and with 6.1.1 we can
ship a complete setup :)
we also are set on the Tomcat front as far as I can see right now :)
Unless Stephan Siano does say so otherwise I'm fine with it.
regards, Achim
20
+0.99 from me
why not +1? I have only one little concern and I hope it's not that
important.
With https://ops4j1.jira.com/browse/PAXWEB-1103 I added support for
undertow.xml based configuration, which is based on these two XSDs:
- urn:jboss:domain:4.2
- urn:jboss:domain:undertow:3.1
I used the
12 matches
Mail list logo
