May 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-113. ------------------------------- > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 - JBPM6 Integration > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-113. --------------------------------- Resolution: Done We're not doing anything with the contentHash right now. This task was about forging relationships across document artifacts. We need another issue to address skipping adding of artifacts with identical content. > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 - JBPM6 Integration > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-113) Improve WSDL derivation to find references to other artifacts

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-113?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-113: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/252 > Improve WSDL derivation to find references to other artifacts > ------------------------------------------------------------- > > Key: SRAMP-113 > URL: https://issues.jboss.org/browse/SRAMP-113 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 - JBPM6 Integration > > > Currently the WSDL deriver will set up the derived relationships, but it won't resolve relationships to artifacts external to the original (source) wsdl document artifact. We need to be able to set up relationships across multiple wsdls and schemas. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-60) Remove Overlord icon and reduce header height when used with common headrer

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/GADGETS-60?page=com.atlassian.jira.plugin... ] Gary Brown reassigned GADGETS-60: --------------------------------- Assignee: Eric Wittmann (was: Jeff Yu) > Remove Overlord icon and reduce header height when used with common headrer > --------------------------------------------------------------------------- > > Key: GADGETS-60 > URL: https://issues.jboss.org/browse/GADGETS-60 > Project: Gadget Server and Gadgets > Issue Type: Task > Reporter: Gary Brown > Assignee: Eric Wittmann > Fix For: 1.0.0.M5 > > > Currently when the overlord-common header is added, with the existing gs header, it uses up too much space at the top of the page. > Eric suggested it would be possible to remove the icon and that region reduced in height so it only contains the 'widget store' link. > Also see whether changing the side and current gs backgrounds to a grey might help it blend better with the commons header. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-60) Remove Overlord icon and reduce header height when used with common headrer

by Gary Brown (JIRA)

Gary Brown created GADGETS-60: --------------------------------- Summary: Remove Overlord icon and reduce header height when used with common headrer Key: GADGETS-60 URL: https://issues.jboss.org/browse/GADGETS-60 Project: Gadget Server and Gadgets Issue Type: Task Reporter: Gary Brown Assignee: Jeff Yu Fix For: 1.0.0.M5 Currently when the overlord-common header is added, with the existing gs header, it uses up too much space at the top of the page. Eric suggested it would be possible to remove the icon and that region reduced in height so it only contains the 'widget store' link. Also see whether changing the side and current gs backgrounds to a grey might help it blend better with the commons header. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-199) Wsdl and Xsd Derivers are not setting up import/include relationships

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-199: ----------------------------------- Summary: 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: Eric Wittmann Fix For: 0.3.1 - jBPM - bugfix 1 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-198) Deploy Demos/CLI

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-198?page=com.atlassian.jira.plugin.... ] Eric Wittmann reassigned SRAMP-198: ----------------------------------- Assignee: Eric Wittmann (was: Kurt Stam) > Deploy Demos/CLI > ---------------- > > Key: SRAMP-198 > URL: https://issues.jboss.org/browse/SRAMP-198 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.1.1 - Workflow Demo > Reporter: Nick Cross > Assignee: Eric Wittmann > Fix For: 0.3.0 - JBPM6 Integration > > > Currently the S-RAMP-Distro zips are not deployed. Either make them deployable or allow the CLI/Demos to be deployed in Maven. This would allow productisation to pick up the components. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-198) Deploy Demos/CLI

by Nick Cross (JIRA)

Nick Cross created SRAMP-198: -------------------------------- Summary: Deploy Demos/CLI Key: SRAMP-198 URL: https://issues.jboss.org/browse/SRAMP-198 Project: S-RAMP Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Distro Affects Versions: 0.1.1 - Workflow Demo Reporter: Nick Cross Assignee: Kurt Stam Fix For: 0.3.0 - JBPM6 Integration Currently the S-RAMP-Distro zips are not deployed. Either make them deployable or allow the CLI/Demos to be deployed in Maven. This would allow productisation to pick up the components. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-206) Document Link context type

by Gary Brown (JIRA)

Gary Brown created RTGOV-206: -------------------------------- Summary: Document Link context type Key: RTGOV-206 URL: https://issues.jboss.org/browse/RTGOV-206 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.Final Need to update docs to describe the Link context type with timeframe value, and also the information processor config. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-198) Update information processor config to support 'timeframe' value for use with Link context

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-198?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-198. ------------------------------ Resolution: Done > Update information processor config to support 'timeframe' value for use with Link context > ------------------------------------------------------------------------------------------ > > Key: RTGOV-198 > URL: https://issues.jboss.org/browse/RTGOV-198 > Project: RTGov (Run Time Governance) > Issue Type: Enhancement > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.Final > > > When creating a Link context type, using the information processor, we also need to be able to set the timeframe value. Will just be ignored if the context type is not Link, although validation could also be updated to check it is either there or not, depending upon the type. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2013