4:11 p.m.
Paul Nittel created EMBJOPR-370:
-----------------------------------
Summary: Local Tx Datasource Security Deployment Type randomly changes from
None
Key: EMBJOPR-370
URL: https://issues.jboss.org/browse/EMBJOPR-370
Project: Embedded Jopr
Issue Type: Bug
Components: Core Infrastructure
Environment: SOA 5.3 ER4 / EDS with server on RHEL 6 and Firefox on Fedora 16
Reporter: Paul Nittel
In defining my datasource, I find I cannot leave the Security Deployment Type in its
default configuration (unset checked, radio buttons cleared). To set it the way I need, I
uncheck the unset box and select the None radio button (I've already defined the other
attributes).
Click Save.
Go back and review the configuration and I (occasionally) find the None ahs changed to
Application or Domain and Application. The -ds.xml file is misconfigured in the same
fashion, showing this:
<security-domain-and-application xsi:type="securityMetaData"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
This behavior, and the need to unset and select None when that it described as the Default
value, seems incorrect.
--
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
8:41 a.m.
[
https://issues.jboss.org/browse/EMBJOPR-370?page=com.atlassian.jira.plugi...
]
RH Bugzilla Integration updated EMBJOPR-370:
--------------------------------------------
Bugzilla Update: Perform
Local Tx Datasource Security Deployment Type randomly changes from
None
-----------------------------------------------------------------------
Key: EMBJOPR-370
URL: https://issues.jboss.org/browse/EMBJOPR-370
Project: Embedded Jopr
Issue Type: Bug
Components: Core Infrastructure
Environment: SOA 5.3 ER4 / EDS with server on RHEL 6 and Firefox on Fedora 16
Reporter: Paul Nittel
In defining my datasource, I find I cannot leave the Security Deployment Type in its
default configuration (unset checked, radio buttons cleared). To set it the way I need, I
uncheck the unset box and select the None radio button (I've already defined the other
attributes).
Click Save.
Go back and review the configuration and I (occasionally) find the None ahs changed to
Application or Domain and Application. The -ds.xml file is misconfigured in the same
fashion, showing this:
<security-domain-and-application xsi:type="securityMetaData"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
This behavior, and the need to unset and select None when that it described as the
Default value, seems incorrect.
--
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
8:41 a.m.
[
https://issues.jboss.org/browse/EMBJOPR-370?page=com.atlassian.jira.plugi...
]
RH Bugzilla Integration updated EMBJOPR-370:
--------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=841238
Local Tx Datasource Security Deployment Type randomly changes from
None
-----------------------------------------------------------------------
Key: EMBJOPR-370
URL: https://issues.jboss.org/browse/EMBJOPR-370
Project: Embedded Jopr
Issue Type: Bug
Components: Core Infrastructure
Environment: SOA 5.3 ER4 / EDS with server on RHEL 6 and Firefox on Fedora 16
Reporter: Paul Nittel
In defining my datasource, I find I cannot leave the Security Deployment Type in its
default configuration (unset checked, radio buttons cleared). To set it the way I need, I
uncheck the unset box and select the None radio button (I've already defined the other
attributes).
Click Save.
Go back and review the configuration and I (occasionally) find the None ahs changed to
Application or Domain and Application. The -ds.xml file is misconfigured in the same
fashion, showing this:
<security-domain-and-application xsi:type="securityMetaData"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
This behavior, and the need to unset and select None when that it described as the
Default value, seems incorrect.
--
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
8:41 a.m.
[
https://issues.jboss.org/browse/EMBJOPR-370?page=com.atlassian.jira.plugi...
]
RH Bugzilla Integration commented on EMBJOPR-370:
-------------------------------------------------
Paul Nittel <pnittel(a)redhat.com> made a comment on [bug
841238|https://bugzilla.redhat.com/show_bug.cgi?id=841238]
This is happening with RHQ, but I cannot figure out how to log it as that component!
Description of problem:
When creating a local Tx datasource, the user is required to uncheck the unset box and
choose one of the four radio button choices, even though the description shows
"None" is the default value.
If the user wants to use "None" they should not have to do anything with
Security Deployment Type. Instead, they must uncheck the unset box and select the None
radio button.
This brings us to the second problem: When the datasource is saved, the Security
Deployment Type is (almost) always some value other than the "None" that was
specified. The -ds.xml files reflect the incorrect setting.
Version-Release number of selected component (if applicable):
SOA-P 5.3 ER5
How reproducible:
~100%
Steps to Reproduce:
1. Create a Local Tx Datasource
2. Fill out all fields, but leave the Security Deployment Type alone... we will use the
default "None" value
3. Save the datasource
4. At this point you will get an error proclaiming the need to specify the Security
Deployment Type.
5. Specify it.
6. Save again
7. Go back and see what vlue was saved for the Security Deployment Type. Probably not
"None".
Actual results:
Expected results:
Additional info:
Local Tx Datasource Security Deployment Type randomly changes from
None
-----------------------------------------------------------------------
Key: EMBJOPR-370
URL: https://issues.jboss.org/browse/EMBJOPR-370
Project: Embedded Jopr
Issue Type: Bug
Components: Core Infrastructure
Environment: SOA 5.3 ER4 / EDS with server on RHEL 6 and Firefox on Fedora 16
Reporter: Paul Nittel
In defining my datasource, I find I cannot leave the Security Deployment Type in its
default configuration (unset checked, radio buttons cleared). To set it the way I need, I
uncheck the unset box and select the None radio button (I've already defined the other
attributes).
Click Save.
Go back and review the configuration and I (occasionally) find the None ahs changed to
Application or Domain and Application. The -ds.xml file is misconfigured in the same
fashion, showing this:
<security-domain-and-application xsi:type="securityMetaData"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
This behavior, and the need to unset and select None when that it described as the
Default value, seems incorrect.
--
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
4310
days inactive
4322
days old
embjopr-issues@lists.jboss.org
3 comments
2 participants
participants (2)
-
Paul Nittel (JIRA) -
RH Bugzilla Integration (JIRA)