March 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-170) Atom feeds do not work very well in exisiting clients

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-170?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-170: ---------------------------- Attachment: Screen Shot 2013-03-10 at 12.08.22 PM.png > Atom feeds do not work very well in exisiting clients > ----------------------------------------------------- > > Key: SRAMP-170 > URL: https://issues.jboss.org/browse/SRAMP-170 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Atom Binding > Affects Versions: 0.1.1 > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.2.0 - Milestone 4 > > Attachments: Screen Shot 2013-03-10 at 12.08.22 PM.png > > > When using exiting atom clients our feed don't work very well. I think one should be able to follow links down into an entry for example, but the link is not populated. We should investigate why this is. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-43) renaming the bam to rtgov in the gadgets.

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/GADGETS-43?page=com.atlassian.jira.plugin... ] Jeff Yu resolved GADGETS-43. ---------------------------- Resolution: Done > renaming the bam to rtgov in the gadgets. > ----------------------------------------- > > Key: GADGETS-43 > URL: https://issues.jboss.org/browse/GADGETS-43 > Project: Gadget Server and Gadgets > Issue Type: Task > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0.0.M4 > > > Due to the BAM renaming (renamed to rtgov), the rtgov related gadgets' url need to be changed accordingly. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-43) renaming the bam to rtgov in the gadgets.

by Jeff Yu (JIRA)

Jeff Yu created GADGETS-43: ------------------------------ Summary: renaming the bam to rtgov in the gadgets. Key: GADGETS-43 URL: https://issues.jboss.org/browse/GADGETS-43 Project: Gadget Server and Gadgets Issue Type: Task Reporter: Jeff Yu Assignee: Jeff Yu Fix For: 1.0.0.M4 Due to the BAM renaming (renamed to rtgov), the rtgov related gadgets' url need to be changed accordingly. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-42) creating documents with asciidoc

by Jeff Yu (JIRA)

[ https://issues.jboss.org/browse/GADGETS-42?page=com.atlassian.jira.plugin... ] Jeff Yu resolved GADGETS-42. ---------------------------- Fix Version/s: 1.0.0.M4 Resolution: Done > creating documents with asciidoc > -------------------------------- > > Key: GADGETS-42 > URL: https://issues.jboss.org/browse/GADGETS-42 > Project: Gadget Server and Gadgets > Issue Type: Feature Request > Reporter: Jeff Yu > Assignee: Jeff Yu > Fix For: 1.0.0.M4 > > > Creating the documents with asciidoc, and then build it to docbook for the html, pdf generation. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (GADGETS-42) creating documents with asciidoc

by Jeff Yu (JIRA)

Jeff Yu created GADGETS-42: ------------------------------ Summary: creating documents with asciidoc Key: GADGETS-42 URL: https://issues.jboss.org/browse/GADGETS-42 Project: Gadget Server and Gadgets Issue Type: Feature Request Reporter: Jeff Yu Assignee: Jeff Yu Creating the documents with asciidoc, and then build it to docbook for the html, pdf generation. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-141) Xpath evaluation of non-namspace aware nodes returning null result

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-141?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-141: ----------------------------- Fix Version/s: 1.0.0.M5 (was: 1.0.0.M4) > Xpath evaluation of non-namspace aware nodes returning null result > ------------------------------------------------------------------ > > Key: RTGOV-141 > URL: https://issues.jboss.org/browse/RTGOV-141 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > > When information processor applies an xpath evaluator to extract context and property information from a DOM node, where the node is not namespace aware, this results in a null value being returned. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-141) Xpath evaluation of non-namspace aware nodes returning null result

by Gary Brown (JIRA)

Gary Brown created RTGOV-141: -------------------------------- Summary: Xpath evaluation of non-namspace aware nodes returning null result Key: RTGOV-141 URL: https://issues.jboss.org/browse/RTGOV-141 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M4 When information processor applies an xpath evaluator to extract context and property information from a DOM node, where the node is not namespace aware, this results in a null value being returned. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-141) Xpath evaluation of non-namspace aware nodes returning null result

by Gary Brown (JIRA)

Gary Brown created RTGOV-141: -------------------------------- Summary: Xpath evaluation of non-namspace aware nodes returning null result Key: RTGOV-141 URL: https://issues.jboss.org/browse/RTGOV-141 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M4 When information processor applies an xpath evaluator to extract context and property information from a DOM node, where the node is not namespace aware, this results in a null value being returned. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-66) Synchronous activity event processing

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-66?page=com.atlassian.jira.plugin.s... ] Gary Brown updated RTGOV-66: ---------------------------- Fix Version/s: 1.0.0.M4 (was: 1.0.0.M5) > Synchronous activity event processing > ------------------------------------- > > Key: RTGOV-66 > URL: https://issues.jboss.org/browse/RTGOV-66 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M4 > > > The current policy enforcement example has two parts, the event evaluation using mvel to determine whether a customer should be suspended, and then an exchange handler configured in switchyard app to enforce the decision. > This is an asynchronous approach to enforcement that potential enables a customer to exceed their restrictions (albeit briefly) before the enforcement kicks in. > In situations where enforcement must apply immediately a policy has been broken, then we need a synchronous event evaluation to occur at the activity collector and potentially immediately affect the message exchange. > Need to consider: > - whether this mechanism should use a restricted form of the EPN as a way to make configuration consistent - although it would be dealing with derived ActivityType rather than an ActivityUnit at the top level, and interaction between nodes would also be synchronous, which may lead to ordering issues or configurations that would not be supported. > - what actions are required based on the decision made in a policy - for the customer suspended case it is likely to be just throwing an exception, but are there other actions? > Deployment of these sync policies should be equivalent to other components in the architecture. > Benefit of having a specific mechanism may be that it doesn't cause confusion with the full blown configuration, and also the fact that it is supposed to be returning a decision, rather than just propagating derived results. Not using the EPN may have benefits of not including its mechanics in the lightweight server configuration. > However we need to consider how it would interact with 'services' (e.g. cache) - possibly this could be a similar/same mechanism without having to use the whole EPN infrastructure. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-66) Synchronous activity event processing

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-66?page=com.atlassian.jira.plugin.s... ] Gary Brown resolved RTGOV-66. ----------------------------- Resolution: Done Finished implementing initial mechanism that allows a policy to block a business transaction by returning an exception. If other actions are required, these should be raised as an enhancement request. > Synchronous activity event processing > ------------------------------------- > > Key: RTGOV-66 > URL: https://issues.jboss.org/browse/RTGOV-66 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 1.0.0.M5 > > > The current policy enforcement example has two parts, the event evaluation using mvel to determine whether a customer should be suspended, and then an exchange handler configured in switchyard app to enforce the decision. > This is an asynchronous approach to enforcement that potential enables a customer to exceed their restrictions (albeit briefly) before the enforcement kicks in. > In situations where enforcement must apply immediately a policy has been broken, then we need a synchronous event evaluation to occur at the activity collector and potentially immediately affect the message exchange. > Need to consider: > - whether this mechanism should use a restricted form of the EPN as a way to make configuration consistent - although it would be dealing with derived ActivityType rather than an ActivityUnit at the top level, and interaction between nodes would also be synchronous, which may lead to ordering issues or configurations that would not be supported. > - what actions are required based on the decision made in a policy - for the customer suspended case it is likely to be just throwing an exception, but are there other actions? > Deployment of these sync policies should be equivalent to other components in the architecture. > Benefit of having a specific mechanism may be that it doesn't cause confusion with the full blown configuration, and also the fact that it is supposed to be returning a decision, rather than just propagating derived results. Not using the EPN may have benefits of not including its mechanics in the lightweight server configuration. > However we need to consider how it would interact with 'services' (e.g. cache) - possibly this could be a similar/same mechanism without having to use the whole EPN infrastructure. -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues March 2013