[ANN] XINS 2.0 Web Services framework released

XINS 2.0 has been released.
XINS is an open-source Web Services development framework.
XINS accepts the following protocols: REST, SOAP, XML-RPC, XML, Yahoo! JSON and JSON-RPC.
From the specification of the API written in simple XML, XINS generates:
* Documentation of the specifications and implementations in HTML and OpenDocument format
* Test forms, for testing your applications with a browser
* Client-side Java code, supporting load-balancing, fail-over and time-out handling
* Server-side skeleton
* Web application (WAR file), compatible with servlet containers
* WSDL, for SOAP-interoperability
* SMD, for the Dojo toolkit
* Unit test code, based on JUnit
* Stubs, typically used for testing
The 2.0 release adds the following features:
* New protocols: Yahoo! JSON (with callbacks) and JSON-RPC (1.0 and 1.1)
* Import of WSDL and XML Schema.
* WSDL and SMD meta functions
* Better integration with the Spring Framework, the Dojo toolkit and GWT
* Examples with REST implementation, implementation in Groovy and with Dojo toolkit
Links:
* Web site: http://xins.sourceforge.net/
* Features: http://xins.sourceforge.net/features.html
* Demo: http://xins.sourceforge.net/demo.html
* User guide: http://xins.sourceforge.net/docs/
* Primer: http://xins.sourceforge.net/primer.html

Similar Messages

[ANN] XINS 2.1 open source Web Services framework release

XINS 2.1 Web Services Framework has been released.
XINS is an open source Web Services Framework based on simple specifications of the Web Service in XML and
generation of code and documentation from the specification.
The generation includes Client JAR with its Javadoc, Server side template with its Javadoc, documentation in OpenDocument Format,
documentation in HTML including the test forms, WSDL file, unit tests (JUnit) and stubs.
The Web Services accept several protocols including REST, SOAP, XML-RPC, XML, JSON Yahoo! and JSON-RPC.
What's new:
* Start the API with java -jar <api name>.war
* Improved generated specification in OpenDocument Format
* Include/exclude calling convention with ACLs
* New calling convention that maps SOAP request and response as the wsdl2api command mapping.
* Smaller generated build.xml
* Added possibility to include other runtime properties files
* The runtime property location can be a URL
* Swing Graphical User Interface
* New tools: emma, glean, webstart
* New target: javadoc-test-<api name>, javadoc-apis
* Bug fixes and small RFEs
Download XINS 2.1:
Windows installer: http://prdownloads.sf.net/xins/xins-2.1.exe?download
TAR GZ archive: http://prdownloads.sf.net/xins/xins-2.1.tgz?download
Resources:
Web site: http://xins.sourceforge.net/
XINS demos: http://xins.sourceforge.net/demo.html
Documentation: http://xins.sourceforge.net/documentation.html
User guide: http://xins.sourceforge.net/docs/index.html

I recommend you implement your web service with JAX-WS 2.0
Axis (both version) are good but why do you want to use something that is not included in JEE API, when Java provide same thing with better performance.
personally try to prevent non standard technologies despite they can be better than core java implementation sometimes.
I don't know Xfire.
the good:
-JAX-WS performance is better than axis,
- you can create your web service simply with annotation.(this means write class and then make it as a service easily)
- support every kind of service invocation(callback,Asynchronous,...)
- architecture is nice (you can operate on SOAP level)
the Bad:
- It is JEE 5 or JSE 6 dependent.
- there is seriously lack of documentation and examples for it, on java web sites and internet.

Which is the BEST Java Web Service Framework to use?

Hi all,
I'm a beginner to Web Services.
I am planning to implement java web services to make the communication between java(Tomcat Server) and C# client.
I found list of web service frameworks like,
1. Apache Axis,(POJO,Axiom)
2. JSON-RPC,
3. Java Web Services Development Pack ,
4. Web Services Invocation Framework,
5. Xfire,
6. XML Interface for Network Services. ...
Please do reply me that which web service framework will be efficient to use.

But, I want to know which Framework will provide
better performance?
better than what?
Also I want to develope the web service as a standard
one andeach has it's own quircks and implementation details. Each should be able to generate and accept the same SOAP messages though if you implement them properly.
It should be able to provide bulk data exchange.
That will depend in large part on your hardware.
Please suggest a web service framework
(Java-based) which will give better performance.again, better than what?
Better than messenger pidgeons?
Better than swallows (European or African)?
And if so, how heavy would the message capsule be? 2 swallows may be able to carry a coconut together, holding it on a piece of string.

Difference Between SAP Connectors and SAP Web Services Framework

Hello,
I would like to know the main difference between the SAP Connectors protocol (that uses SOAP) and the SAP Web Services Framework starting with NetWeaver.
Thank you,
Pedro Carrilho

Hi Pedro,
I guess you are talking about Business Connectors and XI.
If that is the case, the differences are:
SAP XI belongs to SAP Netweaver Technology, whereas BC is an Integration tool provided by Webmethods.
SAP XI is based on a model called "Hub & Spoke" and Business Connectors are "point to point". So by using XI, what happens is that you do not redesign Solutions once again.
With XI you save the entire integration knowledge of a collaborative process centrally in SAP XI: Objects at design time in the Integration Repository and objects at configuration time in the Integration Directory. In this way, SAP Exchange Infrastructure follows the principle of shared collaboration knowledge: You no longer need to search for information about a collaborative process in each of the systems involved, but can call this information centrally instead. This procedure considerably reduces the costs for the development and maintenance of the shared applications.
Also SAP XI comes with pre-configured solutions bundled along with it, so you can straight-away use the solution instead of redesigning.
Also i believe SAP XI is integrated as a required solution for some new mySAP solution like SRM, there are some scenarios within SRM requires SAP XI to be used and we cannot use BC's there.
But incase if you do not have multiple systems connected and communication is between just 2 systems, BC should be sufficient, instead of investing on XI.
But i guess slowly SAP will be stopping its support for BC, as SAP XI can do everything that BC does and even much more.
Also go through these threads...
Re: Business connector
XI vs Connectors (Like JCo and .NET)
I hope this is what you were looking for...
Regards,
Abhy

Which is best web service framework for developing web services in Java?

Hi Friends,
I want to develop web services using Java 1.5.
But I am in confusion with different frameworks provides to develop WS.
Like
1) Apache axis
2) Java Web Service dev. Pack
3) JSON-RPC-Java
4) Web Ser. Invocation Pack
5) XFire
Can some one guide which framework should I use?
OR where will i get useful comparison between this frameworks?

Hi,
Personally I have used:
1. XFire
2. Apache Axis
3. Java Web Service Pack
My personal opinion / .02 cents?
1. XFire is awesome and very easy to set up and get running. They also have a great community / mailing lists. We use it in some production systems and it runs great.
2. Apache AXIS 1/2 made me want to dive out the window and go splat just short of the double yellow line on the road. Pain in the butt to set up and get running. Way too complex. Really bad docs / tutorials / support.
3. Java Web Service Pack - I really prefer NetBeans 5.5 and the JWSP. Easy to build services, cohesive enviroment. You can get the job done.
That's my two cents.
M Goodell

Oracle web services framework confusion

Searching oracle technet i have found references to these oracle webservices frameworks:
1) apache soap server 2 based
2) oracle application server web services
3) jax-rpc web services 10g preview
It seems 1) is deprecated by oracle. That leaves me with the questions:
a) what is the difference between 2) and 3)? is 2) not jax-rpc based?
b) And will the appearance of 3) mean that 2) goes into
maintanance mode soon?
c) can webservices based on 2) be deployed to a standalone oc4j instead of a complete application server? and does jdeveloper support this?

Thanks a lot for clearing this things to me.
I have to start a web services projects and I am confused which tools to use - JDeveloper Assistents or the WebServicesAssembler (as pointed out before).
Because I did not find some hints on this (expecpt your ones), it seems to me that I am missing some point or criteria on that I can do such a decision when to use what of those two tools.
Do I understand you right, that in future JDeveloper and the WebServicesAssembler will use the same .jar files and also generate the same code?
Thanks a lot for such valuable hints, Willi

ANN: Tutorial - Dynamically Invoking Web Services

This tutorial describes how build an application that invokes Web Services dynamically at runtime. You will also learn how to publish and find Web Services registered in Oracle UDDI registry. The sample application implements a bportal where the user can compare insurance prices.
http://otn.oracle.com/sample_code/tutorials/wsdyn/toc.htm
Available 1/7/03.

When you test the connection (steps are below, and in the Setup section, http://otn.oracle.com/sample_code/tutorials/wsdyn/setup.htm#editthe)
do you get a Status Success message?
Edit the connection
1. Click on the Connections node to expand it.
2. Double click on Application server.
3. In the connection wizard step 1 type Connection name as "WebServiceDII".
4. Select connection type as Oracle9iApplication server.
5. Click next to go to Step 2
6. Enter Username and Password valid for this server.
7. Click Next to go to Step 3.
8. Click Next to go to Step 4.
9. Test the connection you should get status "Success".
10. For all future deployment purposes use this ("WebServiceDII") connection.
11. Click "Finish" button to dismiss the dialog box.

Web Services Framework - WSDL Generation

Hi, all!
Question: Is it possible to adapt the wizard-generated WSDL-Files by adding additional elements to the <xsd:sequence>?
Thanks a lot in advance for any answers!
Regards,
Thomas

Check BADi BBP_CAT_CALL_ENRICH (BAdI for Transfer of Additional Parameters to Web Service) it might help you.
Peter

ANN: Jeffrey Zeldman's Web Standards Advisor released

WebAssist is proud to announce the release of Jeffrey
Zeldman's Web
Standards Advisor, a tool to help web designers reap the
benefits of web
standard compliant sites. Built in collaboration with Jeffrey
Zeldman, the
leading authority on web standards, this Adobe Dreamweaver
extension
includes full HTML and CSS validation as well as checks a
wide range of web
standard issues.
Key features:
* Access W3C HTML and CSS validators from within Dreamweaver
* Validates linked, imported, embedded or inline CSS
* Checks 9 different microformats
* Reviews single page, multiple pages or entire site
* Advises on a range of web standard issues, from classitis
to deprecated
tags.
* Go directly to the code for any reported issue
* Full HTML report, suitable for printing
* Advice on what's nonstandard and how to bring it into
compliance from
Jeffrey Zeldman, author of Designing with Web Standards.
Works with Dreamweaver CS4, Dreamweaver CS3, and Dreamweaver
8 on both Macs
and PCs.
Jeffrey Zeldman's Web Standards Advisor is only $49.99
($34.99 upgrade for
owners of Super Suite and Web Designers Suite).
For more information, visit
http://www.webassist.com/go/webstandards
To check out Jeffrey Zeldman's thoughts on the subject:
http://www.zeldman.com/2009/01/12/jeffrey-zeldmans-web-standards-advisor/
Best - Joe
Joseph Lowery
VP of Product Management, WebAssist -
http://www.webassist.com
Author, Dreamweaver CS3 Bible -
http://www.idest.com/dreamweaver/

WebAssist is proud to announce the release of Jeffrey
Zeldman's Web
Standards Advisor, a tool to help web designers reap the
benefits of web
standard compliant sites. Built in collaboration with Jeffrey
Zeldman, the
leading authority on web standards, this Adobe Dreamweaver
extension
includes full HTML and CSS validation as well as checks a
wide range of web
standard issues.
Key features:
* Access W3C HTML and CSS validators from within Dreamweaver
* Validates linked, imported, embedded or inline CSS
* Checks 9 different microformats
* Reviews single page, multiple pages or entire site
* Advises on a range of web standard issues, from classitis
to deprecated
tags.
* Go directly to the code for any reported issue
* Full HTML report, suitable for printing
* Advice on what's nonstandard and how to bring it into
compliance from
Jeffrey Zeldman, author of Designing with Web Standards.
Works with Dreamweaver CS4, Dreamweaver CS3, and Dreamweaver
8 on both Macs
and PCs.
Jeffrey Zeldman's Web Standards Advisor is only $49.99
($34.99 upgrade for
owners of Super Suite and Web Designers Suite).
For more information, visit
http://www.webassist.com/go/webstandards
To check out Jeffrey Zeldman's thoughts on the subject:
http://www.zeldman.com/2009/01/12/jeffrey-zeldmans-web-standards-advisor/
Best - Joe
Joseph Lowery
VP of Product Management, WebAssist -
http://www.webassist.com
Author, Dreamweaver CS3 Bible -
http://www.idest.com/dreamweaver/

[ANN] Online Seminars on Web Services Development Management and Security

This week and the next, join us online here:
http://www.oracle.com/technology/tech/java/newsletter/seminars.html
Or catch the recordings.

join us now here:
http://conference.oracle.com/imtapp/app/cmn_jm.uix?mID=21194005&src=app/wel_public_mtgs

[ANN] XINS 1.4.0 released: Web Services development framework

After 5 months of development, tuning and testing, XINS 1.4.0 has been released. XINS is an open-source Java-based Web Services framework. It offers a simple tool for the development of distributed applications.
One of the key features that differentiates XINS from other technologies is the definition-driven approach. Write simple XML definitions and XINS will generate lots for you:
* Documentation of the specifications and implementations
* Test forms, for testing your applications with a browser
* Client-side Java code, supporting load-balancing, fail-over and time-out handling
* Web application (WAR file), compatible with servlet containers
* WSDL, for SOAP-interoperability
* Unit test code, based on JUnit
* Stubs, typically used for testing
* etc.
Another key feature is protocol independence. XINS supports several communication protocols, including SOAP, XML-RPC and POX-RPC. For each incoming request XINS automatically determines which protocol to use. With XSLT the results can be transformed to HTML or other content types. Custom protocols can be added by added a single Java class.
XINS 1.4 offers various new features over release 1.3, as well as some bug fixes. The main new features are:
* Automatic communication protocol detection.
* Asynchronous requests (http://xins.sf.net/asynchronous.html)
* Generation of documentation in OpenDocument format, for use by OpenOffice.org, for example.
* Support for including files (e.g. HTML) in the WAR file
* Extensive Pet Store demo
Additionally, both the compile-time performance and the runtime performance of XINS have been tuned further.
XINS is used in production systems since the end of 2002. As a stable release, XINS 1.4.0 is backwards compatible with all previous stable releases. It has been tested extensively on various Java and OS platforms, including Solaris, Linux and Windows.
Download XINS 1.4.0, either as a Windows installer or as a platform-independent TAR GZ file:
* Windows installer: http://prdownloads.sf.net/xins/xins-1.4.0.exe?download
* TAR GZ archive: http://prdownloads.sf.net/xins/xins-1.4.0.tgz?download
More information is available here:
* XINS website: http://xins.sf.net/
* XINS 1.4.0 release notes: http://xins.sf.net/notes-1.4.0.html
* User guide: http://xins.sf.net/docs/
* XINS Primer: http://xins.sf.net/primer.html - A 15-minute introduction tutorial
* Presentation Frameworks in general and XINS in particular: http://xins.sf.net/presentation_200604_v4.pdf
* Wikipedia page: http://en.wikipedia.com/wiki/XINS

After 5 months of development, tuning and testing, XINS 1.4.0 has been released. XINS is an open-source Java-based Web Services framework. It offers a simple tool for the development of distributed applications.
One of the key features that differentiates XINS from other technologies is the definition-driven approach. Write simple XML definitions and XINS will generate lots for you:
* Documentation of the specifications and implementations
* Test forms, for testing your applications with a browser
* Client-side Java code, supporting load-balancing, fail-over and time-out handling
* Web application (WAR file), compatible with servlet containers
* WSDL, for SOAP-interoperability
* Unit test code, based on JUnit
* Stubs, typically used for testing
* etc.
Another key feature is protocol independence. XINS supports several communication protocols, including SOAP, XML-RPC and POX-RPC. For each incoming request XINS automatically determines which protocol to use. With XSLT the results can be transformed to HTML or other content types. Custom protocols can be added by added a single Java class.
XINS 1.4 offers various new features over release 1.3, as well as some bug fixes. The main new features are:
* Automatic communication protocol detection.
* Asynchronous requests (http://xins.sf.net/asynchronous.html)
* Generation of documentation in OpenDocument format, for use by OpenOffice.org, for example.
* Support for including files (e.g. HTML) in the WAR file
* Extensive Pet Store demo
Additionally, both the compile-time performance and the runtime performance of XINS have been tuned further.
XINS is used in production systems since the end of 2002. As a stable release, XINS 1.4.0 is backwards compatible with all previous stable releases. It has been tested extensively on various Java and OS platforms, including Solaris, Linux and Windows.
Download XINS 1.4.0, either as a Windows installer or as a platform-independent TAR GZ file:
* Windows installer: http://prdownloads.sf.net/xins/xins-1.4.0.exe?download
* TAR GZ archive: http://prdownloads.sf.net/xins/xins-1.4.0.tgz?download
More information is available here:
* XINS website: http://xins.sf.net/
* XINS 1.4.0 release notes: http://xins.sf.net/notes-1.4.0.html
* User guide: http://xins.sf.net/docs/
* XINS Primer: http://xins.sf.net/primer.html - A 15-minute introduction tutorial
* Presentation Frameworks in general and XINS in particular: http://xins.sf.net/presentation_200604_v4.pdf
* Wikipedia page: http://en.wikipedia.com/wiki/XINS

[ANN] XINS 1.5.0 released: Web Services development framework

XINS 1.5.0 has been released. XINS is an open-source Web Services framework.
It offers a simple tool for the development of APIs.
One of the key features that differentiates XINS from other technologies is the definition-driven approach.
Write simple XML definitions and XINS will generate for you:
* Documentation of the specifications in HTML
* Test forms, for testing your applications with a browser
* Client-side code, supporting load-balancing, fail-over and time-out handling
* Web application, compatible with Java servlet containers
* WSDL, for SOAP-interoperability
* Unit test code, based on JUnit
* Stubs, typically used for testing
Another key feature is protocol independence. XINS supports several communication protocols, including SOAP, XML-RPC and POX-RPC.
For each incoming request XINS automatically determines which protocol to use. With XSLT the results can be transformed to HTML or other content types. Custom protocols can be added.
XINS 1.5 offers various new features over release 1.4, as well as some bug fixes. The main new features are:
* Improved integration with Eclipse and NetBeans
* JMX support
* Tools for APIs (PMD, FindBugs, java2html, test coverage, ...)
* Ant tasks to call an API and to call a XINS target
* Integration of the front-end framework in the core
XINS is used in production systems since the end of 2002. As a stable release, XINS 1.5.0 is backwards compatible with all previous stable releases.
It has been tested extensively on various platforms, including Solaris, Linux and Windows.
Download XINS 1.5.0:
Windows installer: http://prdownloads.sf.net/xins/xins-1.5.0.exe?download
TAR GZ archive: http://prdownloads.sf.net/xins/xins-1.5.0.tgz?download
Resources:
Web site: http://xins.sourceforge.net/
Release notes: http://xins.sourceforge.net/notes-1.5.0.html
XINS demos: http://xins.sourceforge.net/demo.html
Documentation: http://xins.sourceforge.net/documentation.html
User guide: http://xins.sourceforge.net/docs/index.html
101 new features in XINS 1.5 presentation: http://xins.sourceforge.net/xins1.5-features.ppt

Int my ant task I have the following:
<mxmlc services="${SERVICE_CONFIG_PATH}" ... >
Where SERVICE_CONFIG_PATH is the absolute path of the services config file.
I didn't see anything like this in your ant task.

ABAP web services

HIII..
I want to know about a ABAP web service . How this can be created????
Thanks in advance.
Regards
Mayank Saxena

Hi,
Web Services
Business processes consist of individual process steps that can vary in how extensive they are. One or more functions are then assigned to these steps; an executing software component is then assigned to each function. Clearly, the heterogeneous nature of system landscapes in enterprises makes it impossible to implement all the necessary functions associated with a complete process using the same technology on the same component. A modern software infrastructure must be in the position to integrate functions, implemented on widely differing software components, in one effective complete process. Until now, the combination of different applications has largely been based on manually declared interfaces, message formats, and agreements between business partners.
Web services simplify this process. They are based on open, generally accepted standards. They enable you to combine functions in a single process, even if they are implemented in widely differing software components. Web services are standalone, executable entities that can be published, searched for, and called, across a network.
Introduction
The SAP Web Application Server implements the following basic Web services standards: eXtensible Markup Language (XML); Simple Object Access Protocol (SOAP); Web Service Definition Language (WSDL); and Universal Description, Discovery, and Integration (UDDI).
In the documentation that follows, we assume that the reader is familiar with Web service standards and techniques. You will find a general introduction to the Web Services topic under Sun Microsystems, in the pages of W3C, and in the general explanations for standardization organization OASIS under the topic UDDI.
Integration
ABAP and Java Web Services
Enterprises can extend their solutions by using Java or ABAP Web services, or both. If your priority in programming an application is the selection of data, the integration of an ABAP Web Service could be appropriate. Conversely, if you are implementing processes that involve different business partners and systems, it may be beneficial to program in Java and integrate Java Web Services.
The Web Service Framework consists of:
·        The development environment for the ABAP Engine
·        The development environment for the J2EE Engine
·        Tools that support UDDI registration
·        A distributed, interoperable SOAP runtime (ABAP and J2EE Engine)
Processing of SOAP requests using the Internet Communication Framework
Web Services and the SAP Exchange Infrastructure
The SAP Exchange Infrastructure is a key area in SAP NetWeaver. The Exchange Infrastructure provides an open, process-oriented integration infrastructure for the unhindered flow of information and for XML-based message exchanges. Systems integrated using SAP XI exchange messages over the Integration Server.
The programming model for XI ABAP proxies and Web services has been unified. The advantage of this is that both technologies can be implemented so that they complement one another. Messages can be sent and received either using the XI runtime or the Web service runtime.
Additional proxy runtime services can be controlled using protocols that you request using a proxy method. The features you have available depend on whether you are using the Web Service Framework or the Exchange Infrastructure for communication.
Features
The ABAP Workbench offers an environment where you can publish, search for, and call Web services. It enables the SAP Web Application Server to act both as a server and client for Web services.
The Web service infrastructure enables developers to:
·    Publish independent function that were implemented as RFC-enabled function modules, function groups, BAPIs, or XI message interfaces. This includes functions available as part of mySAP.com solutions, or functions developed by customers or partners. The Web service can be used across the entire Internet using standard protocols and can easily be added to any development environment. (See also Creating a Web Service).
·    Consume Web services, regardless of where they are stored or how they are implemented. Business processes can be implemented across several systems, either within an enterprise or across several enterprises. (See also Consuming Web Services.)
The following triangle shows the basic architecture of the Web Service Framework:
Service Provider
After the functions have been implemented, a Web service interface must be created that provides a representation of the Web service for the user. This interface offers an abstraction layer and thus independence from the specific implementation used. Based on this interface, the Web service is configured and can be called at runtime. Publishing Web services in a UDDI Registry is supported by the UDDI client functions in the SAP Web AS.
Service Directory
You can store Web service definitions and released Web Services in a UDDI Registry. WSDL documents provide the basis of the Web service client, which can then be searched for in the UDDI using either a browser or the standard UDDI APIs. Web services can be published and searched for in all registries that conform to the standard. SAP also offers a public UDDI Business Registry under uddi.sap.com.
Service Requestor
The SAP Web AS allows you to integrate Web services. It can generate Web service clients from WSDL files.
Standardization and Extensibility
Web services and Web service standards develop quickly; new standards are being presented continually at standardization committees. However, these extended standards such as security standards or additional protocols can easily be integrated in the Web Service Framework using SAP.
See also:
Web Services Toolset
For more information see the following link.
http://help.sap.com/saphelp_nw04/helpdata/en/9b/dad1ae3908ee44a5caf57e10918be9/frameset.htm
Please Reward If Helpful
Jagadish

Simple web services and XA

WSI-15 indicates non-transactional WS, But WSI-16 indicates WS "use short-running,
XA transactions"

A<WSI-15>Let me clear up any possible confusion. There is no inherent support for
transactions within the web service framework and in particular there is no way for
a web service client to demarcate a transaction. There are some emerging standards
(BTP,SOAP-CTX) that hope to address these issues but they really are in their infancy.
On the implementation side of the web service (with your stateless session EJB for
instance) there is however nothing to stop you using transaction. The actual business
process that you are invoking can and should have complete XA transaction support
which is what slide 16 eludes to.
"Elie Dagher" <[email protected]> wrote:
>
WSI-15 indicates non-transactional WS, But WSI-16 indicates WS "use short-running,
XA transactions"

Generate XML file from RFC using Web Services

Hi,
I am trying to save an RFC enabled Function Module output to an XML file using ABAP web services.
I could able to create Web Service and release it using WSCONFIG/WSADMIN. I can actually get the output in XML file when i launch the web service home page. But I need this to be done in the ABAP program itself. So If i run the RFC I could able to create,release web service and capture the Generated XML file by SOAP runtime.
Any FM available?
Thanks,
Ram Sanjeev

which version of WAS you are on .
if you are on WAS6.40 check the following weblog on how to consume webservice using the wsdl file.
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
lower version of WAS use class cl_http_client.
if this case you have to manually build the soap message.
/people/durairaj.athavanraja/blog/2004/09/20/consuming-web-service-from-abap
Regards
Raja

[ANN] XINS 2.0 Web Services framework released

Similar Messages

Maybe you are looking for