[Axiom] Axiom 1.0 RC3 Release
Hi all, We uploaded Axiom 1.0 RC3 release artifacts to following locations. Please help us by downloading and reviewing them. Download locations : * binary and source distributions - http://people.apache.org/~chinthaka/axiom/1.0-RC3/ * jars- http://people.apache.org/~chinthaka/maven/ws-commons/jars/ This release is mainly due to the latest addition of OMDataSource in to Axiom interfaces. Axiom 1.0 will be released soon. (Please note that these releases do not include xdocs but will be available with 1.0 release as usual.) Thanks, Axiom Team signature.asc Description: OpenPGP digital signature
Re: Axis 1.3 on port 80 (not 8080)
In Apache, you need to direct the urls for the axis services to go to mod_jk. Just see how it's done for your other servlets. The relevant file is /etc/httpd/conf.d/jk.conf (and possibly also in /etc/httpd/conf/httpd.conf, and /etc/httpd/conf.d/ssl.conf if you're passing https urls to Tomcat also. Jeff On 4/23/06, Simon McMahon <[EMAIL PROTECTED]> wrote: > > Thanks but those changes are already in place - i.e. mod_jk - because I have > other servlets that already run on port 80. > When I install Axis into that Tomcat configuration Axis still appears to > need port 8080. > > Any idea where I should look to troubleshoot this? What config files etc? > > Cheers, > > Simon. >
Re: Axis 1.3 on port 80 (not 8080)
Thanks but those changes are already in place - i.e. mod_jk - because I have other servlets that already run on port 80. When I install Axis into that Tomcat configuration Axis still appears to need port 8080. Any idea where I should look to troubleshoot this? What config files etc? Cheers, Simon. Simon McMahon Work: (07) 31311420Mobile: (043) 2294180>>> [EMAIL PROTECTED] 04/24/06 11:56am >>>You just need to configure you app server (ie Tomcat) to run on port 80, or even integrate web server Apache with Tomcat using mod_jk.That's it! On 4/23/06, Simon McMahon <[EMAIL PROTECTED]> wrote: Hi, Axis is working great for me. Thanks! Now that I am trying to deploy it our firewall people are asking "why do we have to open port 8080 - blah blah blah ?". To avoid this argument with them I thought I would check if Axis can run on port 80? Please advise if this is possible? I run Apache 1.2.34, Tomcat 4.1.31, Axis 1.3. All on Windows XP. We also run SSL on port 443 for the https. Actually 443 appears to be the only port open on our firewall at the moment. Cheers, Simon. Simon McMahon Work: (07) 31311420Mobile: (043) 2294180*This email, including any attachments sent with it, isconfidential and for the sole use of the intended recipient(s).This confidentiality is not waived or lost, if you receive it andyou are not the intended recipient(s), or if it is transmitted/received in error.Any unauthorised use, alteration, disclosure, distribution orreview of this email is strictly prohibited. The informationcontained in this email, including any attachment sent withit, may be subject to a statutory duty of confidentiality if itrelates to health service matters.If you are not the intended recipient(s), or if you havereceived this email in error, you are asked to immediatelynotify the sender by telephone collect on Australia+61 1800 198 175 or by return email. You should alsodelete this email, and any copies, from your computersystem network and destroy any hard copies produced.If not an intended recipient of this email, you must not copy,distribute or take any action(s) that relies on it; any form ofdisclosure, modification, distribution and/or publication of thisemail is also prohibited.Although Queensland Health takes all reasonable steps toensure this email does not contain malicious software,Queensland Health does not accept responsibility for theconsequences if any person's computer inadvertently suffersany disruption to services, loss of information, harm or isinfected with a virus, other malicious computer programme orcode that may occur as a consequence of receiving thisemail.Unless stated otherwise, this email represents only the viewsof the sender and not the views of the Queensland Government.
Re: Axis 1.3 on port 80 (not 8080)
You just need to configure you app server (ie Tomcat) to run on port 80, or even integrate web server Apache with Tomcat using mod_jk.That's it!On 4/23/06, Simon McMahon <[EMAIL PROTECTED]> wrote: Hi, Axis is working great for me. Thanks! Now that I am trying to deploy it our firewall people are asking "why do we have to open port 8080 - blah blah blah ?". To avoid this argument with them I thought I would check if Axis can run on port 80? Please advise if this is possible? I run Apache 1.2.34, Tomcat 4.1.31, Axis 1.3. All on Windows XP. We also run SSL on port 443 for the https. Actually 443 appears to be the only port open on our firewall at the moment. Cheers, Simon. Simon McMahon Work: (07) 31311420Mobile: (043) 2294180 * This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government.
Re: Axis 1.3 in 64 bit server
I've seen no problems. Axis's thread's lifecycle is managed by your servlet container, running on a JavaVM. If you are seeing unstable behavior, I think those are the places to look, not Axis. But it sounds like you are encountering network problems (response is slow, sometimes even no response?). Maybe that's a place to start looking at. Regards, Dies faizul sulaiman wrote: Hi, Do Axis 1.3 support 64 bit machine? I'm using the Axis 1.3 to build a web services on my 32 bit pc and its working. When I deploy the same service into a 64 bit server the service is not running properly. The processes are quite slow and unstable. Sometimes, it not returning any output but no error from axis. Is there any suggestion for this? Or anyone who have experience on using axis on 64 bit server. - Mohd Faizul Sulaiman -
Axis 1.3 on port 80 (not 8080)
Hi, Axis is working great for me. Thanks! Now that I am trying to deploy it our firewall people are asking "why do we have to open port 8080 - blah blah blah ?". To avoid this argument with them I thought I would check if Axis can run on port 80? Please advise if this is possible? I run Apache 1.2.34, Tomcat 4.1.31, Axis 1.3. All on Windows XP. We also run SSL on port 443 for the https. Actually 443 appears to be the only port open on our firewall at the moment. Cheers, Simon. Simon McMahon Work: (07) 31311420Mobile: (043) 2294180 * This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone collect on Australia +61 1800 198 175 or by return email. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although Queensland Health takes all reasonable steps to ensure this email does not contain malicious software, Queensland Health does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government.
Axis 1.3 in 64 bit server
Hi, Do Axis 1.3 support 64 bit machine? I'm using the Axis 1.3 to build a web services on my 32 bit pc and its working. When I deploy the same service into a 64 bit server the service is not running properly. The processes are quite slow and unstable. Sometimes, it not returning any output but no error from axis. Is there any suggestion for this? Or anyone who have experience on using axis on 64 bit server. - Mohd Faizul Sulaiman -
Axis2 1.0 RC1 Weblogic 9.1 installation problem
H Developesi, I am trying to install Axis2 1.0 RC1 war on weblogic 9.1 through it console as war file. Installation seems sucessful but I am unable to see Any service (default version.aar) or module deployed (default addressing-SNAPSHOT.mar). Even I cann't deployed any services. Does Weblogic is able to understand Axis2 service archive (.aar) and modules (.mar) files. Did anybody got sucess using Axis2 and Wblogic 9.1 Thanks Gopal -- View this message in context: http://www.nabble.com/Axis2-1.0-RC1-Weblogic-9.1-installation-problem-t1495632.html#a4053735 Sent from the Axis - User forum at Nabble.com.
WSRF/MUSE client
Hi all, I am building a client which is designed to invoke custom operations of WSRF services. I generated a SOAP message and I am having a problem when I'm sending it to the server. The service I created has an operation called 'create' which has one input parameter of string type (which is represented by XmlBeans document since I'm using the WSRF/MUSE ANT build). I would really appreciate it if someone will go though the WSDL and SOAP files and see if there is anything wrong with the SOAP message I generated or whether it is a bug in the WSRF/MUSE infrastructure. Attached is the SOAP, the WSDL, and the log I get from the Tomcat. Thanks in advance, Asaf Lahav VP R&D, Prima Grid LTD. Cellular: 972-54-4717955 Phone: 972-3-6540255 Fax: 972-3-6540254 http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:fs="http://www.primagrid.com/test/one/testservice"; xmlns:wsrp="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";> http://localhost:8080/muse/services/ServicesAdmin http://www.primagrid.com/test/one/testservice/ServicesAdminPortType/Create 1 1 http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="http://www.primagrid.com/test/one/testservice"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:wsrp="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"; xmlns:wsrpw="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.wsdl"; xmlns:wsrlw="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.wsdl"; xmlns:wsntw="http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-01.wsdl"; xmlns:muws-p2-wsdl="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.wsdl"; xmlns:mex="http://schemas.xmlsoap.org/ws/2004/09/mex"; xmlns:wsa04="http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:ns="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part1.xsd"; xmlns:ns1="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.xsd"; xmlns:ns2="http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-01.xsd"; xmlns:ns3="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd"; xmlns:ns4="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.xsd"; xmlns:ns5="http://schemas.xmlsoap.org/ws/2003/03/addressing"; targetNamespace="http://www.primagrid.com/test/one/testservice"; name="MyDefinition"> http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.wsdl"; location="../spec/wsrf/WS-ResourceProperties-1_2-Draft_01.wsdl"/> http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.wsdl"; location="../spec/wsrf/WS-ResourceLifetime-1_2-Draft_01.wsdl"/> http://schemas.xmlsoap.org/ws/2004/09/mex"; location="../spec/wsx/WS-MetadataExchange-2004_09.wsdl"/> http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-01.wsdl"; location="../spec/wsn/WS-BaseNotification-1_2-Draft_01.wsdl"/> http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.wsdl"; location="../spec/wsdm/MUWS-Part2-1_0.wsdl"/> http://www.primagrid.com/test/one/testservice"; xmlns="http://www.w3.org/2001/XMLSchema"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:wsrl="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.xsd"; xmlns:wsbf="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd"; xmlns:wsnt="http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-01.xsd"; xmlns:muws-p1-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part1.xsd"; xmlns:muws-p2-xs="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.xsd";> http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd"; schemaLocation="../spec/wsrf/WS-BaseFaults-1_2-Draft_01.xsd"/> http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceLifetime-1.2-draft-01.xsd"; schemaLocation="../spec/wsrf/WS-ResourceLifetime-1_2-Draft_01.xsd"/> http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft-01.xsd"; schemaLocation="../spec/wsn/WS-BaseNotification-1_2-Draft_01.xsd"/> http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part1.xsd"; schemaLocation="../spec/wsdm/MUWS-Part1-1_0.xsd"/> http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.xsd"; schemaLocation="../spec/wsdm/MUWS-Part2-1_0.xsd"/>
Re: Starting a new project..
More questions to add: - what are the advantages of using axis2 over axis1? - what are the risks and benefits of each version? On 4/23/06, Larry Meadors <[EMAIL PROTECTED]> wrote: > ..and want to know if I should use axis1 or axis2. > > The target date for completion is about 8 weeks out. > > I need these to be secure (both in terms of authentication and > authorization), and I see that both Axis and Axis2 use WSS4J (the > WS-Security specification's implementation for Java), so it looks like > either way, I can do that. Any issues with using one version over the > other? > > I am almost a blank slate at this point (I have done one other web > service a year or so ago with axis1), and looking for advice to help > get off on the right foot. :-) > > Larry >
Starting a new project..
..and want to know if I should use axis1 or axis2. The target date for completion is about 8 weeks out. I need these to be secure (both in terms of authentication and authorization), and I see that both Axis and Axis2 use WSS4J (the WS-Security specification's implementation for Java), so it looks like either way, I can do that. Any issues with using one version over the other? I am almost a blank slate at this point (I have done one other web service a year or so ago with axis1), and looking for advice to help get off on the right foot. :-) Larry
guru' s help ! wsdl2java doesn't generate wsdl file in the "MIME Binding Schema"
guru' s help !
wsdl2java doesn't generate wsdl file in the "MIME Binding Schema" ( http://www.w3.org/TR/wsdl.html#A4.4 )
I wann't to get wsdl in the format according to the shema: http://schemas.xmlsoap.org/wsdl/mime/
for example axis/samples/swa/ has the following format file swa.wsdl:
...
here is the binding part:
...
http://schemas.xmlsoap.org/soap/http"/
>
...
but when i execute java2wsdl tool on my code:
...
public interface Storage extends java.rmi.Remote { public storage.core.axis.Product getProduct(java.lang.String in0) throws java.rmi.RemoteException; public storage.core.axis.Product[] getProducts() throws
java.rmi.RemoteException; public java.lang.String getImage(java.lang.String in0, javax.mail.internet.MimeMultipart in1) throws java.rmi.RemoteException; public javax.mail.internet.MimeMultipart getImage2(java.lang.String
in0, float[] in1) throws java.rmi.RemoteException;}
...
I got following wsdl without following http://schemas.xmlsoap.org/wsdl/mime/ shema
...
...
http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:storageProduct"/>
http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:storageProduct"/>
I wan't to axis java2wsdl tool to do it . or some another tool? I mean I want tag to be generated.
please help me to do it. thank you .
[Axis2] Axis2 1.0 RC2 release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I uploaded Axis2 1.0 RC2 release artifacts. Please help us by downloading and reviewing them. Download locations : * binary and source distributions - http://people.apache.org/~deepal/axis2/1.0-RC2/ * jars http://people.apache.org/~deepal/maven/ws/axis2/jars/ * mars (addressing and security) http://people.apache.org/~deepal/maven/ws/axis2/mars/ According to the release plan, I'm expecting to release Axis2 1.0 on 1st May, 2006. Please note that these releases do not include xdocs but will be available with 1.0 release as usual. Thanks, Deepal -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFES3ezjOGcXNDx0CARAn6DAJ4nVlDHJwWkBL7tEdi00YJChGTBPQCgmYFk JQWmxsnKN5uJkXgaWnSxSEM= =UdlC -END PGP SIGNATURE-
