[JBoss JIRA] (WFLY-13067) Cannot load properties from servlet classpath
by Bartosz Baranowski (Jira)
[ https://issues.redhat.com/browse/WFLY-13067?page=com.atlassian.jira.plugi... ]
Bartosz Baranowski commented on WFLY-13067:
-------------------------------------------
[https://docs.oracle.com/cd/E12839_01/web.1111/e13712/configurewebapp.htm#...]
?? However, the contents of the {{WEB-INF}} directory are visible to servlet code using the {{getResource}} and {{getResourceAsStream()}} method calls on the {{ServletContext}} or includes/forwards using the RequestDispatcher. ??
Servlet spec 4.0, section 4.6
??The ServletContext interface provides direct access only to the hierarchy of static content documents that are part of the Web application, including HTML, GIF, and JPEG files, via the following methods of the ServletContext interface: 4-42 Java Servlet Specification • July 2017??
?? ■ getResource ??
??■ getResourceAsStream ??
??The getResource and getResourceAsStream methods take a String with a leading “/” as an argument that gives the path of the resource relative to the root of the context or relative to the META-INF/resources directory of a JAR file inside the web application’s WEB-INF/lib directory. If there is a WEB-INF entry inside the META-INF/resources entry of a JAR file in WEB-INF/lib, then it and all child entries are available only as static resources. No classes or jars will be placed on the context classpath from such a WEB-INF entry, and no Servlet specific descriptors will be processed. These methods will first search the root of the web application context for the requested resource before looking at any of the JAR files in the WEB-INF/lib directory. The order in which the JAR files in the WEB-INF/lib directory are scanned is undefined. This hierarchy of documents may exist in the server’s file system, in a Web application archive file, on a remote server, or at some other location.??
> Cannot load properties from servlet classpath
> ---------------------------------------------
>
> Key: WFLY-13067
> URL: https://issues.redhat.com/browse/WFLY-13067
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Reporter: Thomas Diesler
> Assignee: Bartosz Baranowski
> Priority: Major
>
> With the latest master I can no longer load resources from
> {code}
> ClassLoader loader = SimpleServlet.class.getClassLoader();
> URL propsA = loader.getResource("/psetA.properties");
> {code}
> nor from
> {code}
> ClassLoader loader = SimpleServlet.class.getClassLoader();
> URL propsA = loader.getResource("/WEB-INF/psetA.properties");
> {code}
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2944
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (DROOLS-5662) Creation of Drools wrapper modules
by Mario Fusco (Jira)
Mario Fusco created DROOLS-5662:
-----------------------------------
Summary: Creation of Drools wrapper modules
Key: DROOLS-5662
URL: https://issues.redhat.com/browse/DROOLS-5662
Project: Drools
Issue Type: Task
Reporter: Mario Fusco
Assignee: Mario Fusco
Drools users have among their dependencies module like drools-core and drools-compiler that in reality are no more than "implementation details". This causes backward incompatibilities when we decide to split engine in finer grained submodules and descope optional features.
For this reason we decided to introduce 2 wrapper modules (for the 2 different main usage scenarios that I see at the moment), made by just a pom aggregating a list of dependencies. The suggested names for these modules are at the moment
* *drools-engine* aggregating drools-core, drools-compiler and drools-model-compiler
* *drools-engine-classic* aggregating drools-core, drools-compiler, drools-mvel (and eventually drools-serialization-protobuf)
Add comments to this ticket to suggest different names.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (SWSQE-1168) Document alternatives for PSI OpenStack
by Hayk Hovsepyan (Jira)
[ https://issues.redhat.com/browse/SWSQE-1168?page=com.atlassian.jira.plugi... ]
Hayk Hovsepyan updated SWSQE-1168:
----------------------------------
Sprint: Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45, Kiali Sprint #46 (was: Kiali Sprint #40, Kiali Sprint #41, Kiali Sprint #42, Kiali Sprint #43, Kiali Sprint #44, Kiali Sprint #45)
> Document alternatives for PSI OpenStack
> ---------------------------------------
>
> Key: SWSQE-1168
> URL: https://issues.redhat.com/browse/SWSQE-1168
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> When the PSI OpenStack is down, we need to use something else to provisioning OCP clusters.
> We need to document options:
> * AWS
> * https://quicklab.upshift.redhat.com/clusters
> * bot on coreos slack
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months