[JBoss JIRA] (WFCORE-3259) ModelTestUtils isn't confirming the transformed boot ops work on the legacy slave
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-3259:
----------------------------------------
Summary: ModelTestUtils isn't confirming the transformed boot ops work on the legacy slave
Key: WFCORE-3259
URL: https://issues.jboss.org/browse/WFCORE-3259
Project: WildFly Core
Issue Type: Bug
Components: Domain Management, Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
In checkFailedTransformedBootOperations:
{code}
if (config.isTransformComposite()) {
//Transform and execute the composite
TransformedOperation transformedComposite = mainServices.transformOperation(modelVersion, legacyComposite);
if (transformedComposite.rejectOperation(successResult())) {
Assert.fail(transformedComposite.getFailureDescription());
}
mainServices.executeOperation(modelVersion, transformedComposite);
}
{code}
The result of that "mainServices.executeOperation" is ignored, so if the transformation isn't actually producing good ops, we don't know that.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9313) DataSource and RA services miss dependency to legacy security service
by Flavia Rainone (JIRA)
Flavia Rainone created WFLY-9313:
------------------------------------
Summary: DataSource and RA services miss dependency to legacy security service
Key: WFLY-9313
URL: https://issues.jboss.org/browse/WFLY-9313
Project: WildFly
Issue Type: Bug
Components: JCA
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Priority: Critical
Fix For: 11.0.0.Final
In ActivationSecurityUtil and DsDeploymentXmlInstallProcessor, the necessary dependency to legacy security subsystem might be skipped because some metadata is being overlooked:
- connection definition security metadata
- connection definition recovery security metadata
- xa data source recovery security metadata
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9310) Class loading hierarchie
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9310?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-9310:
-----------------------------------
Priority: Major (was: Blocker)
> Class loading hierarchie
> -------------------------
>
> Key: WFLY-9310
> URL: https://issues.jboss.org/browse/WFLY-9310
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 10.1.0.Final
> Environment: windows 7
> oracle jdk hotspot 8
> wildfly 10 final
> Reporter: stefano canu
> Assignee: David Lloyd
> Attachments: image-2017-09-07-12-57-48-779.png, image-2017-09-07-12-57-52-827.png, image-2017-09-07-12-57-59-849.png
>
>
> Deployng an EAR application with hibernate 4.x jars in lib folders but is ignored and workning with AS module (hibernate 5.0.10) . i tried to do module exclusion by using jboss-deployment- structure but whitout any luck.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9310) Class loading hierarchie
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9310?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-9310:
-----------------------------------
Component/s: JPA / Hibernate
> Class loading hierarchie
> -------------------------
>
> Key: WFLY-9310
> URL: https://issues.jboss.org/browse/WFLY-9310
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading, JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: windows 7
> oracle jdk hotspot 8
> wildfly 10 final
> Reporter: stefano canu
> Assignee: David Lloyd
> Attachments: image-2017-09-07-12-57-48-779.png, image-2017-09-07-12-57-52-827.png, image-2017-09-07-12-57-59-849.png
>
>
> Deployng an EAR application with hibernate 4.x jars in lib folders but is ignored and workning with AS module (hibernate 5.0.10) . i tried to do module exclusion by using jboss-deployment- structure but whitout any luck.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3256) Filters.filterToFilterSpec fails if ANY or ALL include legal undefined fields
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3256?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3256:
------------------------------------------
[~jamezp] I did work around it in the WFCORE-3255 fix, and really the "workaround" was better code overall and not a workaround. So to me this is just something I noticed that's not quite right but isn't a big deal at all.
> Filters.filterToFilterSpec fails if ANY or ALL include legal undefined fields
> -----------------------------------------------------------------------------
>
> Key: WFCORE-3256
> URL: https://issues.jboss.org/browse/WFCORE-3256
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Brian Stansberry
> Assignee: James Perkins
> Priority: Minor
>
> Say you have a filter value like this:
> {code}
> {
> "any" => {
> "match" => ".*",
> "change-level" => undefined,
> "level" => undefined,
> "level-range" => undefined,
> "not" => undefined
> },
> "all" => undefined,
> "change-level" => undefined,
> "level" => undefined,
> "level-range" => undefined,
> "not" => undefined
> }
> {code}
> Writing that will fail with "WFLYLOG0025: Filter ("change-level" => undefined) is invalid".
> This is because filterToFilterSpec will process the "any" node by iterating over its fields and recursing, and as soon as it gets to one of the 'undefined' ones it will fail. But the overall structure should be fine.
> I hit this when testing a WFCORE-3255 fix, one that had the effect of adding "change-level" => undefined, etc to the params used by LoggingOperationsSubsystemTestCase.testLegacyFilters.
> I can probably work around this easily enough and IIRC this 'filter' stuff is real old, so this is no big deal.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months