August 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (OVERLORD-142) Not all required overlord properties are created if file already exists in fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-142?page=com.atlassian.jira.plug... ] Gary Brown resolved OVERLORD-142. --------------------------------- Resolution: Done > Not all required overlord properties are created if file already exists in fuse > ------------------------------------------------------------------------------- > > Key: OVERLORD-142 > URL: https://issues.jboss.org/browse/OVERLORD-142 > Project: Overlord > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.8.Final > > > The properties: > overlord.auth.saml-key-alias=overlord > overlord.auth.saml-keystore=${sys\:karaf.home}/etc/overlord-saml.keystore > are not created by the overlord:generatesamlkeystore command if the file already exists. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-142) Not all required overlord properties are created if file already exists in fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-142?page=com.atlassian.jira.plug... ] Gary Brown updated OVERLORD-142: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/103 > Not all required overlord properties are created if file already exists in fuse > ------------------------------------------------------------------------------- > > Key: OVERLORD-142 > URL: https://issues.jboss.org/browse/OVERLORD-142 > Project: Overlord > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.8.Final > > > The properties: > overlord.auth.saml-key-alias=overlord > overlord.auth.saml-keystore=${sys\:karaf.home}/etc/overlord-saml.keystore > are not created by the overlord:generatesamlkeystore command if the file already exists. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plug... ] David virgil naranjo updated OVERLORD-140: ------------------------------------------ Git Pull Request: https://github.com/Governance/dtgov/pull/218, https://github.com/Governance/rtgov/pull/193 (was: https://github.com/Governance/dtgov/pull/218) > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > <link rel="icon" type="image/png" href="images/favicon.png"></link> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-140) Ensure consistent fav icon for all overlord apps

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-140?page=com.atlassian.jira.plug... ] David virgil naranjo updated OVERLORD-140: ------------------------------------------ Git Pull Request: https://github.com/Governance/dtgov/pull/218 > Ensure consistent fav icon for all overlord apps > ------------------------------------------------ > > Key: OVERLORD-140 > URL: https://issues.jboss.org/browse/OVERLORD-140 > Project: Overlord > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > Ensure that all UI apps (s-ramp, dtgov, rtgov) share a common favicon. Presumably we should use the overlord icon currently included in overlord-commons-uiheader. This can be accomplished by simply including this markup in the gwt host page: > {code} > <link rel="icon" type="image/png" href="images/favicon.png"></link> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-142) Not all required overlord properties are created if file already exists in fuse

by Gary Brown (JIRA)

Gary Brown created OVERLORD-142: ----------------------------------- Summary: Not all required overlord properties are created if file already exists in fuse Key: OVERLORD-142 URL: https://issues.jboss.org/browse/OVERLORD-142 Project: Overlord Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: Overlord-Commons-2.0.8.Final The properties: overlord.auth.saml-key-alias=overlord overlord.auth.saml-keystore=${sys\:karaf.home}/etc/overlord-saml.keystore are not created by the overlord:generatesamlkeystore command if the file already exists. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-552) Support relationships with no target

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-552: --------------------------------- Summary: Support relationships with no target Key: SRAMP-552 URL: https://issues.jboss.org/browse/SRAMP-552 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer 2.1.2 "It is possible for a relationship of a given Relationship Type not to have a target, which is termed a "relationship with no targets". In this case there is only one relationship instance with that Relationship Type for a given Source. Such relationships have a target cardinality of "0". If there is a relationship instance with a given Relationship Type that does have a target, then there CANNOT also be a relationship instance with that Relationship Type which has no target." Currently, this causes: {code} Caused by: javax.jcr.PathNotFoundException: No item exists at path sramp:relationshipType relative to /s-ramp/artifacts/4a/97/7b/bd-ab9b-4f00-b7b5-25f62f04eb45/sramp-relationships:null in workspace "default" at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:346) at org.modeshape.jcr.AbstractJcrNode.getProperty(AbstractJcrNode.java:108) at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.updateGenericRelationships(ArtifactToJCRNodeVisitor.java:267) at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visitBase(ArtifactToJCRNodeVisitor.java:128) at org.overlord.sramp.common.visitors.HierarchicalArtifactVisitorAdapter.visit(HierarchicalArtifactVisitorAdapter.java:209) at org.overlord.sramp.repository.jcr.mapper.ArtifactToJCRNodeVisitor.visit(ArtifactToJCRNodeVisitor.java:310) at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.overlord.sramp.common.visitors.ArtifactVisitorHelper.visitArtifact(ArtifactVisitorHelper.java:41) at org.overlord.sramp.repository.jcr.JCRArtifactPersister.persistArtifactPhase1(JCRArtifactPersister.java:138) at org.overlord.sramp.repository.jcr.JCRPersistence.persistArtifact(JCRPersistence.java:177) ... 47 more {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-551) Generic relationship types cannot match derived/modeled relationship types

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-551: --------------------------------- Summary: Generic relationship types cannot match derived/modeled relationship types Key: SRAMP-551 URL: https://issues.jboss.org/browse/SRAMP-551 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer Generic relationship types cannot match the built-in derived/modeled relationship types -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-547) Support built-in relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-547?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-547: ------------------------------ Description: WsdlDocument, XsdDocument, etc. do not currently include support for importedXsds, includedXsds, redefinedXsds, importedWsdls, etc. (was: WsdlLinker does not include support for: {code} protected List<XsdDocumentTarget> importedXsds; protected List<XsdDocumentTarget> includedXsds; protected List<XsdDocumentTarget> redefinedXsds; protected List<WsdlDocumentTarget> importedWsdls; {code}) > Support built-in relationships > ------------------------------ > > Key: SRAMP-547 > URL: https://issues.jboss.org/browse/SRAMP-547 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > WsdlDocument, XsdDocument, etc. do not currently include support for importedXsds, includedXsds, redefinedXsds, importedWsdls, etc. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-547) Support built-in relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-547?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-547: ------------------------------ Summary: Support built-in relationships (was: Support built-in WsdlDocument relationships) > Support built-in relationships > ------------------------------ > > Key: SRAMP-547 > URL: https://issues.jboss.org/browse/SRAMP-547 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > WsdlLinker does not include support for: > {code} > protected List<XsdDocumentTarget> importedXsds; > protected List<XsdDocumentTarget> includedXsds; > protected List<XsdDocumentTarget> redefinedXsds; > protected List<WsdlDocumentTarget> importedWsdls; > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-89) Create Policy derived artifact handler

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-89?page=com.atlassian.jira.plugin.s... ] Brett Meyer commented on SRAMP-89: ---------------------------------- Needs to derive from policy files themselves, as well as attachments within a WSDL. Example: {code} <wsdl:binding ...> ... <wsp:Policy> <wsp:PolicyReference URI="policy:policy.xml"/> </wsp:Policy> ... </wsdl:binding> {code} > Create Policy derived artifact handler > -------------------------------------- > > Key: SRAMP-89 > URL: https://issues.jboss.org/browse/SRAMP-89 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.6.0 > > > Create the handler that will produce the Derived Artifacts for ws-policy artifacts. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues August 2014