March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-580) Recursive read-resource with include-runtime=true assumes all runtime singleton resources will be present.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-580?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFCORE-580: ------------------------------------ Labels: affects_elytron (was: ) > Recursive read-resource with include-runtime=true assumes all runtime singleton resources will be present. > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-580 > URL: https://issues.jboss.org/browse/WFCORE-580 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha19 > Reporter: Darran Lofthouse > Assignee: Brian Stansberry > Labels: affects_elytron > Fix For: 1.0.0.Beta1 > > > Take the following hierarchy: - > keystore=xxx > alias=yyy > certificate-chain=default > certificate-chain=x509 > keystore is a regular resource with storage=configuration. > alias is a regular resource with storage=runtime > certificate-chain=default and certificate-chain=x509 are regular resources with storage=runtime. > So alias represents a single alias from a Java KeyStore, this may or may not have a certificate chain and it may be a default chain or it may be an x509 chain. > The recursive read-resource is fine with regular resources such as alias as it has to rely on the underlying resource implementation to identify the instances that actually exist. > For the singleton resources however the following method is called: - > {code} > org.jboss.as.controller.operations.global.GlobalOperationHandlers.getChildAddresses(OperationContext, PathAddress, ImmutableManagementResourceRegistration, Resource, String) > {code} > Within this method the following check takes place: - > {code} > if (resource != null && resource.hasChildren(childType)) { > Set<String> childNames = resource.getChildrenNames(childType); > if (element.isWildcard()) { > set.addAll(childNames); > } else if (childNames.contains(element.getValue())) { > set.add(element.getValue()); > } > {code} > Up to this point all is fine, the children the resource claims are available are the only ones added. > But further down this happens: - > {code} > if (!element.isWildcard()) { > ImmutableManagementResourceRegistration childReg = registry.getSubModel(PathAddress.pathAddress(element)); > if (childReg != null && childReg.isRuntimeOnly()) { > set.add(element.getValue()); > } > } > {code} > So even though the resource was previously checked and missing children excluded they are now added back. > The end result in this example is that the recursive read resource attempts to read for certificate-chain=default when it should only be reading for certificate-chain=x509 as already reported by the resource implementation. > From a discussion in HipChat yesterday there was general agreement this behaviour seems to be wrong, however support for Proxied resources may be (incorrectly) dependent on this. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-579) ProxyMetadataSource does not return JDK8 'default' methods fro minterfaces

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-579?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-579: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1196686 > ProxyMetadataSource does not return JDK8 'default' methods fro minterfaces > -------------------------------------------------------------------------- > > Key: WFCORE-579 > URL: https://issues.jboss.org/browse/WFCORE-579 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha19 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-579) ProxyMetadataSource does not return JDK8 'default' methods fro minterfaces

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFCORE-579: ----------------------------------------- Summary: ProxyMetadataSource does not return JDK8 'default' methods fro minterfaces Key: WFCORE-579 URL: https://issues.jboss.org/browse/WFCORE-579 Project: WildFly Core Issue Type: Bug Components: Server Affects Versions: 1.0.0.Alpha19 Reporter: Bartosz Baranowski Assignee: Bartosz Baranowski Fix For: 1.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4404) View does not inherit 'default' methods from interfaces( JDK8 )

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4404?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4404: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1196686 > View does not inherit 'default' methods from interfaces( JDK8 ) > --------------------------------------------------------------- > > Key: WFLY-4404 > URL: https://issues.jboss.org/browse/WFLY-4404 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 9.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 9.0.0.Beta1 > > > View and View service do not inherit JDK8 'default' methods from interfaces. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4404) View does not inherit 'default' methods from interfaces( JDK8 )

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFLY-4404: ---------------------------------------- Summary: View does not inherit 'default' methods from interfaces( JDK8 ) Key: WFLY-4404 URL: https://issues.jboss.org/browse/WFLY-4404 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 9.0.0.Alpha1 Reporter: Bartosz Baranowski Assignee: Jason Greene Fix For: 9.0.0.Beta1 View and View service do not inherit JDK8 'default' methods from interfaces. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4404) View does not inherit 'default' methods from interfaces( JDK8 )

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4404?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski reassigned WFLY-4404: ---------------------------------------- Assignee: Bartosz Baranowski (was: Jason Greene) > View does not inherit 'default' methods from interfaces( JDK8 ) > --------------------------------------------------------------- > > Key: WFLY-4404 > URL: https://issues.jboss.org/browse/WFLY-4404 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 9.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 9.0.0.Beta1 > > > View and View service do not inherit JDK8 'default' methods from interfaces. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4356) build.sh fails on OS X

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-4356?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-4356: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/7228 (was: https://github.com/wildfly/wildfly/pull/7208) > build.sh fails on OS X > ----------------------- > > Key: WFLY-4356 > URL: https://issues.jboss.org/browse/WFLY-4356 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Jeff Mesnil > Assignee: Carlo de Wolf > > the build.sh script fails on Mac OS X: > {noformat} > $ ./build.sh clean install > Maven already exists > Maven is correct version > ./build.sh: line 107: ulimit: open files: cannot modify limit: Invalid argument > {noformat} > The ulimit error was already present before but since WFLY-4305, the build.sh script will exit after this error instead of continuing. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4305) Script rumbles on after error

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-4305?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-4305: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/7228 (was: https://github.com/wildfly/wildfly/pull/7153) > Script rumbles on after error > ----------------------------- > > Key: WFLY-4305 > URL: https://issues.jboss.org/browse/WFLY-4305 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > Fix For: 9.0.0.Beta1 > > > After a failure in the script it rumbles on. > {noformat} > (master) carlo@devel01:~/work/wildfly$ ./build.sh clean > ./tools/download-maven.sh: 20: ./tools/download-maven.sh: curl: not found > Archive: maven.zip > End-of-central-directory signature not found. Either this file is not > a zipfile, or it constitutes one disk of a multi-part archive. In the > latter case the central directory and zipfile comment will be found on > the last disk(s) of this archive. > unzip: cannot find zipfile directory in one of maven.zip or > maven.zip.zip, and cannot find maven.zip.ZIP, period. > mv: cannot stat ‘apache-maven*’: No such file or directory > build.sh: Could not locate Maven; check $MVN or $MAVEN_HOME. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4325) Relative path error in context parameter on Windows

by Nicklas Karlsson (JIRA)

[ https://issues.jboss.org/browse/WFLY-4325?page=com.atlassian.jira.plugin.... ] Nicklas Karlsson commented on WFLY-4325: ---------------------------------------- Actually, I recall I stumbled on this again once more, I think I was using Paths.get(URI) and passing in an uri converted in a servlet doing getClass().getResourceAsStream... etc > Relative path error in context parameter on Windows > --------------------------------------------------- > > Key: WFLY-4325 > URL: https://issues.jboss.org/browse/WFLY-4325 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.Beta1 > Reporter: Nicklas Karlsson > Assignee: Tomaz Cerar > > Deploying the Eclipse BIRT viewer with a context parameter containing a relative reference as a context parameter on a windows machine > <param-value>../birtdata/logs</param-value> > results in > {quote} > 2015-02-05 10:07:37,736 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./birt: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./birt: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: java.nio.file.InvalidPathException: Illegal char <:> at index 2: \C:\Java\WildFly-9.x-testi\standalone\deployments\birt-4.4.0.war\..\birtdata\logs\org.eclipse.datatools.connectivity.oda_2015_02_05_10_07_37.log.lck > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:221) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > ... 3 more > Caused by: java.nio.file.InvalidPathException: Illegal char <:> at index 2: \C:\Java\WildFly-9.x-testi\standalone\deployments\birt-4.4.0.war\..\birtdata\logs\org.eclipse.datatools.connectivity.oda_2015_02_05_10_07_37.log.lck > at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182) > at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153) > at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77) > at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94) > at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255) > at java.nio.file.Paths.get(Paths.java:84) > at java.util.logging.FileHandler.openFiles(FileHandler.java:438) > at java.util.logging.FileHandler.<init>(FileHandler.java:318) > at org.eclipse.birt.report.utility.LoggingUtil.initFileLogger(LoggingUtil.java:103) > at org.eclipse.birt.report.utility.LoggingUtil.configureLoggers(LoggingUtil.java:76) > at org.eclipse.birt.report.service.ReportEngineService.<init>(ReportEngineService.java:229) > at org.eclipse.birt.report.service.ReportEngineService.initEngineInstance(ReportEngineService.java:271) > at org.eclipse.birt.report.service.BirtViewerReportService.<init>(BirtViewerReportService.java:83) > at org.eclipse.birt.report.listener.ViewerServletContextListener.contextInitialized(ViewerServletContextListener.java:57) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:192) > ... 7 more > {quote} > This used to work on the 8.x-series -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-47) execute-commands on EAP6.1.0

by Lionel Orellana (JIRA)

[ https://issues.jboss.org/browse/JBASMP-47?page=com.atlassian.jira.plugin.... ] Lionel Orellana commented on JBASMP-47: --------------------------------------- 7.2.0.Final fails with a similar error. Unexpected element '{urn:jboss:cli:1.2}jboss-cli' I got around it by forcing the dependency to 7.3.0.Final-redhat-14. > execute-commands on EAP6.1.0 > ---------------------------- > > Key: JBASMP-47 > URL: https://issues.jboss.org/browse/JBASMP-47 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Affects Versions: 7.4.Final > Reporter: wiktorowski maximilien > Assignee: James Perkins > Fix For: 7.5.Final > > > I'm trying to use execute-commands goal with EAP 6.1.0 and got : > Failed to initialize CLI context: Failed to parse jboss-cli.xml: Unexpected element: resolve-parameter-values. > CLI dependency should be updated: > [INFO] Plugin Resolved: jboss-as-maven-plugin-7.4.Final.jar > ..... > [INFO] Plugin Dependency Resolved: jboss-as-cli-7.1.2.Final.jar -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2015