[JBoss JIRA] (GADGETS-54) UI changes due to service definition structure change.
by Jeff Yu (JIRA)
Jeff Yu created GADGETS-54:
------------------------------
Summary: UI changes due to service definition structure change.
Key: GADGETS-54
URL: https://issues.jboss.org/browse/GADGETS-54
Project: Gadget Server and Gadgets
Issue Type: Task
Reporter: Jeff Yu
Assignee: Jeff Yu
(1) The response time gadget's user preference will be based on interface and operation, instead of the 'service type' and 'operation'.
(2) The other response time gadget change is the text displayed per point on the chart - this should also maybe include the interface. Note that the serviceType field is now optional, as it may not be available for invocations of external services.
(3) Call trace details tab - again should display the interface aswell as (optional) service 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
13 years
[JBoss JIRA] (GADGETS-52) Duplicated guava.jar in the gadget-server.war
by Jeff Yu (JIRA)
[ https://issues.jboss.org/browse/GADGETS-52?page=com.atlassian.jira.plugin... ]
Jeff Yu resolved GADGETS-52.
----------------------------
Resolution: Done
> Duplicated guava.jar in the gadget-server.war
> ---------------------------------------------
>
> Key: GADGETS-52
> URL: https://issues.jboss.org/browse/GADGETS-52
> Project: Gadget Server and Gadgets
> Issue Type: Bug
> Affects Versions: 1.0.0.M4
> Reporter: Jeff Yu
> Assignee: Jeff Yu
> Fix For: 1.0.0.M5
>
> Attachments: GADGETS-52.patch
>
>
> Description of problem:
> There are two guava.jar causing problem of deployment of gadget-server.war.
> Noticed that it is not always reproduce to every machine.
> Already discussed with Jeff, it happens to some machine , well, not happens to other, which seems to me it happens randomely.
> But I think the duplicate guava.jar can be fixed. I tested that guava-11.0.2.jar would cause the problem below. Hopefully we can remove it.
--
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
13 years
[JBoss JIRA] (GADGETS-52) Duplicated guava.jar in the gadget-server.war
by Jeff Yu (JIRA)
[ https://issues.jboss.org/browse/GADGETS-52?page=com.atlassian.jira.plugin... ]
Jeff Yu updated GADGETS-52:
---------------------------
Attachment: GADGETS-52.patch
> Duplicated guava.jar in the gadget-server.war
> ---------------------------------------------
>
> Key: GADGETS-52
> URL: https://issues.jboss.org/browse/GADGETS-52
> Project: Gadget Server and Gadgets
> Issue Type: Bug
> Affects Versions: 1.0.0.M4
> Reporter: Jeff Yu
> Assignee: Jeff Yu
> Fix For: 1.0.0.M5
>
> Attachments: GADGETS-52.patch
>
>
> Description of problem:
> There are two guava.jar causing problem of deployment of gadget-server.war.
> Noticed that it is not always reproduce to every machine.
> Already discussed with Jeff, it happens to some machine , well, not happens to other, which seems to me it happens randomely.
> But I think the duplicate guava.jar can be fixed. I tested that guava-11.0.2.jar would cause the problem below. Hopefully we can remove it.
--
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
13 years
[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 resolved RTGOV-141.
------------------------------
Resolution: Done
Issue was the xpath expressions were fully qualified paths, from the root element of the document, but when switchyard supplied the information as a DOMSource, the contained node was not the top level element - it was still contained within the SOAPEnvelope and SOAPBody.
So if the path is fully qualified, and the node is not at the top level of the document, then it is imported into a new document at the top level.
> 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
13 years