[GitHub] [karaf-minho] jbonofre opened a new issue, #33: Add method in `Minho` to retrieve the current instance
jbonofre opened a new issue, #33: URL: https://github.com/apache/karaf-minho/issues/33 For convenience, in order to get especially the `ServiceRegistry`, `Minho` should provide a way to retrieve the current instance. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@karaf.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [karaf-minho] jbonofre opened a new issue, #32: Improve dependencies resolver
jbonofre opened a new issue, #32: URL: https://github.com/apache/karaf-minho/issues/32 Maven Parser.getDependencies() is not accurate: - it doesn't retrieve all dependencies - it fails to resolve some transitive dependencies It should mimic the maven-dependency-plugin resolve mojo and the result should be the same as dependency:resolve goal. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@karaf.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [VOTE] Adopt new Apache Karaf "generic" logo
+1 cool! > On Nov 15, 2022, at 2:56 AM, Jean-Baptiste Onofré wrote: > > 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
Hi
Part of the fix is this example:
https://github.com/ops4j/org.ops4j.pax.web/tree/pax-web-8.0.x/samples/samples-war/war-dispatcher
with this web.xml:
http://xmlns.jcp.org/xml/ns/javaee; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-app_4_0.xsd;
version="4.0">
dispatch-servlet
org.ops4j.pax.web.samples.war.osgi.JustDispatchServlet
dispatch-servlet
/
and this org.ops4j.pax.web.samples.war.osgi.JustDispatchServlet:
public class JustDispatchServlet extends HttpServlet {
@Override
protected void service(HttpServletRequest req, HttpServletResponse resp)
throws ServletException, IOException {
// https://github.com/ops4j/org.ops4j.pax.web/issues/1794:
// we want to delegate to "default" servlet hoping to use it's
functionality
getServletContext().getNamedDispatcher("default").include(req, resp);
}
}
the test checks the behavior on three runtimes (Jetty, Tomcat, Undertow).
regards
Grzegorz Grzybek
śr., 16 lis 2022 o 14:57 Prashanth Ettaboina
napisał(a):
> Hi Grzegorz,
>
> I hope the latest version(8.0.13) should solve the issue.
> Thank you for taking up the issue and being supportive, your responses are
> deeply appreciated.
>
> Regards,
> Prashanth
>
> From: Prashanth Ettaboina
> Sent: 16 November 2022 15:33
> To: 'iss...@karaf.apache.org' ; '
> dev@karaf.apache.org' ; 'u...@karaf.apache.org' <
> u...@karaf.apache.org>
> Subject: RE: Unable to create default RequestDispatcher
>
> Hi Grzegorz,
>
> Thank you for your response.
> I have gone through your explanation; I have seen that "/" is overriding
> the default servlet. Thank you for letting me know.
> But we had that web.xml configuration from last several years below is the
> web.xml which was being used from older karaf versions (before 4.4.1).
>
>
> helloboard
> com.console.helloboard.HelloboardServlet
>
>
> helloboard
> /
>
>
> Previously HelloboardServlet used to take in all the requests and process
> them, below is the code block which is used to be executed.
>
> public class HelloboardServlet extends HttpServlet {
>
>protected void doGet(HttpServletRequest request,
> HttpServletResponse response) throws ServletException, IOException {
> if (request.getServletPath().equals("/")) {
> response.sendRedirect("views/welcome.jsp");
> } else if (request.getServletPath().startsWith("/resources/")){
> if(request.getServletPath().endsWith(".css")) {
> response.setContentType("text/css");
> } else if (request.getServletPath().endsWith(".js")) {
>response.setContentType("text/javascript");
> }
> RequestDispatcher rd =
> getServletContext().getNamedDispatcher("default");
> rd.include(request, response);
> }
>}
> }
>
> I want to know why it was able to create a default RequestDispatcher back
> then and why not now? are there any changes in the implementation as part
> of the upgrades, if yes can I get some information of what has been
> modified.
>
> As per your directions I have changed the web.xml servlet mapping from /
> to /*, now I'm able to create the default servlet but the above code block
> will not be working because I have changed the url-pattern from / to /* all
> the request objects are containing servletPath as "" (empty string). Which
> will break the existing flow.
>
> I'm sorry that I cannot share the WAB and can give any further inputs
> regarding this issue.
>
> Thanks,
> Prashanth Ettaboina.
>
>
> From: Prashanth Ettaboina
> Sent: 16 November 2022 14:02
> To: 'iss...@karaf.apache.org' iss...@karaf.apache.org>>; 'dev@karaf.apache.org' >; 'u...@karaf.apache.org' <
> u...@karaf.apache.org>
> Subject: RE: Unable to create default RequestDispatcher
>
> Hi Grzegorz,
>
> Thank you for your response.
> I have gone through your explanation; I have seen that "/" is overriding
> the default servlet. Thank you for letting me know.
> But we had that web.xml configuration from last several years below is the
> web.xml which was being used from older karaf versions (before 4.4.1).
>
>
> helloboard
> com.console.helloboard.HelloboardServlet
>
>
> helloboard
> /
>
>
> Previously HelloboardServlet used to take in all the requests and process
> them, below is the code block which is used to be executed.
>
> public class HelloboardServlet extends HttpServlet {
>
>protected void doGet(HttpServletRequest request,
> HttpServletResponse response) throws ServletException, IOException {
> if (request.getServletPath().equals("/")) {
> response.sendRedirect("views/welcome.jsp");
> } else if
RE: Unable to create default RequestDispatcher
Hi Grzegorz,
I hope the latest version(8.0.13) should solve the issue.
Thank you for taking up the issue and being supportive, your responses are
deeply appreciated.
Regards,
Prashanth
From: Prashanth Ettaboina
Sent: 16 November 2022 15:33
To: 'iss...@karaf.apache.org' ; 'dev@karaf.apache.org'
; 'u...@karaf.apache.org'
Subject: RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm sorry that I cannot share the WAB and can give any further inputs regarding
this issue.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 16 November 2022 14:02
To: 'iss...@karaf.apache.org'
mailto:iss...@karaf.apache.org>>;
'dev@karaf.apache.org' mailto:dev@karaf.apache.org>>;
'u...@karaf.apache.org' mailto:u...@karaf.apache.org>>
Subject: RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm sorry that I cannot share the WAB and can give any further inputs regarding
this issue.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 15 November 2022 20:03
To: 'iss...@karaf.apache.org'
mailto:iss...@karaf.apache.org>>;
'dev@karaf.apache.org' mailto:dev@karaf.apache.org>>;
Re: Unable to create default RequestDispatcher
Hello
I've fixed the problem here:
https://github.com/ops4j/org.ops4j.pax.web/commit/19696d4dcabe8b5663d33f894a8d40fc2b742c88
The problem was that during WAR scanning, if there was any servlet mapped
to "/", "default" servlet was removed entirely - now it's still registered,
but with empty mapping - so you can't invoke it, but you can get a named
dispatcher for it.
I'm going to release Pax Web 8.0.13 today.
Thanks Prashanth for the report!
regards
Grzegorz Grzybek
śr., 16 lis 2022 o 12:21 Grzegorz Grzybek napisał(a):
> Hello Prashanth
>
> I've added some findings to
> https://github.com/ops4j/org.ops4j.pax.web/issues/1794 and I see there's
> a problem in Tomcat and Jetty runtimes for Pax Web.
> I've just checked it in pure standalone Tomcat and indeed - the "default"
> dispatcher should NEVER be removed - I'm working on a fix.
>
> regards
> Grzegorz Grzybek
>
> śr., 16 lis 2022 o 12:02 Prashanth Ettaboina
> napisał(a):
>
>> Hi Grzegorz,
>>
>> Thank you for your response.
>> I have gone through your explanation; I have seen that "/" is overriding
>> the default servlet. Thank you for letting me know.
>> But we had that web.xml configuration from last several years below is
>> the web.xml which was being used from older karaf versions (before 4.4.1).
>>
>>
>> helloboard
>>
>> com.console.helloboard.HelloboardServlet
>>
>>
>> helloboard
>> /
>>
>>
>> Previously HelloboardServlet used to take in all the requests and process
>> them, below is the code block which is used to be executed.
>>
>> public class HelloboardServlet extends HttpServlet {
>>
>>protected void doGet(HttpServletRequest request,
>> HttpServletResponse response) throws ServletException, IOException {
>> if (request.getServletPath().equals("/")) {
>> response.sendRedirect("views/welcome.jsp");
>> } else if
>> (request.getServletPath().startsWith("/resources/")){
>> if(request.getServletPath().endsWith(".css")) {
>> response.setContentType("text/css");
>> } else if (request.getServletPath().endsWith(".js")) {
>>response.setContentType("text/javascript");
>> }
>> RequestDispatcher rd =
>> getServletContext().getNamedDispatcher("default");
>> rd.include(request, response);
>> }
>>}
>> }
>>
>> I want to know why it was able to create a default RequestDispatcher back
>> then and why not now? are there any changes in the implementation as part
>> of the upgrades, if yes can I get some information of what has been
>> modified.
>>
>> As per your directions I have changed the web.xml servlet mapping from /
>> to /*, now I'm able to create the default servlet but the above code block
>> will not be working because I have changed the url-pattern from / to /* all
>> the request objects are containing servletPath as "" (empty string). Which
>> will break the existing flow.
>>
>> I'm sorry that I cannot share the WAB and can give any further inputs
>> regarding this issue.
>>
>> Thanks,
>> Prashanth Ettaboina.
>>
>>
>> From: Prashanth Ettaboina
>> Sent: 16 November 2022 14:02
>> To: 'iss...@karaf.apache.org' ; '
>> dev@karaf.apache.org' ; 'u...@karaf.apache.org' <
>> u...@karaf.apache.org>
>> Subject: RE: Unable to create default RequestDispatcher
>>
>> Hi Grzegorz,
>>
>> Thank you for your response.
>> I have gone through your explanation; I have seen that "/" is overriding
>> the default servlet. Thank you for letting me know.
>> But we had that web.xml configuration from last several years below is
>> the web.xml which was being used from older karaf versions (before 4.4.1).
>>
>>
>> helloboard
>>
>> com.console.helloboard.HelloboardServlet
>>
>>
>> helloboard
>> /
>>
>>
>> Previously HelloboardServlet used to take in all the requests and process
>> them, below is the code block which is used to be executed.
>>
>> public class HelloboardServlet extends HttpServlet {
>>
>>protected void doGet(HttpServletRequest request,
>> HttpServletResponse response) throws ServletException, IOException {
>> if (request.getServletPath().equals("/")) {
>> response.sendRedirect("views/welcome.jsp");
>> } else if
>> (request.getServletPath().startsWith("/resources/")){
>> if(request.getServletPath().endsWith(".css")) {
>> response.setContentType("text/css");
>> } else if (request.getServletPath().endsWith(".js")) {
>>response.setContentType("text/javascript");
>> }
>> RequestDispatcher rd =
>> getServletContext().getNamedDispatcher("default");
>> rd.include(request, response);
>> }
>>}
>> }
>>
>> I want to know why it was able to create a default RequestDispatcher back
>> then and why not now? are
Re: Unable to create default RequestDispatcher
Hello Prashanth
I've added some findings to
https://github.com/ops4j/org.ops4j.pax.web/issues/1794 and I see there's a
problem in Tomcat and Jetty runtimes for Pax Web.
I've just checked it in pure standalone Tomcat and indeed - the "default"
dispatcher should NEVER be removed - I'm working on a fix.
regards
Grzegorz Grzybek
śr., 16 lis 2022 o 12:02 Prashanth Ettaboina
napisał(a):
> Hi Grzegorz,
>
> Thank you for your response.
> I have gone through your explanation; I have seen that "/" is overriding
> the default servlet. Thank you for letting me know.
> But we had that web.xml configuration from last several years below is the
> web.xml which was being used from older karaf versions (before 4.4.1).
>
>
> helloboard
> com.console.helloboard.HelloboardServlet
>
>
> helloboard
> /
>
>
> Previously HelloboardServlet used to take in all the requests and process
> them, below is the code block which is used to be executed.
>
> public class HelloboardServlet extends HttpServlet {
>
>protected void doGet(HttpServletRequest request,
> HttpServletResponse response) throws ServletException, IOException {
> if (request.getServletPath().equals("/")) {
> response.sendRedirect("views/welcome.jsp");
> } else if (request.getServletPath().startsWith("/resources/")){
> if(request.getServletPath().endsWith(".css")) {
> response.setContentType("text/css");
> } else if (request.getServletPath().endsWith(".js")) {
>response.setContentType("text/javascript");
> }
> RequestDispatcher rd =
> getServletContext().getNamedDispatcher("default");
> rd.include(request, response);
> }
>}
> }
>
> I want to know why it was able to create a default RequestDispatcher back
> then and why not now? are there any changes in the implementation as part
> of the upgrades, if yes can I get some information of what has been
> modified.
>
> As per your directions I have changed the web.xml servlet mapping from /
> to /*, now I'm able to create the default servlet but the above code block
> will not be working because I have changed the url-pattern from / to /* all
> the request objects are containing servletPath as "" (empty string). Which
> will break the existing flow.
>
> I'm sorry that I cannot share the WAB and can give any further inputs
> regarding this issue.
>
> Thanks,
> Prashanth Ettaboina.
>
>
> From: Prashanth Ettaboina
> Sent: 16 November 2022 14:02
> To: 'iss...@karaf.apache.org' ; '
> dev@karaf.apache.org' ; 'u...@karaf.apache.org' <
> u...@karaf.apache.org>
> Subject: RE: Unable to create default RequestDispatcher
>
> Hi Grzegorz,
>
> Thank you for your response.
> I have gone through your explanation; I have seen that "/" is overriding
> the default servlet. Thank you for letting me know.
> But we had that web.xml configuration from last several years below is the
> web.xml which was being used from older karaf versions (before 4.4.1).
>
>
> helloboard
> com.console.helloboard.HelloboardServlet
>
>
> helloboard
> /
>
>
> Previously HelloboardServlet used to take in all the requests and process
> them, below is the code block which is used to be executed.
>
> public class HelloboardServlet extends HttpServlet {
>
>protected void doGet(HttpServletRequest request,
> HttpServletResponse response) throws ServletException, IOException {
> if (request.getServletPath().equals("/")) {
> response.sendRedirect("views/welcome.jsp");
> } else if (request.getServletPath().startsWith("/resources/")){
> if(request.getServletPath().endsWith(".css")) {
> response.setContentType("text/css");
> } else if (request.getServletPath().endsWith(".js")) {
>response.setContentType("text/javascript");
> }
> RequestDispatcher rd =
> getServletContext().getNamedDispatcher("default");
> rd.include(request, response);
> }
>}
> }
>
> I want to know why it was able to create a default RequestDispatcher back
> then and why not now? are there any changes in the implementation as part
> of the upgrades, if yes can I get some information of what has been
> modified.
>
> As per your directions I have changed the web.xml servlet mapping from /
> to /*, now I'm able to create the default servlet but the above code block
> will not be working because I have changed the url-pattern from / to /* all
> the request objects are containing servletPath as "" (empty string). Which
> will break the existing flow.
>
> I'm sorry that I cannot share the WAB and can give any further inputs
> regarding this issue.
>
> Thanks,
> Prashanth Ettaboina.
> From: Prashanth Ettaboina
> Sent: 15 November 2022 20:03
>
RE: [VOTE] Adopt new Apache Karaf "generic" logo
+1 Like the colours, the logo design, and the font. Do the small squares represent a Karaf instance or the modules on a runtime? Or could be both? If modules, the black box surrounding the small squares is the runtime? Met vriendelijke groet / Mit freundlichen Grüßen / Kind regards, Maurice Betzel Principal Software Engineer Gaston Schul Group Department ICT Kazernestraat 10 5928 NL Venlo Phone: +31 77 32 460 26 Mobile Phone: +31 6 10 37 58 03 Website: www.gaston-schul.com -Original Message- From: Jean-Baptiste Onofré Sent: 15 November 2022 09:57 To: dev ; user Subject: [VOTE] Adopt new Apache Karaf "generic" logo CAUTION: This email originated from outside of Gaston Schul. Do not click links or open attachments unless you recognize the sender and know the content is safe. 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 Al onze verrichtingen geschieden op basis van de Algemene voorwaarden der Expediteurs van België, gepubliceerd in de bijlage tot het Belgisch Staatsblad dd. 24 juni 2005 onder nr. 0090237. De tekst van deze voorwaarden wordt op uw verzoek gratis toegezonden. All our transactions are subject to the General Conditions of the Belgian Forwarders Association which have been published under nr. 0090237 in the "Bijlage tot het Belgisch Staatsblad" dated June 24th, 2005, and is available free of charge upon request. Toutes nos opérations se font sur base des Conditions Générales des Expéditeurs de Belgique. Le texte en a été publié dans l' Annexe au Moniteur Belge du 24 juin 2005 sous le n° 0090237. Ce texte sera vous envoyé gratuitment sur demande. Email confidentiality notice: This email and any files transmitted with it are confidential and intended only for the use of the recipient. If you have received this email in error please notify its sender.
RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm sorry that I cannot share the WAB and can give any further inputs regarding
this issue.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 15 November 2022 20:03
To: 'iss...@karaf.apache.org' ; 'dev@karaf.apache.org'
; 'u...@karaf.apache.org'
Subject: 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
RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm sorry that I cannot share the WAB and can give any further inputs regarding
this issue.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 16 November 2022 14:02
To: 'iss...@karaf.apache.org' ; 'dev@karaf.apache.org'
; 'u...@karaf.apache.org'
Subject: RE: Unable to create default RequestDispatcher
Hi Grzegorz,
Thank you for your response.
I have gone through your explanation; I have seen that "/" is overriding the
default servlet. Thank you for letting me know.
But we had that web.xml configuration from last several years below is the
web.xml which was being used from older karaf versions (before 4.4.1).
helloboard
com.console.helloboard.HelloboardServlet
helloboard
/
Previously HelloboardServlet used to take in all the requests and process them,
below is the code block which is used to be executed.
public class HelloboardServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
if (request.getServletPath().equals("/")) {
response.sendRedirect("views/welcome.jsp");
} else if (request.getServletPath().startsWith("/resources/")){
if(request.getServletPath().endsWith(".css")) {
response.setContentType("text/css");
} else if (request.getServletPath().endsWith(".js")) {
response.setContentType("text/javascript");
}
RequestDispatcher rd =
getServletContext().getNamedDispatcher("default");
rd.include(request, response);
}
}
}
I want to know why it was able to create a default RequestDispatcher back then
and why not now? are there any changes in the implementation as part of the
upgrades, if yes can I get some information of what has been modified.
As per your directions I have changed the web.xml servlet mapping from / to /*,
now I'm able to create the default servlet but the above code block will not be
working because I have changed the url-pattern from / to /* all the request
objects are containing servletPath as "" (empty string). Which will break the
existing flow.
I'm sorry that I cannot share the WAB and can give any further inputs regarding
this issue.
Thanks,
Prashanth Ettaboina.
From: Prashanth Ettaboina
Sent: 15 November 2022 20:03
To: 'iss...@karaf.apache.org'
mailto:iss...@karaf.apache.org>>;
'dev@karaf.apache.org' mailto:dev@karaf.apache.org>>;
'u...@karaf.apache.org' mailto:u...@karaf.apache.org>>
Subject: 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
Re: [VOTE] Adopt new Apache Karaf "generic" logo
+1 regards, Francois On 15/11/2022 09:56, Jean-Baptiste Onofré wrote: 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: [VOTE] Adopt new Apache Karaf "generic" logo
Hi, The logo was generated but we can update the font to keep the actual one. Regards, Francois On 16/11/2022 08:23, Grzegorz Grzybek wrote: 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 -- -- François
