[JBoss JIRA] (SRAMP-199) Wsdl and Xsd Derivers are not setting up import/include relationships
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-199?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-199:
-------------------------------------
Currently the WSDL and XSD derivers create relationships between the various derived artifacts that they create. Additionally, they attempt to lookup artifacts derived from other WSDLs or XSDs and create those relationships as well.
For example, if a WSDL imports an XSD, the deriver for the WSDL file will successfully create appropriate relationships to any types the wsdl references that are defined in the XSD (as long as the XSD was added to s-ramp first).
However, the actual *import* relationship (see the s-ramp spec for wsdl and xsd import relationships) is not created.
> Wsdl and Xsd Derivers are not setting up import/include relationships
> ---------------------------------------------------------------------
>
> Key: SRAMP-199
> URL: https://issues.jboss.org/browse/SRAMP-199
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.2.0 - Security & S-RAMP-1.0
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> The XSD deriver and WSDL derivers need to set up relationships to other xsd/wsdl documents when they are imported or included.
--
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
10 years, 9 months
[JBoss JIRA] (SRAMP-212) Support property expansion in CLI command files
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-212?page=com.atlassian.jira.plugin.... ]
Eric Wittmann reassigned SRAMP-212:
-----------------------------------
Assignee: David virgil naranjo (was: Eric Wittmann)
> Support property expansion in CLI command files
> -----------------------------------------------
>
> Key: SRAMP-212
> URL: https://issues.jboss.org/browse/SRAMP-212
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Shell
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> Currently the CLI (sramp shell) supports the ability to pass it a file containing a list of commands to execute. This should be enhanced to support property expansion (standard Ant format), which would allow for more powerful/useful operation when integrating with e.g. Ant.
--
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
10 years, 9 months
[JBoss JIRA] (SRAMP-384) Add validation for password in overlord commons installer
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-384?page=com.atlassian.jira.plugin.... ]
Eric Wittmann reassigned SRAMP-384:
-----------------------------------
Assignee: David virgil naranjo (was: Eric Wittmann)
> Add validation for password in overlord commons installer
> ---------------------------------------------------------
>
> Key: SRAMP-384
> URL: https://issues.jboss.org/browse/SRAMP-384
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: David virgil naranjo
> Fix For: 0.5.0 - API Management
>
>
> Currently the overlord commons installer is responsible for doing all security related work. This includes creating the overlord 'admin' user and configured a password for this user. The installer prompts the user for this password and then passes whatever the user entered to the JBoss EAP add-user utility. This utility will fail if the password does not meet certain standards. However, the utility fails without failing the overall install.
> The installer should do its own validation of the password entered by the user so that this silent failure doesn't happen. Also note that the password input and validation should happen before anything else security related gets installed.
--
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
10 years, 9 months
[JBoss JIRA] (RTGOV-406) Update Karaf samples sla report to access activity store
by Gary Brown (JIRA)
Gary Brown created RTGOV-406:
--------------------------------
Summary: Update Karaf samples sla report to access activity store
Key: RTGOV-406
URL: https://issues.jboss.org/browse/RTGOV-406
Project: RTGov (Run Time Governance)
Issue Type: Sub-task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.M1
Reports are now supported, but the SLA report sample needed to be simplified as it was based on using the JPA version of Activity Store.
Once JPA ActivityStore supported in Karaf, then the full example could be added back in.
--
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
10 years, 9 months