[JBoss JIRA] (WFWIP-143) Deployment of application (quickstart/helloworld-rs) triggers CDI warning for io.smallrye.metrics stuff
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFWIP-143:
---------------------------------------
Summary: Deployment of application (quickstart/helloworld-rs) triggers CDI warning for io.smallrye.metrics stuff
Key: WFWIP-143
URL: https://issues.jboss.org/browse/WFWIP-143
Project: WildFly WIP
Issue Type: Bug
Components: MP Metrics
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
Deployment of application (quickstart/helloworld-rs) triggers CDI warning for io.smallrye.metrics stuff
{code}
13:42:42,723 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.MetricProducer is deprecated from CDI 1.1!
13:42:42,734 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.MetricNameFactory is deprecated from CDI 1.1!
13:42:42,736 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.MetricsInterceptor is deprecated from CDI 1.1!
13:42:42,741 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.MetricRegistries is deprecated from CDI 1.1!
13:42:42,744 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.MeteredInterceptor is deprecated from CDI 1.1!
13:42:42,750 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.CountedInterceptor is deprecated from CDI 1.1!
13:42:42,753 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.TimedInterceptor is deprecated from CDI 1.1!
13:42:42,756 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.MetricsRequestHandler is deprecated from CDI 1.1!
{code}
These WARN messages must go away by using proper api. Some EAP customers are doing log auditing and analysis for each entry which is INFO+.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-143) Deployment of application (quickstart/helloworld-rs) triggers CDI warnings for io.smallrye.metrics stuff
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFWIP-143?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda updated WFWIP-143:
------------------------------------
Summary: Deployment of application (quickstart/helloworld-rs) triggers CDI warnings for io.smallrye.metrics stuff (was: Deployment of application (quickstart/helloworld-rs) triggers CDI warning for io.smallrye.metrics stuff)
> Deployment of application (quickstart/helloworld-rs) triggers CDI warnings for io.smallrye.metrics stuff
> --------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-143
> URL: https://issues.jboss.org/browse/WFWIP-143
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Deployment of application (quickstart/helloworld-rs) triggers CDI warning for io.smallrye.metrics stuff
> {code}
> 13:42:42,723 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.MetricProducer is deprecated from CDI 1.1!
> 13:42:42,734 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.MetricNameFactory is deprecated from CDI 1.1!
> 13:42:42,736 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.MetricsInterceptor is deprecated from CDI 1.1!
> 13:42:42,741 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.MetricRegistries is deprecated from CDI 1.1!
> 13:42:42,744 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.MeteredInterceptor is deprecated from CDI 1.1!
> 13:42:42,750 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.CountedInterceptor is deprecated from CDI 1.1!
> 13:42:42,753 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.interceptors.TimedInterceptor is deprecated from CDI 1.1!
> 13:42:42,756 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class io.smallrye.metrics.MetricsRequestHandler is deprecated from CDI 1.1!
> {code}
> These WARN messages must go away by using proper api. Some EAP customers are doing log auditing and analysis for each entry which is INFO+.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-140) Server shutdown or microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFWIP-140?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda updated WFWIP-140:
------------------------------------
Priority: Blocker (was: Critical)
> Server shutdown or microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
> --------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-140
> URL: https://issues.jboss.org/browse/WFWIP-140
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
> I think this should be decreased to DEBUG level.
> {code}
> 12:09:38,411 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.currentLoadedClass.count]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalLoadedClass.count]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalUnloadedClass.count]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.availableProcessors]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.systemLoadAverage]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: gc.G1 Old Generation.count]
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-140) Server shutdown or microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFWIP-140?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda updated WFWIP-140:
------------------------------------
Description:
Server shutdown causes INFO log entry for each metric.
microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric.
I think this should be decreased to DEBUG level.
{code}
12:09:38,411 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.currentLoadedClass.count]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalLoadedClass.count]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalUnloadedClass.count]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.availableProcessors]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.systemLoadAverage]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: gc.G1 Old Generation.count]
...
{code}
was:
microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
I think this should be decreased to DEBUG level.
{code}
12:09:38,411 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.currentLoadedClass.count]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalLoadedClass.count]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalUnloadedClass.count]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.availableProcessors]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.systemLoadAverage]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: gc.G1 Old Generation.count]
...
{code}
> Server shutdown or microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
> --------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-140
> URL: https://issues.jboss.org/browse/WFWIP-140
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Server shutdown causes INFO log entry for each metric.
> microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric.
> I think this should be decreased to DEBUG level.
> {code}
> 12:09:38,411 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.currentLoadedClass.count]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalLoadedClass.count]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalUnloadedClass.count]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.availableProcessors]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.systemLoadAverage]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: gc.G1 Old Generation.count]
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-142) Vendor metrics - loaded_modules reports incorrect value
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFWIP-142?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda updated WFWIP-142:
------------------------------------
Priority: Blocker (was: Major)
> Vendor metrics - loaded_modules reports incorrect value
> -------------------------------------------------------
>
> Key: WFWIP-142
> URL: https://issues.jboss.org/browse/WFWIP-142
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> Vendor metrics - loaded_modules reports incorrect value
> {code}
> curl http://localhost:10090/metrics/vendor 2>/dev/null | grep loaded_modules
> # HELP vendor:loaded_modules Number of loaded modules
> # TYPE vendor:loaded_modules gauge
> vendor:loaded_modules 23.0
> {code}
> When I tried Thorntail 2 based deployment I got {{vendor:loaded_modules 298.0}}
> WF probably reports incorrect value for loaded modules.
> The same value is reported when I deploy {{quickstart/helloworld-rs/target/helloworld-rs.war}} application. For sure new modules are triggered by deplyment.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-142) Vendor metrics - loaded_modules reports incorrect value
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFWIP-142:
---------------------------------------
Summary: Vendor metrics - loaded_modules reports incorrect value
Key: WFWIP-142
URL: https://issues.jboss.org/browse/WFWIP-142
Project: WildFly WIP
Issue Type: Bug
Components: MP Metrics
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
Vendor metrics - loaded_modules reports incorrect value
{code}
curl http://localhost:10090/metrics/vendor 2>/dev/null | grep loaded_modules
# HELP vendor:loaded_modules Number of loaded modules
# TYPE vendor:loaded_modules gauge
vendor:loaded_modules 23.0
{code}
When I tried Thorntail 2 based deployment I got {{vendor:loaded_modules 298.0}}
WF probably reports incorrect value for loaded modules.
The same value is reported when I deploy {{quickstart/helloworld-rs/target/helloworld-rs.war}} application. For sure new modules are triggered by deplyment.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-140) Server shutdown or microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFWIP-140?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda updated WFWIP-140:
------------------------------------
Summary: Server shutdown or microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric (was: microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric)
> Server shutdown or microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
> --------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-140
> URL: https://issues.jboss.org/browse/WFWIP-140
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Critical
>
> microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
> I think this should be decreased to DEBUG level.
> {code}
> 12:09:38,411 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.currentLoadedClass.count]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalLoadedClass.count]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalUnloadedClass.count]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.availableProcessors]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.systemLoadAverage]
> 12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: gc.G1 Old Generation.count]
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3249) [DMN Designer] Add support for optional typeRefs
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3249?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-3249 at 11/6/18 7:39 AM:
---------------------------------------------------------------------
[~manstis] I try to avoid the use of {{null}} as part of the business logic as much as possible, so a value representing the absence of the {{TypeRef}} sounds perfectly reasonable to me :-)
was (Author: karreiro):
[~manstis] I try to avoid the use of {{null}} as part of the business logic as much as possible, so a value representing the absence of the {{TypeRef}} sounds perfectly reasonable to me.
> [DMN Designer] Add support for optional typeRefs
> ------------------------------------------------
>
> Key: DROOLS-3249
> URL: https://issues.jboss.org/browse/DROOLS-3249
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Daniel José dos Santos
> Priority: Critical
> Labels: drools-tools
>
> At the moment {{TypeRef}} is a mandatory field within the editor.
> This is a hard limitation of use of the Properties Panel bean-binding (it cannot bind to {{null}} values). However the DMN Specification states that {{TypeRef}} are optional (and we are working around by changing the _default_ to {{Any}} - see [DROOLS-3248|https://issues.jboss.org/browse/DROOLS-3248]).
> We need to change the UI and marshaller to be able to support _optional_ {{TypeRef}}. This would (probably) require adding a _magic_ value to {{BuiltInType}} representing a "null" selection. It would need to:
> - Appear at the top of the "Data Type selector" widget (with label "<None>" or similar)
> - Be the _selected_ option when the {{TypeRef}} is the new _magic_ value (this should happen automatically, but worth checking!)
> - The marshaller should set the {{TypeRef}} to the _magic_ {{BuiltInType}} if the DMN model (coming from XML->{{kie-dmn-model}}->workbench model) has a {{null}} {{TypeRef}} - the _magic_ value is only to be used _client-side_.
> - The marshaller should set the {{TypeRef}} to {{null}} when converting from the workbench model to {{kie-dmn-model}} and the workbench model {{TypeRef}} is the _magic_ value - again, the _magic_ value is only to be used _client-side_.
> - Check that creating new data-types does not show the _magic_ value (it uses a different widget, but population of the widget probably iterates all {{BuiltInType}}.
> [~tari_manga] [~karreiro] seem reasonable to you?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3249) [DMN Designer] Add support for optional typeRefs
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3249?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-3249:
--------------------------------------------
[~manstis] I try to avoid the use of {{null}} as part of the business logic as much as possible, so a value representing the absence of the {{TypeRef}} sounds perfectly reasonable to me.
> [DMN Designer] Add support for optional typeRefs
> ------------------------------------------------
>
> Key: DROOLS-3249
> URL: https://issues.jboss.org/browse/DROOLS-3249
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Daniel José dos Santos
> Priority: Critical
> Labels: drools-tools
>
> At the moment {{TypeRef}} is a mandatory field within the editor.
> This is a hard limitation of use of the Properties Panel bean-binding (it cannot bind to {{null}} values). However the DMN Specification states that {{TypeRef}} are optional (and we are working around by changing the _default_ to {{Any}} - see [DROOLS-3248|https://issues.jboss.org/browse/DROOLS-3248]).
> We need to change the UI and marshaller to be able to support _optional_ {{TypeRef}}. This would (probably) require adding a _magic_ value to {{BuiltInType}} representing a "null" selection. It would need to:
> - Appear at the top of the "Data Type selector" widget (with label "<None>" or similar)
> - Be the _selected_ option when the {{TypeRef}} is the new _magic_ value (this should happen automatically, but worth checking!)
> - The marshaller should set the {{TypeRef}} to the _magic_ {{BuiltInType}} if the DMN model (coming from XML->{{kie-dmn-model}}->workbench model) has a {{null}} {{TypeRef}} - the _magic_ value is only to be used _client-side_.
> - The marshaller should set the {{TypeRef}} to {{null}} when converting from the workbench model to {{kie-dmn-model}} and the workbench model {{TypeRef}} is the _magic_ value - again, the _magic_ value is only to be used _client-side_.
> - Check that creating new data-types does not show the _magic_ value (it uses a different widget, but population of the widget probably iterates all {{BuiltInType}}.
> [~tari_manga] [~karreiro] seem reasonable to you?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBVFS-207) Provide way to retrieve VirtualFile instance from url.openConnection()
by Tomas Hofman (Jira)
[ https://issues.jboss.org/browse/JBVFS-207?page=com.atlassian.jira.plugin.... ]
Tomas Hofman updated JBVFS-207:
-------------------------------
Summary: Provide way to retrieve VirtualFile instance from url.openConnection() (was: Provide way to retrieve VirtualFile instance from VirtualFileURLConnection)
> Provide way to retrieve VirtualFile instance from url.openConnection()
> ----------------------------------------------------------------------
>
> Key: JBVFS-207
> URL: https://issues.jboss.org/browse/JBVFS-207
> Project: JBoss VFS
> Issue Type: Enhancement
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
> Priority: Major
>
> It is not possible to obtain VirtualFile (and by extensions it's physicalFile) instance wrapped in VirtualFileURLConnection without using reflection.
> Code snippet from Drools [1], where they try to get hold of {{VirtualFile#getPhysicalFile()}}:
> {code}
> private static Object findVirtualFile( URL url ) throws IOException {
> URLConnection urlConnection = url.openConnection();
> try {
> if ( urlConnection.getClass().getName().equals( "org.jboss.vfs.protocol.VirtualFileURLConnection" ) ) {
> Field f = urlConnection.getClass().getDeclaredField( "file" );
> f.setAccessible( true );
> return f.get( urlConnection );
> }
> } catch (NoSuchFieldException | IllegalAccessException e) {
> // ignored
> }
> return urlConnection.getContent();
> }
> {code}
> [1] https://github.com/kiegroup/drools/commit/2a36f67a29ed06d0f980a60ff1c81fa...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months