April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-133) Expression Language 3.0 (JSR-341) APIs

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-133?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-133: ------------------------------------- Additional updates were made based on the RI 3.0-b08 APIs: https://github.com/jboss/jboss-el-api_spec/commit/0ac8cc1e1dc0459ff25b1dc... This also includes a change to use com.sun.el.ExpressionFactoryImpl: https://github.com/jboss/jboss-el-api_spec/commit/0ac8cc1e1dc0459ff25b1dc... > Expression Language 3.0 (JSR-341) APIs > -------------------------------------- > > Key: JBEE-133 > URL: https://issues.jboss.org/browse/JBEE-133 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-javaee-specs > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1177) Recursive expression resolution

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1177?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1177: ----------------------------------- Assignee: Jess Sightler > Recursive expression resolution > ------------------------------- > > Key: WFLY-1177 > URL: https://issues.jboss.org/browse/WFLY-1177 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jess Sightler > > When resolving an expression, keep resolving until the output of the resolution matches the input. > Use case: > ${sys.prop.with.host.specific.value} > resolves to > ${VAULT::xxxxx} > which resolves to > thesecret > Basically, the main mechanism for customizing domain-level configs on a per-host basis is to use expressions and use different values on each host. But this breaks down when a vault expression is added to the mix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-996) No way to query valid property values for objects of type PROPERTY via cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-996?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved WFLY-996. ----------------------------------- Fix Version/s: 8.0.0.Alpha1 Resolution: Won't Fix There's nothing we will do about this as a general issue. If a particular resource is using properties instead of exposing fully defined attributes, please file a specific to get that corrected. > No way to query valid property values for objects of type PROPERTY via cli > -------------------------------------------------------------------------- > > Key: WFLY-996 > URL: https://issues.jboss.org/browse/WFLY-996 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Environment: CLI browsing AS 7.1.1.Final model with modcluster enabled via *ha profile. > Reporter: Simeon Pinder > Labels: rhq > Fix For: 8.0.0.Alpha1 > > > If you run the following to browse the resource-description > subsystem=modcluster/mod-cluster-config=configuration/:read-resource-description(operations=true,inherited=false,recursive=false,proxies=false) > You'll encounter Object type = PROPERTY > "property" => { > "description" => "Properties for the metric.", > "type" => PROPERTY, > "required" => false > } > Which has an acceptable list of property values as described here. > http://docs.jboss.org/mod_cluster/1.2.0/html/java.AS7config.html#LoadMetric > There is no way to query the acceptable and currently supported list of property values via cli. You must hard code and risk going out of synch with as7/modclusters supported values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1014) Enable CORS requests

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1014?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1014: ----------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > Enable CORS requests > -------------------- > > Key: WFLY-1014 > URL: https://issues.jboss.org/browse/WFLY-1014 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Harald Pehl > Assignee: Darran Lofthouse > > We've been prototyping an alternative distribution channel for the console and have setup a demo that leverages the mozilla app store to deliver the AS7 web console to users: > https://marketplace.firefox.com/app/kea/?src=mkt-search > For this to work the AS needs to fully support CORS [1]. The general idea is that you can retrieve the console through a marketplace like the mozilla one (chrome would be another alternative) and connect to any domain controller, wether it runs locally or remotely. > If want to give it shot, point four firefox browser to the marketplace URL, launch the app and connect to our CORS demo instance that runs on EC2: > http://as7-preview.dyndns.org:9990 > user: admin > pass: webstore123! > [1] http://en.wikipedia.org/wiki/Cross-origin_resource_sharing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-352) EAP 6 Domain Mode Logging for Management is nonexistent.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-352?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-352: ---------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > EAP 6 Domain Mode Logging for Management is nonexistent. > --------------------------------------------------------- > > Key: WFLY-352 > URL: https://issues.jboss.org/browse/WFLY-352 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Eric Rich > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > Attachments: jboss-as-domain-management-7.1.2.Final-redhat-1.jar, log_mgmt_auth_calls.txt > > > When trying to diagnose LDAP or Admin Configuration issue in Domain mode there is currently no logging for any of the authentication information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1270) Split logging subsystem parser for different schema versions

by James Perkins (JIRA)

James Perkins created WFLY-1270: ----------------------------------- Summary: Split logging subsystem parser for different schema versions Key: WFLY-1270 URL: https://issues.jboss.org/browse/WFLY-1270 Project: WildFly Issue Type: Enhancement Components: Logging Reporter: James Perkins Assignee: James Perkins Priority: Minor The logging subsystem parser currently reads and writes XML for all schema versions. Split the reads out into a different parsers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-710) CLI command for executing the deployment scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-710?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-710: ---------------------------------- Component/s: Server > CLI command for executing the deployment scanner > ------------------------------------------------ > > Key: WFLY-710 > URL: https://issues.jboss.org/browse/WFLY-710 > Project: WildFly > Issue Type: Feature Request > Components: CLI, Server > Reporter: Ben Schofield > Priority: Minor > Fix For: Awaiting Volunteers > > > provide a CLI command that will run the deployment scanner even if the deployment scanner is turned off. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-688) Incorrect URL named in the 'Kitchensink' quickstart 'Readme.md' file.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-688?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-688: ---------------------------------- Assignee: (was: Brian Stansberry) > Incorrect URL named in the 'Kitchensink' quickstart 'Readme.md' file. > --------------------------------------------------------------------- > > Key: WFLY-688 > URL: https://issues.jboss.org/browse/WFLY-688 > Project: WildFly > Issue Type: Bug > Components: Documentation > Environment: Fedora 14, latest AS7 download, latest AS7 quickstarts download > Reporter: Mark Yourcheck > Priority: Minor > Labels: eap6-ux > Fix For: Awaiting Volunteers > > Attachments: readme.md > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The kitchensink quickstart Readme.md line #50 directs the user to: > http://localhost:8080/jboss-javaee6-webapp-src > It should be: > http://localhost:8080/jboss-as-kitchensink > Note: Readme.html names the correct URL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-709) read-operation-name and read-operation-description should be combined

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-709?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-709: ---------------------------------- Assignee: (was: Brian Stansberry) > read-operation-name and read-operation-description should be combined > --------------------------------------------------------------------- > > Key: WFLY-709 > URL: https://issues.jboss.org/browse/WFLY-709 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Kevin Barfield > Priority: Minor > Labels: eap6-ux > Fix For: Awaiting Volunteers > > > For usability, there should be a way to get a list of operation names with the descriptions attached > Example: > read-resource - This shows you the resources at the this node > etc > etc > etc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-255) Improve reporting during deployment hang

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-255?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-255: ---------------------------------- Assignee: (was: Brian Stansberry) > Improve reporting during deployment hang > ---------------------------------------- > > Key: WFLY-255 > URL: https://issues.jboss.org/browse/WFLY-255 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Environment: http://java.net/jira/browse/EJB_SPEC-60 > java version "1.7.0_09" > OpenJDK Runtime Environment (IcedTea7 2.3.3) (7u9-2.3.3-0ubuntu1~12.10.1) > OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode) > Ubuntu 12.10 > Reporter: Carlo de Wolf > Fix For: 8.0.0.Beta1 > > Attachments: deployment-hang-20130205.txt, server.log > > > Management Thread waits indefinitely for, what seems to be, a finished operation. > {noformat} > "management-handler-thread - 2" prio=10 tid=0x00007fa1380d0000 nid=0x7683 in Object.wait() [0x00007fa136deb000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at java.lang.Object.wait(Object.java:503) > at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158) > - locked <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor) > at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:464) > at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:148) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:299) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 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 April 2013