[jira] [Created] (AXIOM-387) Deprecate getChildrenWithName and introduce a replacement method
Deprecate getChildrenWithName and introduce a replacement method Key: AXIOM-387 URL: https://issues.apache.org/jira/browse/AXIOM-387 Project: Axiom Issue Type: Task Components: API Reporter: Andreas Veithen Priority: Minor The behavior of OMElement#getChildrenWithName is somewhat ill defined for QNames without namespace. In earlier Axiom versions, for such QNames, the returned iterator would only match the local name and return child elements with any namespace. This was changed in r522259, but the legacy behavior was later restored by AXIOM-11 to avoid breaking existing code. However, this legacy behavior is only supported by LLOM. DOOM always uses strict QName matching. It should also be noted that none of this is properly documented in the Javadoc of the getChildrenWithName method. To enable us to eventually get rid of this legacy code, we should (1) deprecate OMElement#getChildrenWithName (2) introduce a replacement method (getChildrenWithQName) with a well defined behavior (i.e. that always uses strict QName matching) (3) update the documentation to recommend users to migrate to getChildrenWithQName or getChildrenWithLocalName depending on the use case -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
Re: [jira] [Created] (XMLRPC-185) Library dependency
The authoritative source for dependencies is http://ws.apache.org/xmlrpc/dependencies.html On Fri, Apr 15, 2011 at 12:20 PM, Zafar Khaydarov (JIRA) j...@apache.org wrote: Library dependency -- Key: XMLRPC-185 URL: https://issues.apache.org/jira/browse/XMLRPC-185 Project: XML-RPC Issue Type: Improvement Components: Releases, Source, Website Affects Versions: 3.1.4 Environment: JRE 1.6 Eclipse Windows 7 Reporter: Zafar Khaydarov Hello, Thanks a lot for the library first of all. But! Somebody should update the web site as the latest version of the library depend on the old httpclient (2.0). The documentation about dependencies refers to Not Found (http://jakarta.apache.org/commons/httpclient/) Also in tutorials you should explicitly mention about the dependencies on HttpComponents (which refers to the old version). If there is an opportunity, I could help in this improvement. thanx. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org -- Capitalism is the astounding belief that the most wickedest of men will do the most wickedest of things for the greatest good of everyone. John Maynard Keynes (http://en.wikiquote.org/wiki/Keynes) https://linuxcounter.net/user/221257.html - To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
[jira] [Created] (AXIOM-388) Add methods to OMElement that allow calculating the namespace context of an element
Add methods to OMElement that allow calculating the namespace context of an element --- Key: AXIOM-388 URL: https://issues.apache.org/jira/browse/AXIOM-388 Project: Axiom Issue Type: New Feature Components: API Reporter: Andreas Veithen There are a couple of things that the average Java developer is unable to code correctly. One of these things is calculating the namespace context of an element in an XML document. Examples: (1) The following change in Axis2 attempts to resolve an issue where the databinding fails to resolve a QName value if the prefix is declared on the SOAP envelope: http://svn.apache.org/viewvc?view=revisionrevision=398161 Strictly speaking this change is incorrect because it only takes into account namespaces declared on the soap:Envelope, but not on the soap:Body. (2) The following change in Synapse adds code to compile an XPath expression retrieved from an XML configuration document: http://svn.apache.org/viewvc/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/mediators/Value.java?view=diffr1=1080144r2=1080145pathrev=1080145 To build the namespace context for the XPath expression, the code uses OMElement#getAllDeclaredNamespaces() on the element that has the attribute the XPath expression is extracted from. That is incorrect because namespaces relevant for the interpretation of the XPath expression may also be declared on ancestors of this element. (3) RAMPART-40 introduces code that attempts to build a namespace context by scanning the entire document tree for namespace declarations (!). To avoid these issues and to make life easier for developers, Axiom should define high level methods that allow to calculate the namespace context of a given element. There should be actually two methods: * One that returns an iterator over all namespace declarations in scope. This method could be used e.g. to initialize the namespace context of an XPath expression. * One that returns a NamespaceContext object that can be used with other XML APIs that support this interface. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
Build failed in Jenkins: woden-trunk #286
See https://builds.apache.org/job/woden-trunk/286/ -- [...truncated 692 lines...] Running org.apache.woden.wsdl20.xml.NameAttributeTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.woden.wsdl20.xml.EndpointElementTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.153 sec Running org.apache.woden.wsdl20.xml.DocumentationElementTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.woden.wsdl20.BindingFaultReferenceTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.woden.wsdl20.EndpointTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.woden.wsdl20.xml.IncludeElementTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.woden.internal.wsdl20.assertions.TestInterface1009 Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running org.apache.woden.wsdl20.xml.BindingFaultReferenceElementTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.woden.wsdl20.extensions.ExtensionRegistryTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.woden.wsdl20.BindingFaultTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.woden.wsdl20.xml.InterfaceOperationElementTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.woden.wsdl20.xml.InterfaceFaultReferenceElementTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.woden.WSDLFactoryTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.woden.wsdl20.InterfaceFaultTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.woden.wsdl20.xml.InterfaceMessageReferenceElementTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running org.apache.woden.wsdl20.xml.BindingMessageReferenceElementTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.woden.wsdl20.xml.TypesElementTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.woden.wsdl20.xml.DescriptiontElementTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.woden.xml.TokenAttrTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.woden.wsdl20.ServiceTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.woden.wsdl20.xml.ImportElementTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.woden.wsdl20.xml.ServiceElementTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running org.apache.woden.wsdl20.extensions.http.HTTPLocationTest Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running org.apache.woden.wsdl20.fragids.FragmentIdentificationTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 sec Running org.apache.woden.wsdl20.InterfaceFaultReferenceTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.woden.wsdl20.xml.InterfaceElementTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running testcase.resolver.schemaloc.SchemaLocationTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec Running org.apache.woden.wsdl20.BindingTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.woden.wsdl20.xml.BindingElementTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Results : Tests run: 238, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-jar-plugin:2.3:jar (default-jar) @ woden-tests-impl-om --- [INFO] Building jar: https://builds.apache.org/job/woden-trunk/ws/woden/woden-tests/target/om/woden-tests-impl-om-1.0-SNAPSHOT.jar [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 7.340s [INFO] Finished at: Mon Sep 05 19:21:46 UTC 2011 [INFO] Final Memory: 9M/312M [INFO] [INFO] ...SUCCESS. [INFO] --- Execution Summary: Builds Passing: 1 Builds Failing: 0 --- [INFO] [INFO] Installing https://builds.apache.org/job/woden-trunk/ws/woden/woden-tests/pom.xml to https://builds.apache.org/job/woden-trunk/ws/.repository/org/apache/woden/woden-tests/1.0-SNAPSHOT/woden-tests-1.0-SNAPSHOT.pom [INFO] ---
Jenkins build is back to normal : woden-trunk #287
See https://builds.apache.org/job/woden-trunk/287/ - To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org
