You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by Alejandro Calbazana <al...@calbazana.com> on 2008/09/23 15:39:17 UTC
Proxy Question
Hello,
I'm investigating Synapse and would like to know if I can add services
to the ESB as proxied services and expose the service WSDL without
pulling a copy into a local registry. I have about 3 web services that
have complex WSDLs where multiple schema are imported. I'd rather not
manage copies of other WSDL as part of my ESB instance as they are
subject to change. I see that there have been some challenges with
importing these types of WSDL. Has this been addressed in the 1.7
release? I only see examples where WSDL is published as follows:
<publishWSDL uri="file:/repository/path/to/wsdl.wsdl"/>
Is it possible to say something like uri="http://path/to/wsdl.wsdl"?
Thanks!
Alejandro
Re: Proxy Question
Posted by indika kumara <in...@gmail.com>.
if mvn clean install -U will not work , you have to locally build rampart [1].
[1] http://ws.apache.org/rampart/source-repository.html
Thanks
Indika
On Thu, Sep 25, 2008 at 6:58 PM, Alejandro Calbazana
<al...@calbazana.com> wrote:
> Thanks Indika! I tried pulling the trunk, but it would not build for me. I
> get the following when mvn tries to resolve:
>
> Missing:
> ----------
> 1) org.apache.rampart:rampart-policy:jar:SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.rampart
> -DartifactId=rampart-policy -Dversion=SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.rampart
> -DartifactId=rampart-policy -Dversion=SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.apache.synapse:synapse-utils:bundle:SNAPSHOT
> 2) org.apache.rampart:rampart-policy:jar:SNAPSHOT
>
> 2) org.apache.rampart:rampart-trust:jar:SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.rampart
> -DartifactId=rampart-trust -Dversion=SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.rampart
> -DartifactId=rampart-trust -Dversion=SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.apache.synapse:synapse-utils:bundle:SNAPSHOT
> 2) org.apache.rampart:rampart-trust:jar:SNAPSHOT
>
> 3) org.apache.rampart:rampart-core:jar:SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.rampart
> -DartifactId=rampart-core -Dversion=SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.rampart
> -DartifactId=rampart-core -Dversion=SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.apache.synapse:synapse-utils:bundle:SNAPSHOT
> 2) org.apache.rampart:rampart-core:jar:SNAPSHOT
>
> 4) org.apache.rampart:rampart:mar:SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.rampart
> -DartifactId=rampart -Dversion=SNAPSHOT -Dpackaging=mar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=org.apache.rampart -DartifactId=rampart
> -Dversion=SNAPSHOT -Dpackaging=mar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
>
> Path to dependency:
> 1) org.apache.synapse:synapse-utils:bundle:SNAPSHOT
> 2) org.apache.rampart:rampart:mar:SNAPSHOT
>
> ----------
> 4 required artifacts are missing.
>
> for artifact:
> org.apache.synapse:synapse-utils:bundle:SNAPSHOT
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> wso2-m2 (http://dist.wso2.org/maven2/),
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
> apache-incubating
> (http://people.apache.org/repo/m2-incubating-repository/),
> apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository/)
>
>
> indika kumara wrote:
>>
>> Hi
>>
>> I have just tried this scenario, it works with a built from current
>> svn. It seems there were issues with previous releases as I am getting
>> same errors you have got, for 1.2 releases.
>> It seems https://issues.apache.org/jira/browse/SYNAPSE-442 has
>> resolved this issue.
>>
>> Could you try out this with a synapse SNAPSHOT?
>>
>> Thanks
>> Indika
>>
>>
>> On Wed, Sep 24, 2008 at 4:32 PM, Alejandro Calbazana
>> <al...@calbazana.com> wrote:
>>
>>>
>>> Hi Evanthika,
>>>
>>> I see that your wsdl fully qualifies the location of the schema import
>>> location. I am using Axis2 to host the service. When the service is
>>> built
>>> and deployed, the schemaLocation attribute is set to locate the schema
>>> relative to the service. So, Axis2 produces something along the
>>> following:
>>>
>>> <xs:import namespace="..." schemaLocation="ServiceName?xsd0=xsd0.xsd"/>
>>>
>>> As a result Synapse will try to resolve to the filesystem, relative to
>>> the
>>> base of the repository. So, while this works in your case, it may not
>>> work
>>> in other cases where the schemaLocation is defined as above.
>>>
>>> Thanks,
>>>
>>> Alejandro
>>>
>>> Evanthika Amarasiri wrote:
>>>
>>>>
>>>> Hi Alejandro,
>>>>
>>>> I was able to create a proxy service with the publishWSDL uri given as
>>>> an
>>>> http url. Also I have an XSD import within this WSDL where the xsd is
>>>> hosted
>>>> at a remote server.
>>>>
>>>> The location of the WSDL file -
>>>> http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl (As specified in
>>>> the
>>>> below configuration)
>>>> The location of the XSD file -
>>>> http://ww2.wso2.org/~evanthika/wsdl/import_schema.xsd (Refered in the
>>>> import_schema.wsdl file)
>>>>
>>>> Below is the configuration that I tried.
>>>>
>>>> <proxy name="TestProxyService" transports="https http"
>>>> startOnLoad="true">
>>>> <target>
>>>> <inSequence>
>>>> <send>
>>>> <endpoint>
>>>> <address
>>>> uri="http://localhost:9000/soap/SimpleStockQuoteService"/>
>>>> </endpoint>
>>>> </send>
>>>> </inSequence>
>>>> <outSequence>
>>>> <send/>
>>>> </outSequence>
>>>> </target>
>>>> <publishWSDL
>>>> uri="http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl"/>
>>>> </proxy>
>>>>
>>>> I was able to start the above configuration successfully. Can you check
>>>> your WSDL, XSD files and the configuration against mine and see whether
>>>> you
>>>> have properly created the files?
>>>>
>>>>
>>>> Thanks,
>>>> Evanthika
>>>>
>>>>
>>>> Asankha C. Perera wrote:
>>>>
>>>>>
>>>>> Alejandro
>>>>>
>>>>>>
>>>>>> Ah, I tried that once and it failed. I gave it a try again and took a
>>>>>> closer look at the logs. It looks like it cant resolve imported
>>>>>> schema
>>>>>> references.
>>>>>>
>>>>>
>>>>> This probably is a bug.. Evanthika can you check this and make that a
>>>>> test case for the releases?
>>>>>
>>>>> asankha
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>
Re: Proxy Question
Posted by Alejandro Calbazana <al...@calbazana.com>.
Thanks Indika! I tried pulling the trunk, but it would not build for
me. I get the following when mvn tries to resolve:
Missing:
----------
1) org.apache.rampart:rampart-policy:jar:SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.rampart
-DartifactId=rampart-policy -Dversion=SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.rampart
-DartifactId=rampart-policy -Dversion=SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.synapse:synapse-utils:bundle:SNAPSHOT
2) org.apache.rampart:rampart-policy:jar:SNAPSHOT
2) org.apache.rampart:rampart-trust:jar:SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.rampart
-DartifactId=rampart-trust -Dversion=SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.rampart
-DartifactId=rampart-trust -Dversion=SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.synapse:synapse-utils:bundle:SNAPSHOT
2) org.apache.rampart:rampart-trust:jar:SNAPSHOT
3) org.apache.rampart:rampart-core:jar:SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.rampart
-DartifactId=rampart-core -Dversion=SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.rampart
-DartifactId=rampart-core -Dversion=SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.synapse:synapse-utils:bundle:SNAPSHOT
2) org.apache.rampart:rampart-core:jar:SNAPSHOT
4) org.apache.rampart:rampart:mar:SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.rampart
-DartifactId=rampart -Dversion=SNAPSHOT -Dpackaging=mar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.rampart
-DartifactId=rampart -Dversion=SNAPSHOT -Dpackaging=mar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.synapse:synapse-utils:bundle:SNAPSHOT
2) org.apache.rampart:rampart:mar:SNAPSHOT
----------
4 required artifacts are missing.
for artifact:
org.apache.synapse:synapse-utils:bundle:SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
wso2-m2 (http://dist.wso2.org/maven2/),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
apache-incubating
(http://people.apache.org/repo/m2-incubating-repository/),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository/)
indika kumara wrote:
> Hi
>
> I have just tried this scenario, it works with a built from current
> svn. It seems there were issues with previous releases as I am getting
> same errors you have got, for 1.2 releases.
> It seems https://issues.apache.org/jira/browse/SYNAPSE-442 has
> resolved this issue.
>
> Could you try out this with a synapse SNAPSHOT?
>
> Thanks
> Indika
>
>
> On Wed, Sep 24, 2008 at 4:32 PM, Alejandro Calbazana
> <al...@calbazana.com> wrote:
>
>> Hi Evanthika,
>>
>> I see that your wsdl fully qualifies the location of the schema import
>> location. I am using Axis2 to host the service. When the service is built
>> and deployed, the schemaLocation attribute is set to locate the schema
>> relative to the service. So, Axis2 produces something along the following:
>>
>> <xs:import namespace="..." schemaLocation="ServiceName?xsd0=xsd0.xsd"/>
>>
>> As a result Synapse will try to resolve to the filesystem, relative to the
>> base of the repository. So, while this works in your case, it may not work
>> in other cases where the schemaLocation is defined as above.
>>
>> Thanks,
>>
>> Alejandro
>>
>> Evanthika Amarasiri wrote:
>>
>>> Hi Alejandro,
>>>
>>> I was able to create a proxy service with the publishWSDL uri given as an
>>> http url. Also I have an XSD import within this WSDL where the xsd is hosted
>>> at a remote server.
>>>
>>> The location of the WSDL file -
>>> http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl (As specified in the
>>> below configuration)
>>> The location of the XSD file -
>>> http://ww2.wso2.org/~evanthika/wsdl/import_schema.xsd (Refered in the
>>> import_schema.wsdl file)
>>>
>>> Below is the configuration that I tried.
>>>
>>> <proxy name="TestProxyService" transports="https http"
>>> startOnLoad="true">
>>> <target>
>>> <inSequence>
>>> <send>
>>> <endpoint>
>>> <address
>>> uri="http://localhost:9000/soap/SimpleStockQuoteService"/>
>>> </endpoint>
>>> </send>
>>> </inSequence>
>>> <outSequence>
>>> <send/>
>>> </outSequence>
>>> </target>
>>> <publishWSDL
>>> uri="http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl"/>
>>> </proxy>
>>>
>>> I was able to start the above configuration successfully. Can you check
>>> your WSDL, XSD files and the configuration against mine and see whether you
>>> have properly created the files?
>>>
>>>
>>> Thanks,
>>> Evanthika
>>>
>>>
>>> Asankha C. Perera wrote:
>>>
>>>> Alejandro
>>>>
>>>>> Ah, I tried that once and it failed. I gave it a try again and took a
>>>>> closer look at the logs. It looks like it cant resolve imported schema
>>>>> references.
>>>>>
>>>> This probably is a bug.. Evanthika can you check this and make that a
>>>> test case for the releases?
>>>>
>>>> asankha
>>>>
>>>>
>>>
>>>
>>
>
>
>
Re: Proxy Question
Posted by indika kumara <in...@gmail.com>.
Hi
I have just tried this scenario, it works with a built from current
svn. It seems there were issues with previous releases as I am getting
same errors you have got, for 1.2 releases.
It seems https://issues.apache.org/jira/browse/SYNAPSE-442 has
resolved this issue.
Could you try out this with a synapse SNAPSHOT?
Thanks
Indika
On Wed, Sep 24, 2008 at 4:32 PM, Alejandro Calbazana
<al...@calbazana.com> wrote:
> Hi Evanthika,
>
> I see that your wsdl fully qualifies the location of the schema import
> location. I am using Axis2 to host the service. When the service is built
> and deployed, the schemaLocation attribute is set to locate the schema
> relative to the service. So, Axis2 produces something along the following:
>
> <xs:import namespace="..." schemaLocation="ServiceName?xsd0=xsd0.xsd"/>
>
> As a result Synapse will try to resolve to the filesystem, relative to the
> base of the repository. So, while this works in your case, it may not work
> in other cases where the schemaLocation is defined as above.
>
> Thanks,
>
> Alejandro
>
> Evanthika Amarasiri wrote:
>>
>> Hi Alejandro,
>>
>> I was able to create a proxy service with the publishWSDL uri given as an
>> http url. Also I have an XSD import within this WSDL where the xsd is hosted
>> at a remote server.
>>
>> The location of the WSDL file -
>> http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl (As specified in the
>> below configuration)
>> The location of the XSD file -
>> http://ww2.wso2.org/~evanthika/wsdl/import_schema.xsd (Refered in the
>> import_schema.wsdl file)
>>
>> Below is the configuration that I tried.
>>
>> <proxy name="TestProxyService" transports="https http"
>> startOnLoad="true">
>> <target>
>> <inSequence>
>> <send>
>> <endpoint>
>> <address
>> uri="http://localhost:9000/soap/SimpleStockQuoteService"/>
>> </endpoint>
>> </send>
>> </inSequence>
>> <outSequence>
>> <send/>
>> </outSequence>
>> </target>
>> <publishWSDL
>> uri="http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl"/>
>> </proxy>
>>
>> I was able to start the above configuration successfully. Can you check
>> your WSDL, XSD files and the configuration against mine and see whether you
>> have properly created the files?
>>
>>
>> Thanks,
>> Evanthika
>>
>>
>> Asankha C. Perera wrote:
>>>
>>> Alejandro
>>>>
>>>> Ah, I tried that once and it failed. I gave it a try again and took a
>>>> closer look at the logs. It looks like it cant resolve imported schema
>>>> references.
>>>
>>> This probably is a bug.. Evanthika can you check this and make that a
>>> test case for the releases?
>>>
>>> asankha
>>>
>>
>>
>>
>
>
Re: Proxy Question
Posted by Alejandro Calbazana <al...@calbazana.com>.
Hi Evanthika,
I see that your wsdl fully qualifies the location of the schema import
location. I am using Axis2 to host the service. When the service is
built and deployed, the schemaLocation attribute is set to locate the
schema relative to the service. So, Axis2 produces something along the
following:
<xs:import namespace="..." schemaLocation="ServiceName?xsd0=xsd0.xsd"/>
As a result Synapse will try to resolve to the filesystem, relative to
the base of the repository. So, while this works in your case, it may
not work in other cases where the schemaLocation is defined as above.
Thanks,
Alejandro
Evanthika Amarasiri wrote:
> Hi Alejandro,
>
> I was able to create a proxy service with the publishWSDL uri given as
> an http url. Also I have an XSD import within this WSDL where the xsd
> is hosted at a remote server.
>
> The location of the WSDL file -
> http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl (As specified
> in the below configuration)
> The location of the XSD file -
> http://ww2.wso2.org/~evanthika/wsdl/import_schema.xsd (Refered in the
> import_schema.wsdl file)
>
> Below is the configuration that I tried.
>
> <proxy name="TestProxyService" transports="https http"
> startOnLoad="true">
> <target>
> <inSequence>
> <send>
> <endpoint>
> <address
> uri="http://localhost:9000/soap/SimpleStockQuoteService"/>
> </endpoint>
> </send>
> </inSequence>
> <outSequence>
> <send/>
> </outSequence>
> </target>
> <publishWSDL
> uri="http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl"/>
> </proxy>
>
> I was able to start the above configuration successfully. Can you
> check your WSDL, XSD files and the configuration against mine and see
> whether you have properly created the files?
>
>
> Thanks,
> Evanthika
>
>
> Asankha C. Perera wrote:
>> Alejandro
>>> Ah, I tried that once and it failed. I gave it a try again and took
>>> a closer look at the logs. It looks like it cant resolve imported
>>> schema references.
>> This probably is a bug.. Evanthika can you check this and make that a
>> test case for the releases?
>>
>> asankha
>>
>
>
>
Re: Proxy Question
Posted by Evanthika Amarasiri <ev...@wso2.com>.
Hi Alejandro,
I was able to create a proxy service with the publishWSDL uri given as
an http url. Also I have an XSD import within this WSDL where the xsd is
hosted at a remote server.
The location of the WSDL file -
http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl (As specified in
the below configuration)
The location of the XSD file -
http://ww2.wso2.org/~evanthika/wsdl/import_schema.xsd (Refered in the
import_schema.wsdl file)
Below is the configuration that I tried.
<proxy name="TestProxyService" transports="https http"
startOnLoad="true">
<target>
<inSequence>
<send>
<endpoint>
<address
uri="http://localhost:9000/soap/SimpleStockQuoteService"/>
</endpoint>
</send>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<publishWSDL
uri="http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl"/>
</proxy>
I was able to start the above configuration successfully. Can you check
your WSDL, XSD files and the configuration against mine and see whether
you have properly created the files?
Thanks,
Evanthika
Asankha C. Perera wrote:
> Alejandro
>> Ah, I tried that once and it failed. I gave it a try again and took
>> a closer look at the logs. It looks like it cant resolve imported
>> schema references.
> This probably is a bug.. Evanthika can you check this and make that a
> test case for the releases?
>
> asankha
>
Re: Proxy Question
Posted by "Asankha C. Perera" <as...@wso2.com>.
Alejandro
> Ah, I tried that once and it failed. I gave it a try again and took a
> closer look at the logs. It looks like it cant resolve imported
> schema references.
This probably is a bug.. Evanthika can you check this and make that a
test case for the releases?
asankha
Re: Proxy Question
Posted by Alejandro Calbazana <al...@calbazana.com>.
Ah, I tried that once and it failed. I gave it a try again and took a
closer look at the logs. It looks like it cant resolve imported schema
references. Any hints on how to handle this? Seems to look local to
the filesystem.
Paul Fremantle wrote:
> Alejandro
>
> That should be fine. The only reason we use the registry model is to
> make the examples simple.
>
> Paul
>
> On Tue, Sep 23, 2008 at 2:39 PM, Alejandro Calbazana
> <al...@calbazana.com> wrote:
>
>> Hello,
>>
>> I'm investigating Synapse and would like to know if I can add services to
>> the ESB as proxied services and expose the service WSDL without pulling a
>> copy into a local registry. I have about 3 web services that have complex
>> WSDLs where multiple schema are imported. I'd rather not manage copies of
>> other WSDL as part of my ESB instance as they are subject to change. I see
>> that there have been some challenges with importing these types of WSDL.
>> Has this been addressed in the 1.7 release? I only see examples where WSDL
>> is published as follows:
>>
>> <publishWSDL uri="file:/repository/path/to/wsdl.wsdl"/>
>>
>> Is it possible to say something like uri="http://path/to/wsdl.wsdl"?
>>
>> Thanks!
>>
>> Alejandro
>>
>>
>
>
>
>
Re: Proxy Question
Posted by Paul Fremantle <pz...@gmail.com>.
Alejandro
That should be fine. The only reason we use the registry model is to
make the examples simple.
Paul
On Tue, Sep 23, 2008 at 2:39 PM, Alejandro Calbazana
<al...@calbazana.com> wrote:
> Hello,
>
> I'm investigating Synapse and would like to know if I can add services to
> the ESB as proxied services and expose the service WSDL without pulling a
> copy into a local registry. I have about 3 web services that have complex
> WSDLs where multiple schema are imported. I'd rather not manage copies of
> other WSDL as part of my ESB instance as they are subject to change. I see
> that there have been some challenges with importing these types of WSDL.
> Has this been addressed in the 1.7 release? I only see examples where WSDL
> is published as follows:
>
> <publishWSDL uri="file:/repository/path/to/wsdl.wsdl"/>
>
> Is it possible to say something like uri="http://path/to/wsdl.wsdl"?
>
> Thanks!
>
> Alejandro
>
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com