[jira] Commented: (AXIS2-3044) Cannot generate code giving a remote HTTP URI, when the client is behind an HTTP proxy server
[ https://issues.apache.org/jira/browse/AXIS2-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517951 ] Afkham Azeez commented on AXIS2-3044: - Dims, At the moment something like; ./wsdl2java.sh -Dhttp.proxyHost=abc.com -Dhttp.proxyPort= is not possible. I need to edit the wsdl2java.sh file to provide these System properties. Something like the following will be acceptable; ./wsdl2java.sh --http-proxy-host=abc.com --http.proxy-port= or ./wsdl2java.sh -Dhttp.proxyHost=abc.com -Dhttp.proxyPort= > Cannot generate code giving a remote HTTP URI, when the client is behind an > HTTP proxy server > - > > Key: AXIS2-3044 > URL: https://issues.apache.org/jira/browse/AXIS2-3044 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen >Reporter: Afkham Azeez >Assignee: Amila Chinthaka Suriarachchi >Priority: Critical > > We should provide a options to wsdl2java such as; > http-proxy-host & http-proxy-port to facilitate this. > At the moment, users behind a proxy server cannot codegen for remote WSDLs > exposed via HTTP. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3044) Cannot generate code giving a remote HTTP URI, when the client is behind an HTTP proxy server
Cannot generate code giving a remote HTTP URI, when the client is behind an HTTP proxy server - Key: AXIS2-3044 URL: https://issues.apache.org/jira/browse/AXIS2-3044 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: codegen Reporter: Afkham Azeez Assignee: Amila Chinthaka Suriarachchi Priority: Critical Fix For: nightly We should provide a options to wsdl2java such as; http-proxy-host & http-proxy-port to facilitate this. At the moment, users behind a proxy server cannot codegen for remote WSDLs exposed via HTTP. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2703) Global phases after Dispatch are ignored
[ https://issues.apache.org/jira/browse/AXIS2-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498638 ] Afkham Azeez commented on AXIS2-2703: - The correct link is to the origianl issue is https://wso2.org/jira/browse/WSAS-244 > Global phases after Dispatch are ignored > > > Key: AXIS2-2703 > URL: https://issues.apache.org/jira/browse/AXIS2-2703 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Glen Daniels > Assigned To: Glen Daniels > Fix For: 1.3 > > > As noted by Afkham in http://www.wso2.org/jira/browse/WSAS-244, we aren't > currently respecting any phases deployed in axis2.xml after Dispatch. This > is because in the last line of DispatchPhase.checkPostConditions(), we > *overwrite* the ExecutionChain in the MessageContext with the one we get from > the operation. We should be *merging* the operation specific stuff with the > original version. In other words, if we had the following EC: > Phase1[ h1, h2 ], Dispatch[h3], Phase2[], Phase3[h4] > ...and an operation which put handler "h5" into Phase2, we should end up with: > Phase1[ h1, h2 ], Dispatch[h3], Phase2[h5], Phase3[h4] > after dispatching, with the execution point at Phase2. In particular h4 > should still be invoked. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1956) SAAJ 1.3 implementation
[ https://issues.apache.org/jira/browse/AXIS2-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467238 ] Afkham Azeez commented on AXIS2-1956: - Applied the latest patches from Sumedha > SAAJ 1.3 implementation > --- > > Key: AXIS2-1956 > URL: https://issues.apache.org/jira/browse/AXIS2-1956 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: modules > Environment: any >Reporter: sumedha rubasinghe > Attachments: attach.gif, attach.txt, attach.xml, saaj-1.3_09.01.07, > saaj-1.3_22.01.07.patch, saaj-1.3_24.01.07.patch, saaj-api-1.3_09.01.07, > saaj-api-1.3_22.01.07.patch > > > Two patches attached (for modules saaj & saaj-api) include part of saaj 1.3 > implementation. Integrated & tested this with latest source from trunk. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1591) WSDL2Java Appends the generated type classes
WSDL2Java Appends the generated type classes Key: AXIS2-1591 URL: http://issues.apache.org/jira/browse/AXIS2-1591 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.1 Environment: All OSs, JDK 14/15 Reporter: Afkham Azeez Assigned To: Ajith Harshana Ranabahu Priority: Critical Fix For: 1.1 When you process two or more WSDLs using a single WSDL2Java process, the type classes generated for earlier WSDLs get appended to those of the latter WSDLs. Most probably, this is because of using some static, cached or singleton structure within this tool. Say I process a.wsdl, b.wsdl & c.wsdl serially using the same WSDL2Java process. The types generated for b.wsdl will include those generated for a.wsdl, and the types geenrated for c.wsdl will contian those of a.wsdl & b.wsdl. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-1096) org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
[ http://issues.apache.org/jira/browse/AXIS2-1096?page=all ]
Afkham Azeez closed AXIS2-1096.
---
Fixed. Added this method to org.apache.axis2.saaj.SOAPElementImpl
> org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
>
>
> Key: AXIS2-1096
> URL: http://issues.apache.org/jira/browse/AXIS2-1096
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
>Reporter: David Illsley
> Assigned To: Afkham Azeez
>
> org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
> It is implemented in Axiom in org.apache.axiom.om.impl.dom.NodeImpl as:
> public NamedNodeMap getAttributes() {
> return null; // overridden in ElementImpl
> }
> However the axis2 saaj implementation (NodeImplEx, SOAPElementImpl) extends
> this class directly and does not override this method
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-1096) org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
[ http://issues.apache.org/jira/browse/AXIS2-1096?page=all ]
Afkham Azeez resolved AXIS2-1096.
-
Resolution: Fixed
Fixed. Added this method to org.apache.axis2.saaj.SOAPElementImpl
> org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
>
>
> Key: AXIS2-1096
> URL: http://issues.apache.org/jira/browse/AXIS2-1096
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
>Reporter: David Illsley
> Assigned To: Afkham Azeez
>
> org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
> It is implemented in Axiom in org.apache.axiom.om.impl.dom.NodeImpl as:
> public NamedNodeMap getAttributes() {
> return null; // overridden in ElementImpl
> }
> However the axis2 saaj implementation (NodeImplEx, SOAPElementImpl) extends
> this class directly and does not override this method
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1096) org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
[ http://issues.apache.org/jira/browse/AXIS2-1096?page=all ]
Afkham Azeez updated AXIS2-1096:
Assignee: Afkham Azeez
Fixed. add this method to org.apache.axis2.saaj.SOAPElementImpl
> org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
>
>
> Key: AXIS2-1096
> URL: http://issues.apache.org/jira/browse/AXIS2-1096
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
>Reporter: David Illsley
> Assigned To: Afkham Azeez
>
> org.apache.axis2.saaj.SOAPElementImpl.getAttributes returns null
> It is implemented in Axiom in org.apache.axiom.om.impl.dom.NodeImpl as:
> public NamedNodeMap getAttributes() {
> return null; // overridden in ElementImpl
> }
> However the axis2 saaj implementation (NodeImplEx, SOAPElementImpl) extends
> this class directly and does not override this method
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-1086) Service EPR calculation is carried out in the JSPs!
[ http://issues.apache.org/jira/browse/AXIS2-1086?page=comments#action_12430984 ] Afkham Azeez commented on AXIS2-1086: - Please note that this item is related to the listing of the service EPRs in the Axis2 management console > Service EPR calculation is carried out in the JSPs! > --- > > Key: AXIS2-1086 > URL: http://issues.apache.org/jira/browse/AXIS2-1086 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Afkham Azeez > Assigned To: Deepal Jayasinghe > > At present, the calculation of the service EPRs is done in the front end JSP, > using part of the request to this JSP, which obviously is wrong. All EPRs > cannot be computed this way. There should be a backend operation which will > provide all the EPRs of a given service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1086) Service EPR calculation is carried out in the JSPs!
Service EPR calculation is carried out in the JSPs! --- Key: AXIS2-1086 URL: http://issues.apache.org/jira/browse/AXIS2-1086 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.0 Reporter: Afkham Azeez Assigned To: Deepal Jayasinghe At present, the calculation of the service EPRs is done in the front end JSP, using part of the request to this JSP, which obviously is wrong. All EPRs cannot be computed this way. There should be a backend operation which will provide all the EPRs of a given service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1075) AxisService should have a getEPRs
AxisService should have a getEPRs - Key: AXIS2-1075 URL: http://issues.apache.org/jira/browse/AXIS2-1075 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: core Affects Versions: 1.0 Environment: All Reporter: Afkham Azeez Assigned To: Eran Chinthaka The AxisService class should contain a method; public String[] getEPRs(); This method will return all the EPRs of this service (should include REST EPRs, if the service is exposed via REST) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-127) SAAJ TCK compliance for Axis2 SAAJ implementation
[ http://issues.apache.org/jira/browse/AXIS2-127?page=all ] Afkham Azeez updated AXIS2-127: --- Attachment: saaj-tck.jpg 320 of the 324 tests in the SAAJ TCK test suite passed successfully. The remaining 4 tests failed due to issues with attachment handling. See attached screen shot. > SAAJ TCK compliance for Axis2 SAAJ implementation > - > > Key: AXIS2-127 > URL: http://issues.apache.org/jira/browse/AXIS2-127 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Ashutosh Shahi > Assignee: Afkham Azeez > Attachments: saaj-tck.jpg > > Run Axis2 SAAJ implementation again SAAJ TCK and provide all the missing > implementation. > Currently attachment support is missing in SAAJ implementation, complete that. > Ashutosh -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-127) SAAJ TCK compliance for Axis2 SAAJ implementation
[ http://issues.apache.org/jira/browse/AXIS2-127?page=all ] Afkham Azeez updated AXIS2-127: --- Attachment: (was: saaj-tck.jpg) > SAAJ TCK compliance for Axis2 SAAJ implementation > - > > Key: AXIS2-127 > URL: http://issues.apache.org/jira/browse/AXIS2-127 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Ashutosh Shahi > Assignee: Afkham Azeez > > Run Axis2 SAAJ implementation again SAAJ TCK and provide all the missing > implementation. > Currently attachment support is missing in SAAJ implementation, complete that. > Ashutosh -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-127) SAAJ TCK compliance for Axis2 SAAJ implementation
[ http://issues.apache.org/jira/browse/AXIS2-127?page=all ] Afkham Azeez updated AXIS2-127: --- Attachment: saaj-tck.jpg 320 of the 324 tests in the SAAJ TCK test suite passed successfully. The remaining 4 tests failed due to issues with attachment handling. See attached screen shot. > SAAJ TCK compliance for Axis2 SAAJ implementation > - > > Key: AXIS2-127 > URL: http://issues.apache.org/jira/browse/AXIS2-127 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Ashutosh Shahi > Assignee: Afkham Azeez > Attachments: saaj-tck.jpg > > Run Axis2 SAAJ implementation again SAAJ TCK and provide all the missing > implementation. > Currently attachment support is missing in SAAJ implementation, complete that. > Ashutosh -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-306) SAAJ over our DOM
[ http://issues.apache.org/jira/browse/AXIS2-306?page=all ] Afkham Azeez updated AXIS2-306: --- Attachment: axis2-19012006.patch Added a new dependency in the SAAJ project.xml. Please review and commit this patch. > SAAJ over our DOM > - > > Key: AXIS2-306 > URL: http://issues.apache.org/jira/browse/AXIS2-306 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Davanum Srinivas > Assignee: Afkham Azeez > Attachments: Echo.aar, axis.jpg, axis2-18012006.patch.tgz, > axis2-19012006.patch, axis2-doom.patch, axis2-doom.patch, saaj2-29122005.zip, > saaj2.patch, saaj2.patch > > Ruchith, > There are classes in our saaj package the implement org.w3c.dom.* stuff. we > need to make them EXTEND the dom impl classes. For example: > org.apache.axis2.saaj.NodeImpl implements org.w3c.dom.Node > we need to change it to > org.apache.axis2.saaj.NodeImpl extends > org.apache.axis2.om.impl.dom.NodeImpl implements org.w3c.dom.Node > Otherwise we will have 2 classes implementing the same methods from > org.w3c.dom.Node. > What do you think? > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-399) xdocs not XHTML compliant and internal links in maven generated site are broken
[ http://issues.apache.org/jira/browse/AXIS2-399?page=all ] Afkham Azeez updated AXIS2-399: --- Attachment: axis2-xdocs.patch.tgz I have changed the xdocs for the 0.94 release, which were not XHTML compliant to be XHTML compliant, and also fixed the issue of the broken internal links in the maven generated site. Please review and apply the patch attached. > xdocs not XHTML compliant and internal links in maven generated site are > broken > --- > > Key: AXIS2-399 > URL: http://issues.apache.org/jira/browse/AXIS2-399 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Environment: All > Reporter: Afkham Azeez > Assignee: Chatra Nakkawita > Attachments: axis2-xdocs.patch.tgz > > Some of the xdocs are not XHTML compliant, and in the maven generated site, > most of the internal links(links within the page to itself) do not work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS2-399) xdocs not XHTML compliant and internal links in maven generated site are broken
xdocs not XHTML compliant and internal links in maven generated site are broken --- Key: AXIS2-399 URL: http://issues.apache.org/jira/browse/AXIS2-399 Project: Apache Axis 2.0 (Axis2) Type: Bug Environment: All Reporter: Afkham Azeez Assigned to: Chatra Nakkawita Some of the xdocs are not XHTML compliant, and in the maven generated site, most of the internal links(links within the page to itself) do not work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-306) SAAJ over our DOM
[ http://issues.apache.org/jira/browse/AXIS2-306?page=all ] Afkham Azeez updated AXIS2-306: --- Attachment: axis2-18012006.patch.tgz This patch contains the following 1. Fix for MTOM bug where the content type of all attachments were converted to application/octet-stream 2. SAAJ SOAPConnection complete implementaion 3. New integration test which sends a SOAPMessage with attachments to an Echo service, and receives back the response and validates it. With this patch, the SAAJ implementation for AXIS2 is complete, except that SAAJ TCK compliance has to be achieved. Current unit test code coverage of SAAJ, according to clover is 48.5%. Please apply this patch > SAAJ over our DOM > - > > Key: AXIS2-306 > URL: http://issues.apache.org/jira/browse/AXIS2-306 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Davanum Srinivas > Assignee: Afkham Azeez > Attachments: Echo.aar, axis.jpg, axis2-18012006.patch.tgz, axis2-doom.patch, > axis2-doom.patch, saaj2-29122005.zip, saaj2.patch, saaj2.patch > > Ruchith, > There are classes in our saaj package the implement org.w3c.dom.* stuff. we > need to make them EXTEND the dom impl classes. For example: > org.apache.axis2.saaj.NodeImpl implements org.w3c.dom.Node > we need to change it to > org.apache.axis2.saaj.NodeImpl extends > org.apache.axis2.om.impl.dom.NodeImpl implements org.w3c.dom.Node > Otherwise we will have 2 classes implementing the same methods from > org.w3c.dom.Node. > What do you think? > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-369) New AXIS2 Packaging Structure
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ] Afkham Azeez updated AXIS2-369: --- Attachment: axis2-11012005.patch.tgz Please apply the attached patch which handles some of the issues while testing the standard and minumum source ditros. > New AXIS2 Packaging Structure > - > > Key: AXIS2-369 > URL: http://issues.apache.org/jira/browse/AXIS2-369 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Versions: 0.94 > Reporter: Afkham Azeez > Assignee: Afkham Azeez > Fix For: 0.94 > Attachments: axis2-10012005.patch, axis2-11012005.patch.tgz, axis2.patch, > axis2.patch > > New AXIS2 Packaging structure for standard & minimal source and binary > releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-369) New AXIS2 Packaging Structure
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ] Afkham Azeez updated AXIS2-369: --- Comment: was deleted > New AXIS2 Packaging Structure > - > > Key: AXIS2-369 > URL: http://issues.apache.org/jira/browse/AXIS2-369 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Versions: 0.94 > Reporter: Afkham Azeez > Assignee: Afkham Azeez > Fix For: 0.94 > Attachments: axis2-10012005.patch, axis2.patch, axis2.patch > > New AXIS2 Packaging structure for standard & minimal source and binary > releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-369) New AXIS2 Packaging Structure
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ] Afkham Azeez updated AXIS2-369: --- Attachment: (was: axis2.patch) > New AXIS2 Packaging Structure > - > > Key: AXIS2-369 > URL: http://issues.apache.org/jira/browse/AXIS2-369 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Versions: 0.94 > Reporter: Afkham Azeez > Assignee: Afkham Azeez > Fix For: 0.94 > Attachments: axis2.patch, axis2.patch > > New AXIS2 Packaging structure for standard & minimal source and binary > releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-369) New AXIS2 Packaging Structure
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ] Afkham Azeez updated AXIS2-369: --- Attachment: axis2.patch Reattaching patch with license granted to ASF > New AXIS2 Packaging Structure > - > > Key: AXIS2-369 > URL: http://issues.apache.org/jira/browse/AXIS2-369 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Versions: 0.94 > Reporter: Afkham Azeez > Assignee: Afkham Azeez > Fix For: 0.94 > Attachments: axis2.patch, axis2.patch > > New AXIS2 Packaging structure for standard & minimal source and binary > releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-369) New AXIS2 Packaging Structure
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ] Afkham Azeez updated AXIS2-369: --- Attachment: (was: axis2.patch) > New AXIS2 Packaging Structure > - > > Key: AXIS2-369 > URL: http://issues.apache.org/jira/browse/AXIS2-369 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Versions: 0.94 > Reporter: Afkham Azeez > Assignee: Afkham Azeez > Fix For: 0.94 > Attachments: axis2.patch, axis2.patch > > New AXIS2 Packaging structure for standard & minimal source and binary > releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-369) New AXIS2 Packaging Structure
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ] Afkham Azeez updated AXIS2-369: --- Attachment: axis2.patch Reuploading patch with license granted to ASF > New AXIS2 Packaging Structure > - > > Key: AXIS2-369 > URL: http://issues.apache.org/jira/browse/AXIS2-369 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Versions: 0.94 > Reporter: Afkham Azeez > Assignee: Afkham Azeez > Fix For: 0.94 > Attachments: axis2.patch, axis2.patch > > New AXIS2 Packaging structure for standard & minimal source and binary > releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-369) New AXIS2 Packaging Structure
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ] Afkham Azeez updated AXIS2-369: --- Attachment: axis2.patch Patch attached. Modified maven.xml to properly fetch dependencies for std and min distros, and also to reflect the proper std binary ditribution. > New AXIS2 Packaging Structure > - > > Key: AXIS2-369 > URL: http://issues.apache.org/jira/browse/AXIS2-369 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Versions: 0.94 > Reporter: Afkham Azeez > Assignee: Afkham Azeez > Fix For: 0.94 > Attachments: axis2.patch, axis2.patch > > New AXIS2 Packaging structure for standard & minimal source and binary > releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (AXIS2-369) New AXIS2 Packaging Structure
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ] Afkham Azeez reopened AXIS2-369: Assign To: Afkham Azeez (was: Eran Chinthaka) More updates to be carried out on this issue > New AXIS2 Packaging Structure > - > > Key: AXIS2-369 > URL: http://issues.apache.org/jira/browse/AXIS2-369 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Versions: 0.94 > Reporter: Afkham Azeez > Assignee: Afkham Azeez > Fix For: 0.94 > Attachments: axis2.patch > > New AXIS2 Packaging structure for standard & minimal source and binary > releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-369) New AXIS2 Packaging Structure
[ http://issues.apache.org/jira/browse/AXIS2-369?page=all ] Afkham Azeez updated AXIS2-369: --- Attachment: axis2.patch Please apply the attached patch for the new packaging structure. > New AXIS2 Packaging Structure > - > > Key: AXIS2-369 > URL: http://issues.apache.org/jira/browse/AXIS2-369 > Project: Apache Axis 2.0 (Axis2) > Type: New Feature > Components: deployment > Versions: 0.94 > Reporter: Afkham Azeez > Assignee: Eran Chinthaka > Attachments: axis2.patch > > New AXIS2 Packaging structure for standard & minimal source and binary > releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS2-369) New AXIS2 Packaging Structure
New AXIS2 Packaging Structure - Key: AXIS2-369 URL: http://issues.apache.org/jira/browse/AXIS2-369 Project: Apache Axis 2.0 (Axis2) Type: New Feature Components: deployment Versions: 0.94 Reporter: Afkham Azeez Assigned to: Eran Chinthaka New AXIS2 Packaging structure for standard & minimal source and binary releases, docs releas and WAR release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-306) SAAJ over our DOM
[ http://issues.apache.org/jira/browse/AXIS2-306?page=all ] Afkham Azeez updated AXIS2-306: --- Attachment: saaj2-29122005.zip Echo.aar Pls apply the attached patch to apply saaj2.patch to https://svn.apache.org/repos/asf/webservices/axis2/trunk/archive/java/scratch/ruchith_dims/saaj2 and commit the attached Echo.aar file under test-resources The following issues need to be addressed in order to complete this implementation 1. SOAPFaults are not getting serialized. A SOAPFault causes an infinite loop within the org.apache.axis2.soap.impl.dom.SOAPFaultImpl#getChildWithName(String childName) method, during seialization 2. Call does not work with DOOM > SAAJ over our DOM > - > > Key: AXIS2-306 > URL: http://issues.apache.org/jira/browse/AXIS2-306 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Davanum Srinivas > Assignee: Ruchith Udayanga Fernando > Attachments: Echo.aar, axis.jpg, axis2-doom.patch, axis2-doom.patch, > saaj2-29122005.zip, saaj2.patch, saaj2.patch > > Ruchith, > There are classes in our saaj package the implement org.w3c.dom.* stuff. we > need to make them EXTEND the dom impl classes. For example: > org.apache.axis2.saaj.NodeImpl implements org.w3c.dom.Node > we need to change it to > org.apache.axis2.saaj.NodeImpl extends > org.apache.axis2.om.impl.dom.NodeImpl implements org.w3c.dom.Node > Otherwise we will have 2 classes implementing the same methods from > org.w3c.dom.Node. > What do you think? > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-306) SAAJ over our DOM
[ http://issues.apache.org/jira/browse/AXIS2-306?page=all ] Afkham Azeez updated AXIS2-306: --- Attachment: axis2-doom.patch saaj2.patch Here is another patch for SAAJ over DOOM. apply saaj2.patch to https://svn.apache.org/repos/asf/webservices/axis2/trunk/archive/java/scratch/ruchith_dims/saaj2 apply axis2-doom.patch to https://svn.apache.org/repos/asf/webservices/axis2/trunk/java > SAAJ over our DOM > - > > Key: AXIS2-306 > URL: http://issues.apache.org/jira/browse/AXIS2-306 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Davanum Srinivas > Assignee: Ruchith Udayanga Fernando > Attachments: axis.jpg, axis2-doom.patch, axis2-doom.patch, saaj2.patch, > saaj2.patch > > Ruchith, > There are classes in our saaj package the implement org.w3c.dom.* stuff. we > need to make them EXTEND the dom impl classes. For example: > org.apache.axis2.saaj.NodeImpl implements org.w3c.dom.Node > we need to change it to > org.apache.axis2.saaj.NodeImpl extends > org.apache.axis2.om.impl.dom.NodeImpl implements org.w3c.dom.Node > Otherwise we will have 2 classes implementing the same methods from > org.w3c.dom.Node. > What do you think? > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-306) SAAJ over our DOM
[ http://issues.apache.org/jira/browse/AXIS2-306?page=comments#action_12361164 ] Afkham Azeez commented on AXIS2-306: SAAJ over DOOM is currently work-in.progress. Please apply the attached patches to the following repositories: apply saaj2.patch to https://svn.apache.org/repos/asf/webservices/axis2/trunk/archive/java/scratch/ruchith_dims/saaj2 apply axis2-doom.patch to https://svn.apache.org/repos/asf/webservices/axis2/trunk/java The attached image should go into test-resources directory in saaj2 > SAAJ over our DOM > - > > Key: AXIS2-306 > URL: http://issues.apache.org/jira/browse/AXIS2-306 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Davanum Srinivas > Assignee: Ruchith Udayanga Fernando > Attachments: axis.jpg, axis2-doom.patch, saaj2.patch > > Ruchith, > There are classes in our saaj package the implement org.w3c.dom.* stuff. we > need to make them EXTEND the dom impl classes. For example: > org.apache.axis2.saaj.NodeImpl implements org.w3c.dom.Node > we need to change it to > org.apache.axis2.saaj.NodeImpl extends > org.apache.axis2.om.impl.dom.NodeImpl implements org.w3c.dom.Node > Otherwise we will have 2 classes implementing the same methods from > org.w3c.dom.Node. > What do you think? > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-306) SAAJ over our DOM
[ http://issues.apache.org/jira/browse/AXIS2-306?page=all ] Afkham Azeez updated AXIS2-306: --- Attachment: axis.jpg saaj2.patch axis2-doom.patch > SAAJ over our DOM > - > > Key: AXIS2-306 > URL: http://issues.apache.org/jira/browse/AXIS2-306 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Reporter: Davanum Srinivas > Assignee: Ruchith Udayanga Fernando > Attachments: axis.jpg, axis2-doom.patch, saaj2.patch > > Ruchith, > There are classes in our saaj package the implement org.w3c.dom.* stuff. we > need to make them EXTEND the dom impl classes. For example: > org.apache.axis2.saaj.NodeImpl implements org.w3c.dom.Node > we need to change it to > org.apache.axis2.saaj.NodeImpl extends > org.apache.axis2.om.impl.dom.NodeImpl implements org.w3c.dom.Node > Otherwise we will have 2 classes implementing the same methods from > org.w3c.dom.Node. > What do you think? > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS2-336) Using the Admin Console, cannot redeploy a service after reuploading
Using the Admin Console, cannot redeploy a service after reuploading Key: AXIS2-336 URL: http://issues.apache.org/jira/browse/AXIS2-336 Project: Apache Axis 2.0 (Axis2) Type: Improvement Versions: 0.93, 0.94 Reporter: Afkham Azeez Priority: Minor Uploaded an AAR file, say abc.aar, and after a few changes to the service, created the abc.aar once again and tried to upload it. The modified service(s) do not get deployed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS2-335) AXIS service still available after undeploying using the Administration console
AXIS service still available after undeploying using the Administration console --- Key: AXIS2-335 URL: http://issues.apache.org/jira/browse/AXIS2-335 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: Tools Versions: 0.93, 0.94 Reporter: Afkham Azeez Undeployed an AXIS service using the Undeploy axisService link in the Admin Console. Still, the client was able to connect to this service, and the service was still being listed under available services. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS2-334) In the admininstration console, HTTP 500 after logged in administrator's session expires
In the admininstration console, HTTP 500 after logged in administrator's session expires Key: AXIS2-334 URL: http://issues.apache.org/jira/browse/AXIS2-334 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: Tools Versions: 0.93, 0.94 Reporter: Afkham Azeez In the Adminstration console, clicked the Administration link, and after logging in, left the page open until the HTTP session has expired. Now, if we click on any of the administration links, a critical error on the server occurs and an HTTP status 500 is returned. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AXIS2-333) Non blocking dual client does not receive an error when an invalid service is specified in the target EPR
Non blocking dual client does not receive an error when an invalid service is
specified in the target EPR
-
Key: AXIS2-333
URL: http://issues.apache.org/jira/browse/AXIS2-333
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: client-api
Versions: 0.93, 0.94
Reporter: Afkham Azeez
Tried to run the EchoNonBlockingClient example from the AXIS2 User Guide, and
provided an invalid service name as part of the target EPR. The public void
reportError(Exception e) method of the specified Callback object was not
called. Instead, the
while (!callback.isComplete()) {
Thread.sleep(1000);
}
loop was running infinitely.
However, when a correct service was specified, the same code works perfectly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
