You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Raghu Upadhyayula <ru...@responsys.com> on 2010/03/24 21:00:55 UTC
[Axis2] - Issue with soap:address locaiton in the WSDL ...
Hi,
My webservices is deployed under port 80, but when I see the WSDL in the browser, the soap:address location in the WSDL is showing port 8080.
My webservices url is http://localhost/webservices/services/MyService?wsdl & the soap:address location is displayed as <soap:address location="http://localhost:8080/webservices/services/MyService">
It used to display the soap:address location correctly, but suddenly from past couple of days it is displaying 8080 (I haven't changed anything in the webservices).
Does anyone know why the port number is displayed as 8080???
Thanks
Raghu
[cid:image001.gif@01CACB60.1742C070]<http://www.responsys.com/products>
Re: [Axis2] - Issue with soap:address locaiton in the WSDL ...
Posted by Andreas Veithen <an...@gmail.com>.
https://issues.apache.org/jira/browse/AXIS2-4465?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel
On Mon, Apr 19, 2010 at 19:48, Raghu Upadhyayula
<ru...@responsys.com> wrote:
> Andreas,
>
> Do you have the SVN diff's for the fix for AXIS2-4465 issue??
>
> Thanks
> Raghu
>
>
>
> -----Original Message-----
> From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
> Sent: Wednesday, March 24, 2010 3:10 PM
> To: java-user@axis.apache.org
> Subject: Re: [Axis2] - Issue with soap:address locaiton in the WSDL ...
>
> Could be caused by AXIS2-4465.
>
> Andreas
>
> On Wed, Mar 24, 2010 at 21:00, Raghu Upadhyayula
> <ru...@responsys.com> wrote:
>>
>> Hi,
>>
>> My webservices is deployed under port 80, but when I see the WSDL in the browser, the soap:address location in the WSDL is showing port 8080.
>>
>>
>>
>> My webservices url is http://localhost/webservices/services/MyService?wsdl & the soap:address location is displayed as <soap:address location="http://localhost:8080/webservices/services/MyService">
>>
>>
>>
>> It used to display the soap:address location correctly, but suddenly from past couple of days it is displaying 8080 (I haven't changed anything in the webservices).
>>
>>
>>
>> Does anyone know why the port number is displayed as 8080???
>>
>>
>>
>> Thanks
>>
>> Raghu
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
RE: [Axis2] - Issue with soap:address locaiton in the WSDL ...
Posted by Raghu Upadhyayula <ru...@responsys.com>.
Andreas,
Do you have the SVN diff's for the fix for AXIS2-4465 issue??
Thanks
Raghu
-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Sent: Wednesday, March 24, 2010 3:10 PM
To: java-user@axis.apache.org
Subject: Re: [Axis2] - Issue with soap:address locaiton in the WSDL ...
Could be caused by AXIS2-4465.
Andreas
On Wed, Mar 24, 2010 at 21:00, Raghu Upadhyayula
<ru...@responsys.com> wrote:
>
> Hi,
>
> My webservices is deployed under port 80, but when I see the WSDL in the browser, the soap:address location in the WSDL is showing port 8080.
>
>
>
> My webservices url is http://localhost/webservices/services/MyService?wsdl & the soap:address location is displayed as <soap:address location="http://localhost:8080/webservices/services/MyService">
>
>
>
> It used to display the soap:address location correctly, but suddenly from past couple of days it is displaying 8080 (I haven't changed anything in the webservices).
>
>
>
> Does anyone know why the port number is displayed as 8080???
>
>
>
> Thanks
>
> Raghu
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: [Axis2] - Issue with soap:address locaiton in the WSDL ...
Posted by Andreas Veithen <an...@gmail.com>.
Note that "suddenly" doesn't exist in the IT world. If the problem
occurs when moving from a server that exclusively uses HTTP to a
server that uses HTTPS, then it is definitely caused by AXIS2-4465.
Andreas
On Wed, Mar 24, 2010 at 21:42, Raghu Upadhyayula
<ru...@responsys.com> wrote:
> Andreas,
>
> I'm using Axis2 1.4 & it used to work correctly last week, but it is showing port 8080 since then. It is happening in our QA box which is using https.
>
> Thanks
> Raghu
>
>
> -----Original Message-----
> From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
> Sent: Wednesday, March 24, 2010 3:10 PM
> To: java-user@axis.apache.org
> Subject: Re: [Axis2] - Issue with soap:address locaiton in the WSDL ...
>
> Could be caused by AXIS2-4465.
>
> Andreas
>
> On Wed, Mar 24, 2010 at 21:00, Raghu Upadhyayula
> <ru...@responsys.com> wrote:
>>
>> Hi,
>>
>> My webservices is deployed under port 80, but when I see the WSDL in the browser, the soap:address location in the WSDL is showing port 8080.
>>
>>
>>
>> My webservices url is http://localhost/webservices/services/MyService?wsdl & the soap:address location is displayed as <soap:address location="http://localhost:8080/webservices/services/MyService">
>>
>>
>>
>> It used to display the soap:address location correctly, but suddenly from past couple of days it is displaying 8080 (I haven't changed anything in the webservices).
>>
>>
>>
>> Does anyone know why the port number is displayed as 8080???
>>
>>
>>
>> Thanks
>>
>> Raghu
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.4 to Axis 2
Posted by Demetris <de...@ece.neu.edu>.
Not a bad idea Martin thanks.
Martin Gainty wrote:
> Good Evening Demetris
>
> Axis1 is a servlet available in RPC and doc-literal styles
> Axis2 primarily for AARs (Service Archives) primarily for doc-literal
> style
>
> I would refactor by hand just to make sure you have firmer control
> over what is specific to the service
> and which code segments can be extracted to module mars
> (logging,security,addressing come to mind)
>
> HTH
> Martin Gainty
> ______________________________________________
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede
> unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig.
> Diese Nachricht dient lediglich dem Austausch von Informationen und
> entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten
> Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den
> Inhalt uebernehmen.
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
>
>
>
>
>
> > From: demetris@ece.neu.edu
> > To: java-user@axis.apache.org
> > Subject: Axis 1.4 to Axis 2
> > Date: Wed, 24 Mar 2010 16:55:30 -0400
> >
> > I am not sure but this may have been asked before. Is it possible for
> > an Axis 1.4 client to call an Axis 2 service and an Axis 2 client to
> > call an Axis 1.4 service? Is the SOÁP message carrying a different
> > content or is the version of supported soap different across these
> > versions? It would b nice if such a compatibility exists particularly
> > in cases were legacy services are not easy to get upgraded.
> >
> > Thanks
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-user-help@axis.apache.org
> >
>
> ------------------------------------------------------------------------
> Hotmail is redefining busy with tools for the New Busy. Get more from
> your inbox. Sign up now.
> <http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_2>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.4 to Axis 2
Posted by Demetris <de...@ece.neu.edu>.
Thanks Sanjiva
Sanjiva Weerawarana wrote:
> I think the question is about wire-level interop .. not code portability?
>
> Yes it should work.
>
> Sanjiva.
>
> On Thu, Mar 25, 2010 at 5:10 AM, Martin Gainty <mgainty@hotmail.com
> <ma...@hotmail.com>> wrote:
>
> Good Evening Demetris
>
> Axis1 is a servlet available in RPC and doc-literal styles
> Axis2 primarily for AARs (Service Archives) primarily for
> doc-literal style
>
> I would refactor by hand just to make sure you have firmer control
> over what is specific to the service
> and which code segments can be extracted to module mars
> (logging,security,addressing come to mind)
>
> HTH
> Martin Gainty
> ______________________________________________
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de
> confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede
> unbefugte Weiterleitung oder Fertigung einer Kopie ist
> unzulaessig. Diese Nachricht dient lediglich dem Austausch von
> Informationen und entfaltet keine rechtliche Bindungswirkung.
> Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir
> keine Haftung fuer den Inhalt uebernehmen.
>
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
>
>
>
>
>
>
> > From: demetris@ece.neu.edu <ma...@ece.neu.edu>
> > To: java-user@axis.apache.org <ma...@axis.apache.org>
> > Subject: Axis 1.4 to Axis 2
> > Date: Wed, 24 Mar 2010 16:55:30 -0400
>
> >
> > I am not sure but this may have been asked before. Is it
> possible for
> > an Axis 1.4 client to call an Axis 2 service and an Axis 2
> client to
> > call an Axis 1.4 service? Is the SOÁP message carrying a different
> > content or is the version of supported soap different across these
> > versions? It would b nice if such a compatibility exists
> particularly
> > in cases were legacy services are not easy to get upgraded.
> >
> > Thanks
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> <ma...@axis.apache.org>
> > For additional commands, e-mail: java-user-help@axis.apache.org
> <ma...@axis.apache.org>
> >
>
> ------------------------------------------------------------------------
> Hotmail is redefining busy with tools for the New Busy. Get more
> from your inbox. Sign up now.
> <http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_2>
>
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Director & Chief Scientist; Lanka Software Foundation;
> http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.4 to Axis 2
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
I think the question is about wire-level interop .. not code portability?
Yes it should work.
Sanjiva.
On Thu, Mar 25, 2010 at 5:10 AM, Martin Gainty <mg...@hotmail.com> wrote:
> Good Evening Demetris
>
> Axis1 is a servlet available in RPC and doc-literal styles
> Axis2 primarily for AARs (Service Archives) primarily for doc-literal style
>
> I would refactor by hand just to make sure you have firmer control over
> what is specific to the service
> and which code segments can be extracted to module mars
> (logging,security,addressing come to mind)
>
> HTH
> Martin Gainty
> ______________________________________________
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
>
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
>
>
>
>
>
>
> > From: demetris@ece.neu.edu
> > To: java-user@axis.apache.org
> > Subject: Axis 1.4 to Axis 2
> > Date: Wed, 24 Mar 2010 16:55:30 -0400
>
> >
> > I am not sure but this may have been asked before. Is it possible for
> > an Axis 1.4 client to call an Axis 2 service and an Axis 2 client to
> > call an Axis 1.4 service? Is the SOÁP message carrying a different
> > content or is the version of supported soap different across these
> > versions? It would b nice if such a compatibility exists particularly
> > in cases were legacy services are not easy to get upgraded.
> >
> > Thanks
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-user-help@axis.apache.org
> >
>
> ------------------------------
> Hotmail is redefining busy with tools for the New Busy. Get more from your
> inbox. Sign up now.<http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_2>
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Director & Chief Scientist; Lanka Software Foundation;
http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
RE: Axis 1.4 to Axis 2
Posted by Martin Gainty <mg...@hotmail.com>.
Good Evening Demetris
Axis1 is a servlet available in RPC and doc-literal styles
Axis2 primarily for AARs (Service Archives) primarily for doc-literal style
I would refactor by hand just to make sure you have firmer control over what is specific to the service
and which code segments can be extracted to module mars (logging,security,addressing come to mind)
HTH
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> From: demetris@ece.neu.edu
> To: java-user@axis.apache.org
> Subject: Axis 1.4 to Axis 2
> Date: Wed, 24 Mar 2010 16:55:30 -0400
>
> I am not sure but this may have been asked before. Is it possible for
> an Axis 1.4 client to call an Axis 2 service and an Axis 2 client to
> call an Axis 1.4 service? Is the SOÁP message carrying a different
> content or is the version of supported soap different across these
> versions? It would b nice if such a compatibility exists particularly
> in cases were legacy services are not easy to get upgraded.
>
> Thanks
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_2
Axis 1.4 to Axis 2
Posted by D G <de...@ece.neu.edu>.
I am not sure but this may have been asked before. Is it possible for
an Axis 1.4 client to call an Axis 2 service and an Axis 2 client to
call an Axis 1.4 service? Is the SOÁP message carrying a different
content or is the version of supported soap different across these
versions? It would b nice if such a compatibility exists particularly
in cases were legacy services are not easy to get upgraded.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
RE: [Axis2] - Issue with soap:address locaiton in the WSDL ...
Posted by Raghu Upadhyayula <ru...@responsys.com>.
Andreas,
I'm using Axis2 1.4 & it used to work correctly last week, but it is showing port 8080 since then. It is happening in our QA box which is using https.
Thanks
Raghu
-----Original Message-----
From: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Sent: Wednesday, March 24, 2010 3:10 PM
To: java-user@axis.apache.org
Subject: Re: [Axis2] - Issue with soap:address locaiton in the WSDL ...
Could be caused by AXIS2-4465.
Andreas
On Wed, Mar 24, 2010 at 21:00, Raghu Upadhyayula
<ru...@responsys.com> wrote:
>
> Hi,
>
> My webservices is deployed under port 80, but when I see the WSDL in the browser, the soap:address location in the WSDL is showing port 8080.
>
>
>
> My webservices url is http://localhost/webservices/services/MyService?wsdl & the soap:address location is displayed as <soap:address location="http://localhost:8080/webservices/services/MyService">
>
>
>
> It used to display the soap:address location correctly, but suddenly from past couple of days it is displaying 8080 (I haven't changed anything in the webservices).
>
>
>
> Does anyone know why the port number is displayed as 8080???
>
>
>
> Thanks
>
> Raghu
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: [Axis2] - Issue with soap:address locaiton in the WSDL ...
Posted by Andreas Veithen <an...@gmail.com>.
Could be caused by AXIS2-4465.
Andreas
On Wed, Mar 24, 2010 at 21:00, Raghu Upadhyayula
<ru...@responsys.com> wrote:
>
> Hi,
>
> My webservices is deployed under port 80, but when I see the WSDL in the browser, the soap:address location in the WSDL is showing port 8080.
>
>
>
> My webservices url is http://localhost/webservices/services/MyService?wsdl & the soap:address location is displayed as <soap:address location="http://localhost:8080/webservices/services/MyService">
>
>
>
> It used to display the soap:address location correctly, but suddenly from past couple of days it is displaying 8080 (I haven’t changed anything in the webservices).
>
>
>
> Does anyone know why the port number is displayed as 8080???
>
>
>
> Thanks
>
> Raghu
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
[Axis2] - Couple of questions about web services deployment using
Axis2.
Posted by Raghu Upadhyayula <ru...@responsys.com>.
Hi,
We are using Axis2 1.4 version. I have couple of questions about web services deployment using Axis2.
1. How do I deploy 2 different WSDL's pointing to the same endpoint in the same webapp (One WSDL is a subset of another WSDL)?
2. How do I deploy 2 different WSDL's pointing to different endpoints (basically 2 different services) in the same webapp?
I'm currently using the exploded deployment option for my webservices webapp.
Thanks
Raghu