Re: [VOTE] Adopt new Apache Karaf "generic" logo
Hello I like it as generic Karaf logo - I have no idea about the font replacements, alignments and other design-related things. Simply +1 ;) regards Grzegorz Grzybek wt., 15 lis 2022 o 09:57 Jean-Baptiste Onofré napisał(a): > Hi guys, > > As discussed on the other thread, here's a vote for the new Karaf logo > proposal. > > As a reminder, this logo is the generic one, used on the main > karaf.apache.org website. Each Karaf subproject (Minho, OSGi, etc) > will have its own "sub-website", with dedicated content and eventually > its own logo. > > Please vote: > +1 to adopt Karaf generic logo > 0 I don't care > -1 for Karaf generic logo and work on a new one > > NB: I would like to move forward pretty fast on the logo just to > promote the new website and announce Karaf Minho. > > Thanks, > Regards > JB >
Re: Unable to create default RequestDispatcher
Hello
You have this message:
Adding servlet
ServletModel{id=ServletModel-239,name='helloboard',urlPatterns=[/],servletClass=class
com..gcs.console.helloboard.HelloboardServlet,contexts=null}
With this, you're overriding the "default" servlet normally mapped to "/"
with your "helloboard" servlet mapped to "/".
I'll check in Servlets specification how this should behave, but for now
this looks like this is the reason. If you don't add this servlet, named
dispatcher should work.
regards
Grzegorz Grzybek
wt., 15 lis 2022 o 15:38 Prashanth Ettaboina
napisał(a):
> Hi Grzegorz,
>
> I'm generating a WAR file of the bundle(which will have the web
> application).
>
> Adding the war file in the feature.xml and installing it in the karaf as a
> kar file.
>
>
> start-level="95">mvn:com.server.console/helloboard/${project.version}/war
>
> karaf@root()> kar: install file :filepath*** snapshot.kar
>
> below are the logs from karaf which are generated while I installed the
> kar file.
>
> 2022-11-15T19:19:11.401+0530 CEF:1 | org.apache.karaf.kar.core | 4.4.1 |
> INFO | ID=168 THR=0.0-SNAPSHOT.kar CAT=KarServiceImpl
> MSG=Added feature repository
> 'mvn:com.server.kars/example-console/51.0.0-SNAPSHOT/xml/features'
> 2022-11-15T19:19:11.403+0530 CEF:1 | org.apache.karaf.features.core |
> 4.4.1 | INFO | ID=19 THR=0.0-SNAPSHOT.kar CAT=FeaturesServiceImpl
> MSG=Adding features: example-console/[51.0.0.SNAPSHOT,51.0.0.SNAPSHOT]
> 2022-11-15T19:19:15.041+0530 CEF:1 | org.apache.karaf.features.core |
> 4.4.1 | INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
> MSG=Changes to perform:
> 2022-11-15T19:19:15.041+0530 CEF:1 | org.apache.karaf.features.core |
> 4.4.1 | INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
> MSG= Region: root
> 2022-11-15T19:19:15.042+0530 CEF:1 | org.apache.karaf.features.core |
> 4.4.1 | INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
> MSG=Bundles to install:
> 2022-11-15T19:19:15.042+0530 CEF:1 | org.apache.karaf.features.core |
> 4.4.1 | INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
> MSG= mvn:com.server.console/helloboard/51.0.0-SNAPSHOT/war
> 2022-11-15T19:19:20.621+0530 CEF:1 | org.apache.karaf.features.core |
> 4.4.1 | INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
> MSG= helloboard/51.0.0.SNAPSHOT
> 2022-11-15T19:19:20.634+0530 CEF:1 |
> org.ops4j.pax.web.pax-web-extender-war | 8.0.6 | INFO | ID=269
> THR=ender-1-thread-1 CAT=BundleWebApplication MSG=Configuring
> Web Application "/helloboard" for bundle helloboard/51.0.0.SNAPSHOT
> 2022-11-15T19:19:20.635+0530 CEF:1 | org.apache.karaf.features.core |
> 4.4.1 | INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
> MSG=Done.
> 2022-11-15T19:19:32.512+0530 CEF:1 | org.ops4j.pax.web.pax-web-runtime |
> 8.0.6 | INFO | ID=272 THR=ender-1-thread-1
> CAT=StoppableHttpServiceFactory MSG=Binding HTTP Service for bundle:
> [helloboard [318]]
> 2022-11-15T19:19:32.514+0530 CEF:1 |
> org.ops4j.pax.web.pax-web-extender-war | 8.0.6 | INFO | ID=269
> THR=ender-1-thread-1 CAT=BundleWebApplication MSG=Allocated
> context for /helloboard:
> OsgiContextModel{WAB,id=OCM-233,name='/helloboard',path='/helloboard',bundle=helloboard,}
> 2022-11-15T19:19:32.520+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty |
> 8.0.6 | INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerController
> MSG=Receiving Batch{"Deployment of Web Application "/helloboard" for
> bundle helloboard/51.0.0.SNAPSHOT", size=24}
> 2022-11-15T19:19:32.520+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty |
> 8.0.6 | INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerWrapper
>MSG=Creating new Jetty context for
> ServletContextModel{id=ServletContextModel-234,contextPath='/helloboard'}
> 2022-11-15T19:19:32.521+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty |
> 8.0.6 | INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerWrapper
>MSG=Adding
> OsgiContextModel{WAB,id=OCM-233,name='/helloboard',path='/helloboard',bundle=helloboard,context=WebContainerContextWrapper{bundle=helloboard
> [318],contextId='/helloboard',delegate=org.ops4j.pax.web.extender.war.internal.WebApplicationHelper@1641e385}}
> to o.o.p.w.s.j.i.PaxWebServletContextHandler@6ae38bdd
> {/helloboard,null,STOPPED} o.o.p.w.s.j.i.PaxWebServletContextHandler@6ae38bdd
> %7b/dashboard,null,STOPPED%7d>
> 2022-11-15T19:19:32.522+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty |
> 8.0.6 | INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerWrapper
>MSG=Changing default OSGi context model for
> o.o.p.w.s.j.i.PaxWebServletContextHandler@6ae38bdd
> {/helloboard,null,STOPPED} o.o.p.w.s.j.i.PaxWebServletContextHandler@6ae38bdd
> %7b/dashboard,null,STOPPED%7d>
> 2022-11-15T19:19:32.522+0530 CEF:1 | org.ops4j.pax.web.pax-web-spi | 8.0.6
> | INFO | ID=273 THR=ploy /helloboard) CAT=OsgiServletContext
> MSG=Registering
>
RE: Unable to create default RequestDispatcher
Hi Grzegorz,
I'm generating a WAR file of the bundle(which will have the web application).
Adding the war file in the feature.xml and installing it in the karaf as a kar
file.
mvn:com.server.console/helloboard/${project.version}/war
karaf@root()> kar: install file :filepath*** snapshot.kar
below are the logs from karaf which are generated while I installed the kar
file.
2022-11-15T19:19:11.401+0530 CEF:1 | org.apache.karaf.kar.core | 4.4.1 | INFO
| ID=168 THR=0.0-SNAPSHOT.kar CAT=KarServiceImpl MSG=Added
feature repository
'mvn:com.server.kars/example-console/51.0.0-SNAPSHOT/xml/features'
2022-11-15T19:19:11.403+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=0.0-SNAPSHOT.kar CAT=FeaturesServiceImpl
MSG=Adding features: example-console/[51.0.0.SNAPSHOT,51.0.0.SNAPSHOT]
2022-11-15T19:19:15.041+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
MSG=Changes to perform:
2022-11-15T19:19:15.041+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl MSG=
Region: root
2022-11-15T19:19:15.042+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl MSG=
Bundles to install:
2022-11-15T19:19:15.042+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl MSG=
mvn:com.server.console/helloboard/51.0.0-SNAPSHOT/war
2022-11-15T19:19:20.621+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl MSG=
helloboard/51.0.0.SNAPSHOT
2022-11-15T19:19:20.634+0530 CEF:1 | org.ops4j.pax.web.pax-web-extender-war |
8.0.6 | INFO | ID=269 THR=ender-1-thread-1 CAT=BundleWebApplication
MSG=Configuring Web Application "/helloboard" for bundle
helloboard/51.0.0.SNAPSHOT
2022-11-15T19:19:20.635+0530 CEF:1 | org.apache.karaf.features.core | 4.4.1 |
INFO | ID=19 THR=tures-3-thread-1 CAT=FeaturesServiceImpl
MSG=Done.
2022-11-15T19:19:32.512+0530 CEF:1 | org.ops4j.pax.web.pax-web-runtime | 8.0.6
| INFO | ID=272 THR=ender-1-thread-1 CAT=StoppableHttpServiceFactory
MSG=Binding HTTP Service for bundle: [helloboard [318]]
2022-11-15T19:19:32.514+0530 CEF:1 | org.ops4j.pax.web.pax-web-extender-war |
8.0.6 | INFO | ID=269 THR=ender-1-thread-1 CAT=BundleWebApplication
MSG=Allocated context for /helloboard:
OsgiContextModel{WAB,id=OCM-233,name='/helloboard',path='/helloboard',bundle=helloboard,}
2022-11-15T19:19:32.520+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty | 8.0.6 |
INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerController
MSG=Receiving Batch{"Deployment of Web Application "/helloboard" for bundle
helloboard/51.0.0.SNAPSHOT", size=24}
2022-11-15T19:19:32.520+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty | 8.0.6 |
INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerWrapper
MSG=Creating new Jetty context for
ServletContextModel{id=ServletContextModel-234,contextPath='/helloboard'}
2022-11-15T19:19:32.521+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty | 8.0.6 |
INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerWrapper
MSG=Adding
OsgiContextModel{WAB,id=OCM-233,name='/helloboard',path='/helloboard',bundle=helloboard,context=WebContainerContextWrapper{bundle=helloboard
[318],contextId='/helloboard',delegate=org.ops4j.pax.web.extender.war.internal.WebApplicationHelper@1641e385}}
to
o.o.p.w.s.j.i.PaxWebServletContextHandler@6ae38bdd{/helloboard,null,STOPPED}
2022-11-15T19:19:32.522+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty | 8.0.6 |
INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerWrapper
MSG=Changing default OSGi context model for
o.o.p.w.s.j.i.PaxWebServletContextHandler@6ae38bdd{/helloboard,null,STOPPED}
2022-11-15T19:19:32.522+0530 CEF:1 | org.ops4j.pax.web.pax-web-spi | 8.0.6 |
INFO | ID=273 THR=ploy /helloboard) CAT=OsgiServletContext
MSG=Registering
OsgiServletContext{model=OsgiContextModel{WAB,id=OCM-233,name='/helloboard',path='/helloboard',bundle=helloboard,context=WebContainerContextWrapper{bundle=helloboard
[318],contextId='/helloboard',delegate=org.ops4j.pax.web.extender.war.internal.WebApplicationHelper@1641e385}}}
as OSGi service for "/helloboard" context path
2022-11-15T19:19:32.523+0530 CEF:1 | org.ops4j.pax.web.pax-web-jetty | 8.0.6 |
INFO | ID=270 THR=ploy /helloboard) CAT=JettyServerWrapper
MSG=Configuring metadata of
Re: Unable to create default RequestDispatcher
Hello Prashanth
I've added a link to Github issue to your
https://stackoverflow.com/questions/74432966/unable-to-create-default-requestdispatcher
I checked simplest web.xml with a servlet mapped to `/*` (so I can grab all
the requests) and getNamedDispatcher("default") simply worked.
Please share your entire WAB if possible.
regards
Grzegorz Grzybek
wt., 15 lis 2022 o 13:56 Grzegorz Grzybek napisał(a):
> Ah - so you're installing a WAR/WAB? Can you give some details under
> https://github.com/ops4j/org.ops4j.pax.web/issues/1794 ?
>
> Or if you don't use Github, please share:
> - information about the WAR you're installing
> - some logs from Karaf when you install the WAR
>
> regards
> Grzegorz Grzybek
>
> wt., 15 lis 2022 o 12:04 Prashanth Ettaboina
> napisał(a):
>
>> Hi Grzegorz,
>>
>> I'm not registering the ExampleServlet anywhere, I'm configuring them in
>> web.xml.
>> In the web.xml we are giving the servlet and servlet mapping with
>> url-pattern and class path.
>>
>> Thanks,
>> Prashanth Ettaboina.
>>
>> From: Prashanth Ettaboina
>> Sent: 14 November 2022 19:11
>> To: iss...@karaf.apache.org; dev@karaf.apache.org; u...@karaf.apache.org
>> Subject: Unable to create default RequestDispatcher
>>
>> Hi Team,
>>
>> I have updated my KARAF version from 4.2.15 to 4.4.1 and Java from 8 to
>> 11 in my application.
>> Gone through the official Release notes and updated some dependencies as
>> well.
>>
>> Upgraded OSGI-Core from 6.0.0 to 8.0.0.
>> Upgraded osgi.compendium 5.0.0 to osgi.cmpn 7.0.0
>> Upgraded Jetty from 9.4.43.v20210629 to 9.4.46.v20220331.
>> Upgraded pax-web-spi from 4.3.4 to 7.2.11.
>> I'm using javax.servlet-api 3.1.0 version in my application.
>>
>> I'm unable to create default RequestDispatcher.
>> Please check the below code lines.
>>
>> public class ExampleServlet extends HttpServlet {
>> protected void doGet(HttpServletRequest request,
>> HttpServletResponse response) throws ServletException, IOException {
>> RequestDispatcher requestDispatcher =
>> getServletContext().getNamedDispatcher("default"); // get
>> getServletContext() is calling the method in GenericServlet.
>> requestDispatcher.include(request, response);
>> }
>> }
>>
>> the above code used to work fine before the version upgrades but now I'm
>> getting the requestDispatcher as null.
>>
>> Can anyone please look at it, let me know if I'm missing something.
>>
>> Thanks,
>> Prashanth Ettaboina
>>
>>
>>
>>
Re: Unable to create default RequestDispatcher
Ah - so you're installing a WAR/WAB? Can you give some details under
https://github.com/ops4j/org.ops4j.pax.web/issues/1794 ?
Or if you don't use Github, please share:
- information about the WAR you're installing
- some logs from Karaf when you install the WAR
regards
Grzegorz Grzybek
wt., 15 lis 2022 o 12:04 Prashanth Ettaboina
napisał(a):
> Hi Grzegorz,
>
> I'm not registering the ExampleServlet anywhere, I'm configuring them in
> web.xml.
> In the web.xml we are giving the servlet and servlet mapping with
> url-pattern and class path.
>
> Thanks,
> Prashanth Ettaboina.
>
> From: Prashanth Ettaboina
> Sent: 14 November 2022 19:11
> To: iss...@karaf.apache.org; dev@karaf.apache.org; u...@karaf.apache.org
> Subject: Unable to create default RequestDispatcher
>
> Hi Team,
>
> I have updated my KARAF version from 4.2.15 to 4.4.1 and Java from 8 to 11
> in my application.
> Gone through the official Release notes and updated some dependencies as
> well.
>
> Upgraded OSGI-Core from 6.0.0 to 8.0.0.
> Upgraded osgi.compendium 5.0.0 to osgi.cmpn 7.0.0
> Upgraded Jetty from 9.4.43.v20210629 to 9.4.46.v20220331.
> Upgraded pax-web-spi from 4.3.4 to 7.2.11.
> I'm using javax.servlet-api 3.1.0 version in my application.
>
> I'm unable to create default RequestDispatcher.
> Please check the below code lines.
>
> public class ExampleServlet extends HttpServlet {
> protected void doGet(HttpServletRequest request, HttpServletResponse
> response) throws ServletException, IOException {
> RequestDispatcher requestDispatcher =
> getServletContext().getNamedDispatcher("default"); // get
> getServletContext() is calling the method in GenericServlet.
> requestDispatcher.include(request, response);
> }
> }
>
> the above code used to work fine before the version upgrades but now I'm
> getting the requestDispatcher as null.
>
> Can anyone please look at it, let me know if I'm missing something.
>
> Thanks,
> Prashanth Ettaboina
>
>
>
>
RE: Unable to create default RequestDispatcher
Hi Grzegorz,
I'm not registering the ExampleServlet anywhere, I'm configuring them in
web.xml.
In the web.xml we are giving the servlet and servlet mapping with url-pattern
and class path.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 14 November 2022 19:11
To: iss...@karaf.apache.org; dev@karaf.apache.org; u...@karaf.apache.org
Subject: Unable to create default RequestDispatcher
Hi Team,
I have updated my KARAF version from 4.2.15 to 4.4.1 and Java from 8 to 11 in
my application.
Gone through the official Release notes and updated some dependencies as well.
Upgraded OSGI-Core from 6.0.0 to 8.0.0.
Upgraded osgi.compendium 5.0.0 to osgi.cmpn 7.0.0
Upgraded Jetty from 9.4.43.v20210629 to 9.4.46.v20220331.
Upgraded pax-web-spi from 4.3.4 to 7.2.11.
I'm using javax.servlet-api 3.1.0 version in my application.
I'm unable to create default RequestDispatcher.
Please check the below code lines.
public class ExampleServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
RequestDispatcher requestDispatcher =
getServletContext().getNamedDispatcher("default"); // get getServletContext()
is calling the method in GenericServlet.
requestDispatcher.include(request, response);
}
}
the above code used to work fine before the version upgrades but now I'm
getting the requestDispatcher as null.
Can anyone please look at it, let me know if I'm missing something.
Thanks,
Prashanth Ettaboina
[VOTE] Adopt new Apache Karaf "generic" logo
Hi guys, As discussed on the other thread, here's a vote for the new Karaf logo proposal. As a reminder, this logo is the generic one, used on the main karaf.apache.org website. Each Karaf subproject (Minho, OSGi, etc) will have its own "sub-website", with dedicated content and eventually its own logo. Please vote: +1 to adopt Karaf generic logo 0 I don't care -1 for Karaf generic logo and work on a new one NB: I would like to move forward pretty fast on the logo just to promote the new website and announce Karaf Minho. Thanks, Regards JB
Re: [DISCUSS] Adopt new Karaf logo
As we don't have consensus on "cloud" logo, I cancel this vote and start a new one with another proposal. Thanks, Regards JB On Mon, Nov 14, 2022 at 6:43 PM Matt Pavlovich wrote: > > -1 (non-binding) > > My $0.02 — > > 1. The cloud logo is not friendly to be turned into a font > 2. I prefer the alternative hexagon logo is simpler (even if similar to > others) and better suited for the things logos are used for — stickers, font, > ascii art, etc. > > Thanks, > Matt Pavlovich > > On Nov 13, 2022, at 1:47 AM, Jean-Baptiste Onofré wrote: > > Hi guys > > I did a review on twitter and linkedin feedback about Karaf logo (the « cloud > » one). > > To summarize, we only have +1 and two « comments » like « cloud is not > related to Karaf ». > > So, I wonder to make a call and formal vote: > > +1 to adopt Karaf cloud logo > -1 for Karaf cloud logo and work on a new one > > The reason I’m asking is because I’m working on website proposal. So I would > like to integrate the logo. > > Regards > JB > > Le mar. 1 nov. 2022 à 14:11, Jean-Baptiste Onofré a écrit > : >> >> Hi guys, >> >> as discussed on a previous thread, I'm working on a new website >> proposal with the following objectives: >> >> 1. Use docusaurus instead of jekyll to build. The good thing is that >> it supports md syntax, blog, etc. >> 2. Give the same space/visibility to the subprojects (Karaf Minho, >> Karaf OSGi, Karaf Decanter, Karaf Cellar, Karaf Cave, Karaf >> Winegrower) >> 3. Add blog feature to announce and provide details about Karaf projects >> >> Related to that, I created a new "generic" logo for Karaf (each >> project can have its own logo). >> >> You can see the logo proposal attached. >> >> Basically the idea is: >> - boxes populating the cloud represent Karaf projects >> - we can assembly Karaf projects to create a cloud solution >> >> Thoughts ? >> >> If we agree with this logo, I would like to prepare some goodies using >> it (probably on https://www.redbubble.com/en/). >> >> Regards >> JB > >
