[JBoss JIRA] (AS7-3444) Fix description for read-resource operation
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created AS7-3444:
--------------------------------------
Summary: Fix description for read-resource operation
Key: AS7-3444
URL: https://issues.jboss.org/browse/AS7-3444
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Rostislav Svoboda
Assignee: Emanuel Muckenhuber
Fix For: 7.1.0.Final
{code}
bin/jboss-admin.sh -c command=":read-operation-description(name="read-resource")"
...
"include-runtime" => {
"type" => BOOLEAN,
"description" => "Whether to include runtime attributes (i.e. those whose value does not come from the persistent configuration) in the response. If absent, false is the default. Ignored if the 'recursive' parameter is set to true; i.e. runtime attributes can only be read in non-recursive queries.",
...
{code}
Remove 'Ignored if the 'recursive' parameter is set to true; i.e. runtime attributes can only be read in non-recursive queries.'
Support for recursive queries with runtime details was added in AS7-2033
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3467) CLONE - Inconsistency in --help output between domain and standalone
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created AS7-3467:
--------------------------------------
Summary: CLONE - Inconsistency in --help output between domain and standalone
Key: AS7-3467
URL: https://issues.jboss.org/browse/AS7-3467
Project: Application Server 7
Issue Type: Bug
Components: Scripts
Affects Versions: 7.1.0.CR1b
Reporter: Rostislav Svoboda
Assignee: Brian Stansberry
Fix For: 7.1.0.Final
Help for standalone.sh is using logging infrastructure and help for domain.sh is probably using just stdout.
- I'd prefer to use domain.sh way without '16:42:57,124 INFO [stdout]' details. Please sync output for both commands.
- There is typo in help for standalone.sh, it says '\-\-\-\-server-config=<config>', '\-' should be there just twice.
{code}
bin/domain.sh --help
...
--admin-only JBAS012066: Set the host controller's
running type to ADMIN_ONLY causing it
to open administrative interfaces and
accept management requests but not
start servers or, if this host
controller is the master for the
domain, accept incoming connections
from slave host controllers.
...
bin/standalone.sh --help
...
16:42:57,124 INFO [stdout] --admin-only Set the server's running type to
16:42:57,124 INFO [stdout] ADMIN_ONLY causing it to open
16:42:57,124 INFO [stdout] administrative interfaces and accept
16:42:57,124 INFO [stdout] management requests but not start other
16:42:57,124 INFO [stdout] runtime services or accept end user
16:42:57,124 INFO [stdout] requests.
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3464) add-user.sh - possibility of setting another Realms should be considered again
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3464?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek moved JBPAPP-8000 to AS7-3464:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-3464 (was: JBPAPP-8000)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.0.CR1b
(was: EAP 6.0.0 DR 12)
Component/s: Security
(was: Security)
Security: (was: JBoss Internal)
Docs QE Status: (was: NEW)
> add-user.sh - possibility of setting another Realms should be considered again
> ------------------------------------------------------------------------------
>
> Key: AS7-3464
> URL: https://issues.jboss.org/browse/AS7-3464
> Project: Application Server 7
> Issue Type: Bug
> Components: Security
> Affects Versions: 7.1.0.CR1b
> Reporter: Pavel Janousek
> Assignee: Anil Saldhana
> Priority: Critical
>
> I'm aware of add-user.sh isn't general tool for managing an user/groups/roles credential store at all. Is it supposed only as shorthand for quick definition of users access to admin console out of the box. Well..
> According previous paragraph it isn't to much meaningful for me to bring possibility of specify another realm during the invocation of this tool. I think already - Admin console can use another realm than ManagementRealm by change default configuration. I think already too - property file can't contain users definition belong multiple realms. As is stated in comment in the begin of file mgmt-users.properties, this file is for "declaration of users for the realm 'ManagementRealm'".
> I think we should avoid to insert new user with different realm there (it is possible now). add-user.sh doesn't manage any other file and other property file(s) can't be specified during invocation.
> I think this present situation/behavior should confuse hard our end-users - especially users with their own experiences with other JEE servers (Apache Geronimo, Sun/Oracle GlassFish etc.).
> Because we don't provide/support any tool for general CRUD managing of credential store of type like property file(s) - like other JEE app. servers do, we really should use this script/tool only as way to simple very basic user creation in default AS7 environment, because we can't support this tool in any other situation with present behavior and in a such changed environments behavior or final state is hardly understandable (if we create property file (by other way) with the same username, but in different realms, we can't log to admin console never more; if we have users in one realm, switch AS7 instance to use other "admin" realm, we can't add any from existing user to this new realm; we don't know which user belongs to which realm later etc.)
> So conclusion - I think we should remove specification of Realm from input process of add-user.sh script at all and use this script only to define users belongs to ManagementRealm realm and manages only properly mgmt-users.properties files (standalone and domain configuration)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3411) JAX-WS handler chain file not recognized for EJB3 endpoint inside a WAR
by Robert Reimann (JIRA)
Robert Reimann created AS7-3411:
-----------------------------------
Summary: JAX-WS handler chain file not recognized for EJB3 endpoint inside a WAR
Key: AS7-3411
URL: https://issues.jboss.org/browse/AS7-3411
Project: Application Server 7
Issue Type: Bug
Components: Web Services
Affects Versions: 7.1.0.CR1b
Reporter: Robert Reimann
Assignee: Alessio Soldano
I've got an EJB-Jar module with an EJB3 stateless session bean as JAX-WS endpoint. The endpoint references a handler chain via @HandlerChain annotation. While deploying the WAR the following exception is thrown.
{code}
12:36:19,529 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-15) MSC00001: Failed to start service jboss.deployment.unit."jaxws-injection-ejb3-inside.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-injection-ejb3-inside.war".PARSE: Failed to process phase PARSE of deployment "jaxws-injection-ejb3-inside.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
Caused by: java.lang.IllegalStateException
at org.jboss.as.webservices.util.ASHelper.getRequiredAttachment(ASHelper.java:166)
at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER.processAnnotation(WSIntegrationProcessorJAXWS_HANDLER.java:55)
at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:87)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
... 5 more
{code}
As far as i can tell from looking at the corresponding AS7 code the exception means that the handler chain file wasn't found. An EJB3 endpoint inside a WAR without a handler chain works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3216) Web services extension does not register write-attribute handlers for any attributes
by Brian Stansberry (Created) (JIRA)
Web services extension does not register write-attribute handlers for any attributes
------------------------------------------------------------------------------------
Key: AS7-3216
URL: https://issues.jboss.org/browse/AS7-3216
Project: Application Server 7
Issue Type: Bug
Components: Web Services
Affects Versions: 7.1.0.CR1b
Reporter: Brian Stansberry
Assignee: Alessio Soldano
Fix For: 7.1.0.Final
Any attribute that is stored in the persistent configuration (standalone/domain.xml) needs to have be registered via ManagementResourceRegistration.registerReadWriteAttribute(...). This allows the configuration to be updated without forcing the user to edit xml.
If the change to the attribute cannot be immediately reflected in the runtime, then pass an instance of org.jboss.as.controller.ReloadRequiredWriteAttributeHandler to registerReadWriteAttribute as the value for the "writeHandler" parameter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3413) Failed to read WS endpoint runtime data
by Heiko Braun (JIRA)
Heiko Braun created AS7-3413:
--------------------------------
Summary: Failed to read WS endpoint runtime data
Key: AS7-3413
URL: https://issues.jboss.org/browse/AS7-3413
Project: Application Server 7
Issue Type: Bug
Components: Web Services
Reporter: Heiko Braun
Assignee: Alessio Soldano
Fix For: 7.1.0.Final
The following op doesn't return any result nor a useful failure description.
But it should be possible to read WS runtime data from a deployment, no?
{noformat}
[standalone@localhost:9999 /] /deployment=jaxws-samples-handlerchain.war/subsystem=webservices/endpoint=jaxws-samples-handlerchain%3ATestService:read-resource(include-runtime=true)
{
"outcome" => "failed",
"rolled-back" => true
}
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months