September 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-230) ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-230?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-230. --------------------------------- Resolution: Done > ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext > ---------------------------------------------------------------------------------- > > Key: SRAMP-230 > URL: https://issues.jboss.org/browse/SRAMP-230 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.4.0 - API Management > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > While writing a custom {{AbstractXmlDeriver}}, I needed to register a namespace discovered during the processing of the XML file (i.e., during the {{derive}} method). The only way I could figure out how to do this was to cache the instance of the {{StaticNamespaceContext}} passed into the {{configureNamespaceMappings}} method. Then, when the {{derive}} method is called I could register namespaces with the namespace context. It would be nice to have a getter for the namespace context for subclasses to use. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-233) Check for null logger in s-ramp wagon

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-233?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-233: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/314 > Check for null logger in s-ramp wagon > ------------------------------------- > > Key: SRAMP-233 > URL: https://issues.jboss.org/browse/SRAMP-233 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > In certain use cases the wagon will not be injected with the logger. Make sure to check for null before using it. Once that is done, remove the SrampWagonProxy class from dtgov. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-232) Custom Properties Do Not Render Correctly In The Safari Browser

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-232?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-232: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/314 > Custom Properties Do Not Render Correctly In The Safari Browser > --------------------------------------------------------------- > > Key: SRAMP-232 > URL: https://issues.jboss.org/browse/SRAMP-232 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.4.0 - API Management > Environment: OS X 10.8.4, Safari 6.0.5 > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > Attachments: customProperties.png > > > The custom properties of artifacts are displaying on the same line and wrapping when necessary. So for instance, properties x, y, and z, with values 1, 2, and 3 respectfully could display in these 2 different ways (depending on window size): > a: 1b: 2c: 3|Add Property| > or > a: 1b: 2c: > 3|Add Property| > I did not see this problem using the Chrome browser. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-230) ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-230?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-230: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/314 > ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext > ---------------------------------------------------------------------------------- > > Key: SRAMP-230 > URL: https://issues.jboss.org/browse/SRAMP-230 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.4.0 - API Management > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > While writing a custom {{AbstractXmlDeriver}}, I needed to register a namespace discovered during the processing of the XML file (i.e., during the {{derive}} method). The only way I could figure out how to do this was to cache the instance of the {{StaticNamespaceContext}} passed into the {{configureNamespaceMappings}} method. Then, when the {{derive}} method is called I could register namespaces with the namespace context. It would be nice to have a getter for the namespace context for subclasses to use. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-232) Custom Properties Do Not Render Correctly In The Safari Browser

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-232?page=com.atlassian.jira.plugin.... ] Work on SRAMP-232 started by Eric Wittmann. > Custom Properties Do Not Render Correctly In The Safari Browser > --------------------------------------------------------------- > > Key: SRAMP-232 > URL: https://issues.jboss.org/browse/SRAMP-232 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.4.0 - API Management > Environment: OS X 10.8.4, Safari 6.0.5 > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > Attachments: customProperties.png > > > The custom properties of artifacts are displaying on the same line and wrapping when necessary. So for instance, properties x, y, and z, with values 1, 2, and 3 respectfully could display in these 2 different ways (depending on window size): > a: 1b: 2c: 3|Add Property| > or > a: 1b: 2c: > 3|Add Property| > I did not see this problem using the Chrome browser. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-230) ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-230?page=com.atlassian.jira.plugin.... ] Work on SRAMP-230 stopped by Eric Wittmann. > ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext > ---------------------------------------------------------------------------------- > > Key: SRAMP-230 > URL: https://issues.jboss.org/browse/SRAMP-230 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.4.0 - API Management > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > While writing a custom {{AbstractXmlDeriver}}, I needed to register a namespace discovered during the processing of the XML file (i.e., during the {{derive}} method). The only way I could figure out how to do this was to cache the instance of the {{StaticNamespaceContext}} passed into the {{configureNamespaceMappings}} method. Then, when the {{derive}} method is called I could register namespaces with the namespace context. It would be nice to have a getter for the namespace context for subclasses to use. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-230) ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-230?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-230: ------------------------------------- Note: the intent of the deriver is for it to be stateless and lightweight. So it's not a good idea to hang on to the namespace context in any case. Instead, the approach to fixing this issue is to create a XmlDeriverContext that will get passed around. This object will have the root element and XPath objects. Additionally, it will have a "addNamespaceMapping" method to solve the above problem. > ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext > ---------------------------------------------------------------------------------- > > Key: SRAMP-230 > URL: https://issues.jboss.org/browse/SRAMP-230 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.4.0 - API Management > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > While writing a custom {{AbstractXmlDeriver}}, I needed to register a namespace discovered during the processing of the XML file (i.e., during the {{derive}} method). The only way I could figure out how to do this was to cache the instance of the {{StaticNamespaceContext}} passed into the {{configureNamespaceMappings}} method. Then, when the {{derive}} method is called I could register namespaces with the namespace context. It would be nice to have a getter for the namespace context for subclasses to use. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-230) ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-230?page=com.atlassian.jira.plugin.... ] Work on SRAMP-230 started by Eric Wittmann. > ArtifactDeriver Subclasses Should Have Direct Access To The StaticNamespaceContext > ---------------------------------------------------------------------------------- > > Key: SRAMP-230 > URL: https://issues.jboss.org/browse/SRAMP-230 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.4.0 - API Management > Reporter: Dan Florian > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > While writing a custom {{AbstractXmlDeriver}}, I needed to register a namespace discovered during the processing of the XML file (i.e., during the {{derive}} method). The only way I could figure out how to do this was to cache the instance of the {{StaticNamespaceContext}} passed into the {{configureNamespaceMappings}} method. Then, when the {{derive}} method is called I could register namespaces with the namespace context. It would be nice to have a getter for the namespace context for subclasses to use. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-233) Check for null logger in s-ramp wagon

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-233?page=com.atlassian.jira.plugin.... ] Work on SRAMP-233 stopped by Eric Wittmann. > Check for null logger in s-ramp wagon > ------------------------------------- > > Key: SRAMP-233 > URL: https://issues.jboss.org/browse/SRAMP-233 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > In certain use cases the wagon will not be injected with the logger. Make sure to check for null before using it. Once that is done, remove the SrampWagonProxy class from dtgov. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-233) Check for null logger in s-ramp wagon

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-233?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-233: ------------------------------------- Correction - I am going to leave the SrampWagonProxy in dtgov because I actually still want to inject a logger into the wagon. > Check for null logger in s-ramp wagon > ------------------------------------- > > Key: SRAMP-233 > URL: https://issues.jboss.org/browse/SRAMP-233 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Client > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > In certain use cases the wagon will not be injected with the logger. Make sure to check for null before using it. Once that is done, remove the SrampWagonProxy class from dtgov. -- 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

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues September 2013