Typo:
Import-Package:
javax.servlet;version="[2.6,3)",javax.servlet.http;version="[2.6,3)"
On Thu, Aug 16, 2012 at 11:12 PM, Gareth Collins
wrote:
> I was trying to make your configuration more standard. This would be more like
> the bundle configuration of a karaf. Usually you compile against o
I was trying to make your configuration more standard. This would be more like
the bundle configuration of a karaf. Usually you compile against org.osgi
and org.cpmn but these are not used at runtime.
How are you installing this war? Are you just installing as a bundle or via
the pax war url? I as
Actually you can get away (for now) with felix config admin.
Gareth
On Thu, Aug 16, 2012 at 12:48 PM, Gareth Collins
wrote:
> Add pax-confman and felix-configadmin. Note that felix configadmin
> needs to start
> before pax-confman, at least in the current 0.2.2 version.
>
> Gareth
>
> On Thu, Au
Add pax-confman and felix-configadmin. Note that felix configadmin
needs to start
before pax-confman, at least in the current 0.2.2 version.
Gareth
On Thu, Aug 16, 2012 at 12:40 PM, Dario Luzi wrote:
> thanks for the response...
> i need compendium because without it i`m not able to start pax we
Minor points. You should also not need geronimo-servlet (as these
packages should be exported by pax web).
I can't see why you should need osgi.core or compendium either
(osgi.core packages should be exported by the felix runtime).
Gareth
On Thu, Aug 16, 2012 at 11:32 AM, Dario Luzi wrote:
> Upd
Hi Dario,
the log4j-1.2.17.jar will collide with pax-logging also.
What makes the whole thing very suspicious is the fact that your
application never get's over the Deploying State.
Did you try to debug into this? I somehow fear there is still
something missing though I'm not able to see it right
Ok
after seeing this I'd get rid of those slf4j files and replace them
with the pax-logging-service
this way you just need 2 bundles and are able to use all kinds of
logging frameworks.
as can be seen in [1] you also need the jdt compiler for compiling the
jsp pages.
so you need the mvn:org.eclips
hi there...
yes the bundle is available... installed and started just before the
extender (and checking on Bundle.getState() seems to return active)
this is the order
org.apache.log4j_1.2.13.v200706111418.jar
slf4j-log4j12-1.6.6.jar
slf4j-api-1.6.6.jar
org.osgi.core-4.2.0.jar
pax-logging-api-1.6
Hi Dario,
thanks for the information this is exactly what I needed.
Since I'm on the run (back home) I'll try to give you a more detailed
answer later.
Just one thing, since you only have a JSP file in it (and this
requires a web.xml for sure even with Servlet 3.0)
do you have the pax-web-jsp bund
ok so i`ll try to answere your question at the best of my possibilities
what i`m trying to do is to set up a simple enviroment to see how all the
part work together... after doing this i`ll port all this to a bigger
application which is already based upon felix.
So to learn how pax web works for my
This here is a Pax Exam test I wrote yesterday to reproduce your NPE.
It uses a Hello World WAB which is more or less a copy of yours. Maybe
that can help by running the test, comparing it to your own setup and
spotting the differences.
https://github.com/ops4j/org.ops4j.pax.web/blob/d28af574a8317
Well your application isn't running.
therefore you receive a 404.
What does your jar (supposedly a WAB) contain (I'm not able to access
dropbox right now)
does it contain a servlet or JSPs?
Or does it only contain Html files?
What are you trying to archive here?
Did you test your environment with
ok thanks for your responce...
for what i see my http service should be running since when i navigate to
the page using http://localhost:8080/helloweb
HTTP ERROR: 404
Problem accessing /helloweb. Reason:
Not Found
--
*Powered by Jetty://*
*
*
and this lines get p
You also need to set the metadata-complete to false,
this indicates it needs to load additional annotated Servlets.
regards, Achim
2012/8/15 Harald Wellmann :
> Your webapp is DEPLOYING...
> org.ops4j.pax.web.pax-web-extender-war[org.ops4j.pax.web.extender.war.internal.WebEventDispatcher]
> : org
Your webapp is DEPLOYING...
org.ops4j.pax.web.pax-web-extender-war[org.ops4j.pax.web.extender.war.internal.WebEventDispatcher]
: org/osgi/service/web/DEPLOYING
... but it should be DEPLOYED.
This should happen automatically after a short delay.
You didn't mention how you "navigate to the path".
Hi there guys... i tried the solution with the 2.0.2 but it didn`t seem to
work (same behaviour... no output no publishing)... plus for some reason i
was not getting any log output.
after installing pax logging service and api and adopting your first
workaroud with version 2.1.0 i was able to make
I you want to see some simple examples
take a look at the pax-web samples and especially those in conjunction
with the itests.
Basically every feature of pax-web should be covered by an itest (Unit
test isn't enough anymore)
Those are always a pretty good example :)
regards, Achim
Am 14.08.201
Yeah, right now the extender still needs a web.xml but if you want to
run your Servlet 3.0 features
you need to set the metadata-complete to "false" it then starts scanning
for Annotated servlets.
regards, Achim
Am 14.08.2012 20:10, schrieb Harald Wellmann:
Sorry, too quick...
Correct worka
Sorry, too quick...
Correct workaround:
- Edit web.xml in your WAB and add an attribute to the root element:
- Add pax-web-jsp, or else JSPs will just be rendered as static resources.
You don't need to add pax-web-api and spi or upgrade to 2.1.0.
Best regards,
Harald
_
Hi Dario,
glad you're making some progress.
Now it seems you've hit a bug in Pax Web: Your HelloWeb.jar is being
scanned for classes with web annotations, but the bundle does not
contain any classes at all which causes a NullPointerException.
Workaround:
- Edit web.xml in your WAB and add
Hi there guys...
as you said the problem were the system package with which a screwed up a
bit :)... removing that awefull load of configuration i was putting up at
the beginning made the trick
now i was able to succesfully start a jetty server in osgi felix and
everything seemed to work correctly
Hi Dario,
since you are an OSGi-beginner I'd suggest you start with something
easier then a complete container design :-)
therefore since you probably want to start with your own stuff and not
be bothered by infrastructural issues
I really suggest take a look at Karaf [1]. It's a real easy to use
If you just want to launch an OSGi framework with a given set of
bundles, then what you're doing seems way too complex to me. Leave the
system packages alone unless you know exactly what you're doing. It
seems that this is causing your class cast exception.
Provisioning your framework programmatic
*Sorry for the double post but i managed to clear the pom file a bit and
got away lots of the messy stuff in there... now the strange error at the
end of the previous post is gone but the original one persists .*
*
*
*here is the simplified pom *
http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
htt
*Hi there guys...thanks for your fast answere.*
*Here i come with more informations and sorry to put everything in bold but
it was needed to make the post more readable (easier to distinguish code
and text).*
*First of all i attempted to start the system using compendium 4.2.0 but it
didn`t do the
Hi Dario,
depending on your usecases but I'm quite sure you probably could
need a nice OSGi Container as Apache Karaf.
It does have Pax Web Included and
the upcoming Karaf 3.0 will have the latest Pax Web 2.1 with it.
Latest Stable version of Karaf does contain 1.0.11 of Pax-Web.
So as I said bef
Pax Web 2.0.2 is compiled against org.osgi.core and compendium 4.2.0,
not 4.3.0 - not sure if this causes your exception, but it's worth checking.
Another thing: org.apache.felix.framework-4.0.3.jar *is* the "Felix
container" or OSGi framework, or system bundle. If you've installed a
framework
27 matches
Mail list logo
