[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil updated AS7-6334:
-----------------------------
Description:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups [OK]
clustering/infinispan
cmp [OK]
configadmin [OK]
connector/datasource
connector/jca [OK]
connector/resource-adapter
deployment-scanner - WIP Kabir
ee - PR https://github.com/jbossas/jboss-as/pull/3969
ejb3 [OK]
jacorb - Just a note: the 'security' attribute transformation is not tested
jaxr [OK]
jaxrs [OK] empty subsystem
jdr - [OK] empty subsystem
jmx [OK]
jpa [OK]
jsf [OK]
jsr77 [OK] empty subsystem
logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
mail
messaging [OK]
modcluster [OK]
naming [OK]
osgi [OK]
pojo [OK] empty subsystem
remoting - [OK]
sar [OK] empty subsystem
security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407]
threads - WIP Brian
transactions [OK]
web [OK]
webservices - WIP Kabir
weld [OK] empty subsystem
xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3
was:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups [OK]
clustering/infinispan
cmp [OK]
configadmin [OK]
connector/datasource
connector/jca [OK]
connector/resource-adapter
deployment-scanner - WIP Kabir
ee - PR https://github.com/jbossas/jboss-as/pull/3969
ejb3 [OK]
jacorb - Just a note: the 'security' attribute transformation is not tested
jaxr [OK]
jaxrs [OK] empty subsystem
jdr - [OK] empty subsystem
jmx [OK]
jpa [OK]
jsf [OK]
jsr77 [OK] empty subsystem
logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
mail
messaging [OK]
modcluster [OK]
naming [OK]
osgi [OK]
pojo [OK] empty subsystem
remoting - [OK]
sar [OK] empty subsystem
security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407]
threads - WIP Brian
transactions - [PR https://github.com/jbossas/jboss-as/pull/3963]
web - [PR https://github.com/jbossas/jboss-as/pull/3963]
webservices - WIP Kabir
weld [OK] empty subsystem
xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3
> Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6334
> URL: https://issues.jboss.org/browse/AS7-6334
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> Task to track the work we've all been doing on expressions/transformers.
> See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
> 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
> 2) Basic transformation testing against 7.1.2 and 7.1.3
> 3) Reject-expression testing against 7.1.2 and 7.1.3
> Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
> Please edit this description and put an OK after the subsystem name to indicate it's good to go.
> clustering/jgroups [OK]
> clustering/infinispan
> cmp [OK]
> configadmin [OK]
> connector/datasource
> connector/jca [OK]
> connector/resource-adapter
> deployment-scanner - WIP Kabir
> ee - PR https://github.com/jbossas/jboss-as/pull/3969
> ejb3 [OK]
> jacorb - Just a note: the 'security' attribute transformation is not tested
> jaxr [OK]
> jaxrs [OK] empty subsystem
> jdr - [OK] empty subsystem
> jmx [OK]
> jpa [OK]
> jsf [OK]
> jsr77 [OK] empty subsystem
> logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
> mail
> messaging [OK]
> modcluster [OK]
> naming [OK]
> osgi [OK]
> pojo [OK] empty subsystem
> remoting - [OK]
> sar [OK] empty subsystem
> security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407]
> threads - WIP Brian
> transactions [OK]
> web [OK]
> webservices - WIP Kabir
> weld [OK] empty subsystem
> xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3
--
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
11 years, 3 months
[JBoss JIRA] (AS7-6420) trying to add already existing deployment fails with "deployment failed", but no other info
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori commented on AS7-6420:
----------------------------------------
AS7-6421 is about only showing first 10 deployments. "deployment failed" with no other info is a distinct problem - if you have hundreds of deployments (like a large osgi system would), you'd appreciate better error message (something like "the resource already exists"). I'm fine with it being a feature request instead of a bug, but some kind of user info is needed.
> trying to add already existing deployment fails with "deployment failed", but no other info
> -------------------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> EDIT: this seems to be due to already having the deployment there. When you try to readd the same deployment, you get a red box saying deployment failed, but no error message anywhere.
--
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
11 years, 3 months
[JBoss JIRA] (AS7-6420) trying to add already existing deployment fails with "deployment failed", but no other info
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler resolved AS7-6420.
---------------------------------
Resolution: Rejected
See AS7-6421
> trying to add already existing deployment fails with "deployment failed", but no other info
> -------------------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> EDIT: this seems to be due to already having the deployment there. When you try to readd the same deployment, you get a red box saying deployment failed, but no error message anywhere.
--
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
11 years, 3 months
[JBoss JIRA] (AS7-6422) OptionsRoleMappingProvider cannot work on AS7
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/AS7-6422?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on AS7-6422:
----------------------------------
given that AS7 does not provide nested properties inside properties this fix should be done to provider itself
> OptionsRoleMappingProvider cannot work on AS7
> ---------------------------------------------
>
> Key: AS7-6422
> URL: https://issues.jboss.org/browse/AS7-6422
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP)
> Reporter: Akram Ben Aissi
> Assignee: Anil Saldhana
>
> The OptionsRoleMappingProvider available in picketbox jars is intended to provided a simple way to map some toles to other roles.
> This case is usefull in many cases where you get roles from a system and want to map them to one or several JaaS Roles.
> However, OptionsRoleMappingProvider cannot be used in AS7 to map roles to groups because this provider contains an attribute Properties roleMaps which requires a Properties object to be initialized.
> A Properties object cannot be passed by AS7 configuration, so this provider cannot be used as is.
> Here is its required syntax according to picketbox documentation:
> {code:xml}
> <mapping-module code="org.jboss.security.mapping.providers.OptionsRoleMappingProvider"
> type="role">
> <module-option name="rolesMap" >
> <java:properties xmlns:java="urn:jboss:java-properties"
> xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
> xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
> <java:property>
> <java:key>validuser</java:key>
> <java:value>AuthorizedUser,InternalUser</java:value>
> </java:property>
> </java:properties>
> </module-option>
> <module-option name="replaceRoles">false</module-option>
> </mapping-module>
> </mapping>
> {code}
> Such a syntax is not possible in AS7.
> Here is the incriminated code:
> {code:java}
> private Properties roleMapProperties = new Properties();
> /**
> * Specifies
> */
> private boolean REPLACE_ROLES = false;
>
> public void init(Map<String,Object> opt)
> {
> this.options = opt;
> if(options != null)
> {
> if(options.containsKey(REPLACE_ROLES_STRING))
> {
> REPLACE_ROLES = "true".equalsIgnoreCase((String)options.get(REPLACE_ROLES_STRING));
> }
> if(options.containsKey(ROLES_MAP))
> {
> roleMapProperties = (Properties)options.get(ROLES_MAP);
> }
> }
> }
> {code}
> As you can see, roleMapProperties is a Properties.
> But in AS7, options.get(ROLES_MAP) returns a String.
> So an adapter is required to make the AS match the contract, or another implemtation is required.
--
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
11 years, 3 months
[JBoss JIRA] (AS7-6425) Imposible to define attribute via web administration console as system property expression
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6425?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6425:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
> Imposible to define attribute via web administration console as system property expression
> ------------------------------------------------------------------------------------------
>
> Key: AS7-6425
> URL: https://issues.jboss.org/browse/AS7-6425
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> What my tests show is that it's not possible to use system property expressions for defining attributes in web administration console.
> When I tried to set attribute (e.g. "Stateful Access Timeout" - Profile/Containter/EJB3) like
> {code}
> ${some.variable:5000}
> {code}
> the console does not show any error message but it does not show the information about successful update. After "Save" it just takes the expression value and says nothing.
> The change is not propagated (not saved) to xml config file.
--
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
11 years, 3 months
[JBoss JIRA] (AS7-6425) Imposible to define attribute via web administration console as system property expression
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6425?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6425:
----------------------------------
Assignee: Heiko Braun (was: Brian Stansberry)
> Imposible to define attribute via web administration console as system property expression
> ------------------------------------------------------------------------------------------
>
> Key: AS7-6425
> URL: https://issues.jboss.org/browse/AS7-6425
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Heiko Braun
> Fix For: 7.2.0.Alpha1
>
>
> What my tests show is that it's not possible to use system property expressions for defining attributes in web administration console.
> When I tried to set attribute (e.g. "Stateful Access Timeout" - Profile/Containter/EJB3) like
> {code}
> ${some.variable:5000}
> {code}
> the console does not show any error message but it does not show the information about successful update. After "Save" it just takes the expression value and says nothing.
> The change is not propagated (not saved) to xml config file.
--
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
11 years, 3 months
[JBoss JIRA] (AS7-6425) Imposible to define attribute via web administration console as system property expression
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created AS7-6425:
-------------------------------------
Summary: Imposible to define attribute via web administration console as system property expression
Key: AS7-6425
URL: https://issues.jboss.org/browse/AS7-6425
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.2.0.Alpha1
Reporter: Ondřej Chaloupka
Assignee: Brian Stansberry
What my tests show is that it's not possible to use system property expressions for defining attributes in web administration console.
When I tried to set attribute (e.g. "Stateful Access Timeout" - Profile/Containter/EJB3) like
{code}
${some.variable:5000}
{code}
the console does not show any error message but it does not show the information about successful update. After "Save" it just takes the expression value and says nothing.
The change is not propagated (not saved) to xml config file.
--
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
11 years, 3 months
[JBoss JIRA] (AS7-6424) Web administration console does not handle values set with expressions
by Ondřej Chaloupka (JIRA)
[ https://issues.jboss.org/browse/AS7-6424?page=com.atlassian.jira.plugin.s... ]
Ondřej Chaloupka updated AS7-6424:
----------------------------------
Description:
In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
This was hit on ejb subsystem.
You can try to set following tag like this
{code}
<strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
{code}
In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
was:
In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
This was hit on ejb subsystem.
You can try to set following tag like this
<strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
> Web administration console does not handle values set with expressions
> ----------------------------------------------------------------------
>
> Key: AS7-6424
> URL: https://issues.jboss.org/browse/AS7-6424
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Brian Stansberry
>
> In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
> As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
> This was hit on ejb subsystem.
> You can try to set following tag like this
> {code}
> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
> {code}
> In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
--
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
11 years, 3 months
[JBoss JIRA] (AS7-6424) Web administration console does not handle values set with expressions
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6424?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6424:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
> Web administration console does not handle values set with expressions
> ----------------------------------------------------------------------
>
> Key: AS7-6424
> URL: https://issues.jboss.org/browse/AS7-6424
> Project: Application Server 7
> Issue Type: Bug
> Components: Console
> Affects Versions: 7.2.0.Alpha1
> Reporter: Ondřej Chaloupka
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> In case of using expression in standalone.xml then web admin console does not show the evaluated expression and instead of it 0 is shown. In other cases you can see error message of the web admin console saying "Failed to parse response".
> As I was testing the behavior of web administration console just on several places I can't talk about behaving of all subsystem.
> This was hit on ejb subsystem.
> You can try to set following tag like this
> {code}
> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="${some.var:20}" instance-acquisition-timeout="${some.other.var}" instance-acquisition-timeout-unit="MINUTES"/>
> {code}
> In case of max-pool-size you'll see value 0 instead of 20 in the console. And nevertheless that you run the server with -Dsome.other.var=5 you'll see the parsing error because of the instance-acquisition-timeout attribute being set with expression.
--
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
11 years, 3 months