Invocation of Netweaver generated Web Service from XI

Hi,
I have defined a webservice for a stateless session bean using the developer studio. From the wsdl I have imported the message interface as external definition. I have defined mappings on the respective message type. Now I would like to call my service using the SOAP receiver adapter.
Could anybody tell me which URL has to be quoted there. I retrieve the wsdl from the following address:
http://myhost:50000/AddressService/AddressConfig?wsdl
Since the webservice is RPC like, is it valid to invoke it using the SOAP receiver adapter?
Kind regards,
Heiko

Hi Naveen,
Do you have an answer for this ....
Hi Friends,
I have a question regarding publishing a WSDL created via XI (Integration Directory) to a UDDI Server of SAP WAS JAVA 640. Can I publish the WSDL generated from XI in the UDDI Server provided as a part of SAP WAS 640 ? I know that the WSDL will be specific for a client( sender) but I feel that its better than emailing the WSDL to the client after generating it in the integration directory. Any relevant documents, links explaining how to do that will be appreciated.
The above question was asked by Siva Maranani before. His question was as below .
"I know that whenever a webservice is developed using NDS it can be deployed in WebAs and the same can be registered in UDDI ( webAs acting as UDDI registry).
Now my requirement is to register a WSDL file (which describes) for an external webservice. Can WebAs be used as a UDDI registry..?
I like to know if this is possible or not..? if yes.. how..?"
Waiting for the reply...
Thanks & Regards,
Mathew

Similar Messages

Have problem when generate Web Service from bapi function

Dear all,
Please kindly help me about generating Web Service from BAPI function, It does not success only this attached function.
I have done so many function without any problems.
I found 1 case that I use specific variable to be an import/ export then, it can't create as well.
As for this one, I try so many changes but I can't success it as well.
This is my function on R/3 4.6C, Dot net connector 2.0, Dot net Frame Work 1.1.
FUNCTION Z_BAPI_ATTACHMENT_CREATE.
""Local interface: Type: Remote-enabled module
*" IMPORTING
*" VALUE(P_BOTYPE) LIKE BORIDENT-OBJTYPE
*" VALUE(P_BO_ID) LIKE BORIDENT-OBJKEY
*" VALUE(P_MSGTYP) LIKE SOFM-DOCTP
*" VALUE(P_DOCTY) LIKE BORIDENT-OBJTYPE
*" VALUE(P_RELTYP) LIKE BRELTYP-RELTYPE
*" VALUE(P_FNAME) LIKE RLGRAP-FILENAME
*" VALUE(P_OBJDES) TYPE SO_OBJ_DES
*" EXPORTING
*" VALUE(RETURNMESSAGE) TYPE CHAR50
INCLUDE : <cntn01>.
P_BOTYPE TYPE BORIDENT-OBJTYPE DEFAULT 'BUS2105'
P_BO_ID TYPE BORIDENT-OBJKEY
P_MSGTYPE TYPE SOFM-DOCTP DEFAULT 'URL'
P_DOCTY TYPE BORIDENT-OBJTYPE DEFAULT 'MESSAGE'
P_RELTYP TYPE BRELTYP-RELTYPE DEFAULT 'ATTA'
P_FNAME TYPE RLGRAP-FILENAME
P_OBJDES TYPE SO_OBJ_DES
TYPES: BEGIN OF ty_message_key,
foltp TYPE so_fol_tp,
folyr TYPE so_fol_yr,
folno TYPE so_fol_no,
doctp TYPE so_doc_tp,
docyr TYPE so_doc_yr,
docno TYPE so_doc_no,
fortp TYPE so_for_tp,
foryr TYPE so_for_yr,
forno TYPE so_for_no,
END OF ty_message_key.
DATA : lv_message_key TYPE ty_message_key.
DATA : lo_message TYPE swc_object.
DATA : lt_doc_content TYPE STANDARD TABLE OF soli-line
WITH HEADER LINE.
First derive the Attachment's ( MESSAGE )document type.
p_docty = 'MESSAGE'.
CASE p_reltyp.
In case of URls
WHEN 'URL'.
 p_msgtyp = 'URL'.
In case of Notes / Private Notes
WHEN 'NOTE' OR 'PNOT'.
 p_msgtyp = 'RAW'.
WHEN 'ATTA'.
Take given parameter e.g. 'DOC', 'PDF' etc.
P_MSGTYP = 'EXT'.
WHEN OTHERS.
....exit
 EXIT.
ENDCASE.
Create an initial instance of BO 'MESSAGE' - to call the
instance-independent method 'Create'.
swc_create_object lo_message 'MESSAGE' lv_message_key.
define container to pass the parameter values to the method call
in next step.
swc_container lt_message_container.
Populate container with parameters for method
swc_set_element lt_message_container 'DOCUMENTTITLE' p_objdes.
swc_set_element lt_message_container 'DOCUMENTLANGU' 'E'.
swc_set_element lt_message_container 'NO_DIALOG' 'X'.
swc_set_element lt_message_container 'DOCUMENTNAME' p_docty.
swc_set_element lt_message_container 'DOCUMENTTYPE' p_msgtyp.
In case of URLs..it should be concatenated with &KEY& in the begining.
CASE p_msgtyp.
WHEN 'URL'.
lt_doc_content = '&KEY&http://www.rmtiwari.com' .
 CONCATENATE '&KEY&' p_fname INTO lt_doc_content.
 APPEND lt_doc_content.
In case of Notes or Private Notes, get the data from files on appl
server or from wherever(? - remember background).
WHEN 'RAW'.
 lt_doc_content = p_fname.
 APPEND lt_doc_content.
In case of PC File attachments
WHEN OTHERS.
 OPEN DATASET p_fname FOR INPUT IN BINARY MODE.
 IF sy-subrc EQ 0.
 DO.
 READ DATASET p_fname INTO lt_doc_content. "2 of 27
 IF sy-subrc EQ 0.
 APPEND lt_doc_content.
 ELSE.
 EXIT.
 ENDIF.
 ENDDO.
 CLOSE DATASET p_fname.
 ENDIF.
ENDCASE.
'DocumentContent' is a multi-line element ( itab ).
swc_set_table lt_message_container 'DocumentContent' lt_doc_content.
Size is required in case of File attachments
DATA : lv_doc_size TYPE i.
DATA : l_file_lines TYPE i.
DESCRIBE TABLE lt_doc_content LINES l_file_lines.
READ TABLE lt_doc_content INDEX l_file_lines.
lv_doc_size = ( 255 * ( l_file_lines - 1 ) ) +
STRLEN( lt_doc_content ).
swc_set_element lt_message_container 'DOCUMENTSIZE' lv_doc_size .
Refresh to get the reference of create 'MESSAGE' object for attachment
swc_refresh_object lo_message.
swc_call_method lo_message 'CREATE' lt_message_container.
Get Key of new object
swc_get_object_key lo_message lv_message_key.
Now we have attachment as a business object instance. We can now
attach it to our main business object instance.
Create main BO object_a
data: LO_IS_OBJECT_A type SIBFLPORB. "type SIBFLPORB is unknown, so I
DATA: lo_is_object_a TYPE borident.
lo_is_object_a-objkey = p_bo_id.
lo_is_object_a-objtype = p_botype.
LO_IS_OBJECT_A-CATID = 'BO'.
Create attachment BO object_b
data: LO_IS_OBJECT_B type SIBFLPORB. "type SIBFLPORB is unknown
DATA: lo_is_object_b TYPE borident.
lo_is_object_b-objkey = lv_message_key.
lo_is_object_b-objtype = p_docty.
LO_IS_OBJECT_B-CATID = 'BO'.
*TRY.
*CALL METHOD CL_BINARY_RELATION=&gtCREATE_LINK
EXPORTING
IS_OBJECT_A = LO_IS_OBJECT_A
IS_OBJECT_B = LO_IS_OBJECT_B
IP_RELTYPE = P_RELTYP.
CALL FUNCTION 'BINARY_RELATION_CREATE'
EXPORTING
 obj_rolea = lo_is_object_a
 obj_roleb = lo_is_object_b
 relationtype = p_reltyp
EXCEPTIONS
 OTHERS = 1.
Check if everything OK...who cares!!
COMMIT WORK.
if sy-subrc = 0.
RETURNMESSAGE = 'S-Success'.
else.
RETURNMESSAGE = 'E-Error'.
endif.
ENDFUNCTION.
Thanks in advance,
Benjawan
Edited by: Nitipat Chadchavalpanichaya on Oct 20, 2008 9:02 AM

There is no any error message show up. It just the class
Z_BAPI_ATTACHMENT_CREATE doesn't create autometically as normal. I showed you as below.
That means I can't call class z_bapi_attachment_create.
' <autogenerated>
' This code was generated by a SAP. NET Connector Proxy Generator Version 2.0
' Created at 21/10/2551
' Created from Windows
' Changes to this file may cause incorrect behavior and will be lost if
' the code is regenerated.
' </autogenerated>
Imports System
Imports System.Text
Imports System.Collections
Imports System.ComponentModel
Imports System.Runtime.InteropServices
Imports System.Xml.Serialization
Imports System.Web.Services
Imports System.Web.Services.Description
Imports System.Web.Services.Protocols
Imports SAP.Connector
'@ <summary>
'@ Client SAP proxy class
'@ </summary>
<WebServiceBinding(Name:="dummy.Binding", Namespace:="urn:sap-com:document:sap:rfc:functions")> _
Public Class PRAttachment
 Inherits SAPClient
 '@ <summary>
 '@ Initializes a new PRAttachment.
 '@ </summary>
 Public Sub New()
 End Sub
 '@ <summary>
 '@ Initializes a new PRAttachment with a new connection based on the specified connection string.
 '@ </summary>
 '@ <param name="connectionString">A connection string (e.g. RFC or URL) specifying the system where the proxy should connect to.</param>
 Public Sub New(ByVal ConnectionString As String)
 MyBase.New(ConnectionString)
 End Sub
 '@ <summary>
 '@ Initializes a new PRAttachment and adds it to the given container.
 '@ This allows automated connection mananged by VS component designer:
 '@ If container is disposed, it will also dispose this SAPClient instance,
 '@ which will dispose a contained connection if needed.
 '@ </summary>
 '@ <param name="Cont">The container where the new SAPClient instance is to be added.</param>
 Public Sub New(ByVal Cont As Container)
 MyBase.New(Cont)
 End Sub
End Class

I generated web service from function module.Where can I find .wsdl file ?

Hi,
I generated web service from function module.
Where can I find .wsdl file ?
I want to use .wsdl file in .Net application.
Thanks.

Hii Cemil Bozlagan,
All Remote enabled Function Modules in Web AS 6.20 and Above are available as Webservices and the WSDL documents are available in the web service repository at
[http://<host>:<port>/sap/bc/bsp/sap/webservicebrowser/search.html]
Find the respective BAPI.
Click on the WSDL link in the browser and download the WSDL document and use it as per the requirement
Regards,
Varun

Error while generating Web Service from a function module.

Hi Experts,
I am trying to create a web service from function module by doing the steps as mentioned in the below document:
http://www.sdn.sap.com/irj/scn/index;jsessionid=(J2EE3417800)ID1146834250DB10778842957931285337End?rid=/library/uuid/80fa3dff-ce76-2a10-3f94-f3df8f2db5a2&overridelayout=true
When i save it as an local object instead of generating the Web Service it gives me the below error:
"Error during activation of Web Service"
Kindly let me know what needs to be done inorder to resolve this issue.
I have a feeling that this error may be with respect to some authorizations, in that case how do we resolve it
Helpful Inputs Awaited.!!!
Thanks
Dhwani

Hi Dhawani,
Hi Pavan,
Can you please elaborate...how this will help??
Thanks
Dhwani
I dont know the specific reason but internally there may some inconsistancy but i faced the same error and i tried with saving it in the package.
Thanks

Generating Web Service from PL/SLQL procedures using ODSI

1) Is there a way for us to generate REST based web services from PL/SQL procedures using Oracle data services Integrator? If Yes, Can you please point me to any available documentation
2) I am trying to create a phyiscal data source based on PL/SQL procedures in the hope of turning these data sources into web services. I created a JDBC connection in web logic server console and am trying to view the packages under APPS but ODSI always crashes after selecting APPS. Is there a way to resolve this?
Thanks
Bhanu

Hi..
We came accross this problem a while back (I think it was us that the patch was created for). The patch was released under CR369707.
Additionally it took us a while to figure out how to use it correctly.. Here's the info for it from a mail i receievd from our support contact..
Here is more information from engineering on the patch:
This is patch for filtering Stored Procedures in the New Physical Data Service Wizard. It is a partial fix to the problem. It just does filtering - it still retrieves all the jdbc metadata for everything that matches the filter. Ideally, the wizard would let you explore the stored procedures - retrieving the name only - and once you selected a stored procedure, it would retrieve the argument types (which is the expensive part).
Copy these two files to a safe place
<bea_home>\<aldsp_home>\eclipse-plugins\dsp\eclipse\plugins\com.bea.dsp.ide.external_10.3.0\dsp-ide-ldshredder.jar
<bea_home>\<aldsp_home>\eclipse-plugins\dsp\eclipse\plugins\com.bea.dsp.ide.import_metadata_10.3.0.jar
Replace the files with the ones provided in the patch (which I sent you be eMail recently).
Creating Relational Database Physical Data Services -> Stored Procedures will be affected as follows :
The Search field used to represent a pattern for the stored procedures only, and this patterns were applied against every schema visible to ALDSP. The patch allows you to also specify a list of catalogue patterns (useful only when applicable), a list of schema patterns and a list of procedure name patterns. These lists are separated by the pipe symbol, and the lists themselves are command-separated. The catalogue and schema patterns are regular expressions, the procedure pattern is for a database 'like' clause. For, Oracle, the catalogue patterns are not applicable.
Example:
|ODM1,ODM2|B% // look in schemas containing the strings ODM1 or ODM2 for procedures that start with B
// possible results would be MY_ODM1.BUILDER, ODM2.BOTTOM
|^ODM$|B%D // look in the ODM schema for procedures that start with B and end with D.
Also - if there is a search string in the Search box, that search string will be applied to the schema when you click on the + to expand it in the Tree.
Note that once a schema has been 'explored' - either by a search, or by expanding it in the tree, further searches will not update it's children. You would need to quit the wizard and restart.
Once you get the patch if you have issues let me know..

Generating web service from session bean

Hi
I have a session bean in one project which has a service-endpoint defined.
My web services are in another project entirely, within the same workspace if that helps any.
When I generate the web service from the EJB JDev turns the business tier project into a web project,
I don't see any options to include the web service in the web project.
I've reversed all of the changes, but wonder if I shouldn't redo it and copy the mapping file and configuration
across to the web project and reverse the changes in the business tier.
This is a workaround that I'm hoping to avoid, as I'm doing the "howto" for this in our project.
How is this normally done?

I tried generating the web servioce from WSDL, in the web project.
I tested and the web service works fine.
Then I changed the config file to point to the ejb, but the server won't start up....
*08/09/17 10:58:40 WARNING: Application.setConfig Application: current-workspace-app is in failed state as initialization failed.*
This is the webservices.xml bit I updated...
<ejb-link>SomeOrOtherEjbName</ejb-link> The bit I found in webservices.xml when the service is in the business tier.
 The service that works in the web tier.

Parameter names change when generating web service from WSDL

Hi,
I have a problem with BEAs web services that I'm hoping someone can help me with.
I have a
WSDL file, and from that I want to generate a web service implementation and a
web service
client. In the WSDL file, I have a message defined like this:
<message name="someRequest">
<part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
name="data"/>
</message>
I generate the server using the server using the wsdl2service Ant task, I implement
the necessary classes, and I deploy it. When I access the deployed web service,
the parameter name has changed, from "data" to "bytes". If I access the WSDL file
of the deployed web service, it says:
<message name="someRequest">
<part xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:base64Binary"
name="bytes"/>
</message>
This happens for all parameters, string parameters are renamed to "string", base64Binary
parameters are renamed to "bytes", etc...
This poses a problem to me, because if I generate a web service client from the
original WSDL file, it will not be able to talk to my web service. Is there any
way of forcing a web service generated from a WSDL file to keep the parameter
names of the original WSDL file?
Any help in this is greatly appreciated.
Regards,
Petter

From a quick look of your WSDL, it seams that you are mixing document-literal-bare and document-literal-wrapped flavor of web services. WSA may be able to do a better job at working around this mixed flavors than JDeveloper.
If you have hand crafted this WSDL, I would recomend that you spend some time looking at the way WSDL are generated, with the java-first mode (or bottom-up), then author the WSDL you need for the final service.
Here are sample of bare-style :
<xsd:element name="getPupilAddressResponse" type="xsd:string"/>
<xsd:element name="getPupilAddressRequest" type="xsd:int"/>
Wrapped will looks like that:
<xsd:element name="getSENLevelResponse">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="1">
<xsd:element name="LevelDetails" type="tns:SENLevelRecord"/>
<xsd:element name="RecordCount" type="xsd:int">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Hope this helps,
Eric

Is there any script in S1AS which generates Web services from ejbs in jar?

I'm porting a J2EE app from WebLogic to S1AS7. The ISV uses Ant/XDoclet to do some code generation and build. One of targets in the build scripts is to take as input an EJB JAR file and create all the needed web service components and package them into a deployable EAR file using WebLogic's servicegen Ant task
(http://edocs.bea.com/wls/docs81/webserv/assemble.html#1052126).
Is there anything similar in S1AS?
A quick response is greatly appreciated.
Thanks
Kishore

We had looked into doing something similar, and this post is the closest we found.
https://community.qualys.com/thread/11816
Basically you will need a middle-man between Qualys and ConfigMgr to house the data. This may be a new database, or a whole seperate platform. I expect this could easily be done with SQL and SSRS.
Also note, database edits to the ConfigMgr database are
not supported by Microsoft, I would recommend using a central system to pull data from Qualys and ConfigMgr without modifying either.
Daniel Ratliff | http://www.PotentEngineer.com

Web Service From Java class, serialization problem

Hi,
I want to create Web Service from Java class, I made java project, generated web service from it, create web service archive project and deployed it to WAS 6.40.
My class have 2 methods,
public int add(int a, int b);
public MyResponse doSomthing(MyRequest req);
I can succesfully call add method from Web Service Navigator, it works fine but when I call doSomthing methods I get the following error:

Deserializing fails. Nested message: XML Deserialization Error. Result class [com.mycomp.sap_tech.ws.MyRequest] does not have property [Amount] of type [java.lang.String]. It is required to load XML..

Any ideas how to resolve it?
P.S. MyRequest class is exposed throw VI, has default constractor and public getters and setters for all properties. It implements Serializable as well. Any guesses?
Thanks in advance,
Victor.

Hi Bhavik, thanks for response.
as I already mentioned it implements Serializable, so it is not the problem.
Thanks Avi but it didn't helps iether
Victor

How to generate web services for OAS with wsdl extension

Hi,
I wanted to know how to generate web services from Oracle Application Server especially with .wsdl extension and with document/literal style.
I know that earlier there was a tool called SmartConnect from BEA WebLogic.
But that will work only with ALSB (Aqua logic Service Bus). I guess that ALSB has been renamed as Oracle Service Bus by Oracle after the acquisition of WebLogic. My question is what is the new name for the SmartConnect Tool from WebLogic, which generates wsdl very easily from Oracle database.
I am unable to know the new name for SmartConnect and how to download that tool from Oracle web site.
Also, I want to know, whether there is any other way to generate the wsdl from Oracle, if so, please let me know.
Regards
Raman

Hi Jeethandra,
Please refere to the below link might be some help.
[http://help.sap.com/saphelp_mdmgds55/helpdata/en/45/069152856241e1e10000000a1553f6/frameset.htm]
regards
shankar

Consuming web service from ecc6.0:using webservice proxy -service call

Hi,
 On SYSTEM A
AS POC we have generated web service from BAPI_FLIGHT_GETLIST from ECC6.0.
0.we tested using web browser it was working fine.Then saved the WSDL to local pc
On SYSTEM B
1.I have created proxy using wsdl saved on local pc,
2. Created RFC Destination Type "H" giving the web service path
path : /sap/bc/srt/rfc/sap/ZBAPI_FLIGHT_GETLIST_WSD host & http port number.
3. created Logical port using LPCONFIG adn provided the RFC destination.
4. created service call from abap dynpro by using third option "web service proxy"
then selected the proxy generated above.
when i go to component controller context and see,
 exporting
 output
 FLIGHT_LIST
Under FLIGHT_LIST i dont see the node Item then list of elements under that.
How to use this in view as such i dont see output individual parameters??
If i use function module and create service call
then i could see properly like and could use it in view.
 CHANGING
 FLIGHT_LIST
 AIRLINEID
Pointers will be suitable rewarded.
Regards
shekar chandra

closed

Error when generating a Web Service from WSDL (Weblogic Workshop)

Hi,
I am using weblogic workshop 10 for implementing web services and its was working fine. But now when I try to generate a web service from WSDL its crashing with the following error;
Could not find one or more classes: "org.apache.tools.ant.launch.AntMain". Please check the Ant classpath.
org.eclipse.core.runtime.CoreException: Could not find one or more classes: "org.apache.tools.ant.launch.AntMain". Please check the Ant classpath.
     at com.bea.workshop.webservices.core.gen.JwsFromWsdlBuilder.buildJws(JwsFromWsdlBuilder.java:107)
     at com.bea.workshop.webservices.ui.wizards.jwsfromwsdl.GenerateJwsFromWsdlWizard$1.execute(GenerateJwsFromWsdlWizard.java:133)
     at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:101)
     at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
     at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:113)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
org.eclipse.core.runtime.CoreException[4]: com.bea.workshop.webservices.core.gen.WebServicesException:
     at com.bea.workshop.webservices.core.gen.GenerationScript.runAnt(GenerationScript.java:154)
     at com.bea.workshop.webservices.core.gen.GenerationScript.createJWS(GenerationScript.java:98)
     at com.bea.workshop.webservices.core.gen.JwsFromWsdlBuilder.buildJws0(JwsFromWsdlBuilder.java:135)
     at com.bea.workshop.webservices.core.gen.JwsFromWsdlBuilder.buildJws(JwsFromWsdlBuilder.java:98)
     at com.bea.workshop.webservices.ui.wizards.jwsfromwsdl.GenerateJwsFromWsdlWizard$1.execute(GenerateJwsFromWsdlWizard.java:133)
     at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:101)
     at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
     at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:113)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Caused by: org.eclipse.core.runtime.CoreException: Could not find one or more classes: "org.apache.tools.ant.launch.AntMain". Please check the Ant classpath.
     at org.eclipse.ant.core.AntRunner.problemLoadingClass(AntRunner.java:445)
     at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:417)
     at org.eclipse.ant.core.AntRunner.run(AntRunner.java:362)
     at com.bea.workshop.webservices.core.gen.GenerationScript.runAnt(GenerationScript.java:152)
     ... 8 more
I have checked my ANT_HOME and its pointing to the correct location bea\tools\eclipse32\eclipse\plugins\org.apache.ant_1.6.5 and the AntMain classs is present in this path: org.apache.tools.ant.launch.AntMain
If anyone has any idea on this please suggest a solution.
Thanks in advance
-AKJ

Yes, I assume you are talking about ANT_HOME:
see this Screenshot which shows my current settings
[http://i43.tinypic.com/nbrec6.jpg|http://i43.tinypic.com/nbrec6.jpg]
Regards
-AKJ

Problem using WSDL from SAP in IBM's RAD for generating web service client

When importing a WSDL from the ABAP stack on a SAP 6.40 system into IBM's RAD tool for generating a web service client there are errors with the soap fault classes that get generated. The WSDL declares the types for the faults with WebServiceName.RfcException and these have elements of name, text, and message. When the tools see this in the WSDL they generate classes that extend the Java exeception class and this causes an error because the "message" name conflicts with the standard java exception message. Has anyone else ran into this problem? It seems like a basic problem many java tools for generating web service client proxies would have because the soap faults get turned into java exceptions. This name conflict of the java exception with the WSDL fault definition means that code always needs to be adjusted and cannot simply use the classes that are generated from the WSDL. Anyone run across this or a similar problem in the java environment using the SAP WSDL?
Aaron

Hi,
Hello again .
Have you tried your service using soapui ?
You can use your WSDL as input .
In order to eliminate eclipse problem try this service:(I just did)
http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL
Regards.
package main;
import java.io.FileInputStream;
import java.rmi.RemoteException;
import java.util.Properties;
import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapType;
import org.oorsprong.www.websamples_countryinfo.CountryInfoServiceSoapTypeProxy;
import org.oorsprong.www.websamples_countryinfo.TCountryCodeAndName;
public class Main {
public static void main(String[] args) {
try {
   final Properties properties = new Properties();
   properties.load(new FileInputStream("properties.ini"));
   System.getProperties().putAll(properties);
} catch (final Exception exception) {
   exception.printStackTrace();
new Main();
public Main() {
try {
   final CountryInfoServiceSoapType infoServiceSoapType = new CountryInfoServiceSoapTypeProxy();
   final TCountryCodeAndName[] tCountryCodeAndNames = infoServiceSoapType.listOfCountryNamesByName();
   for (final TCountryCodeAndName tCountryCodeAndName : tCountryCodeAndNames) {
    System.out.println(tCountryCodeAndName.getSName());
} catch (final RemoteException exception) {
   exception.printStackTrace();

Error generating Web Service control in Workshop 9.2 from any wsdl

When trying to generate web service control from service control wizard I get the following error:
An error was encountered while generating types: null
The full stack trace is:
<pre>java.lang.reflect.InvocationTargetException
 at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:327)
 at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:830)
 at com.bea.wlw.controls.service.ui.GenerateSCWizard.performFinish(GenerateSCWizard.java:213)
 at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676)
 at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349)
 at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
 at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
 at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
 at org.eclipse.jface.window.Window.open(Window.java:787)
 at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:110)
 at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
 at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
 at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
 at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
 at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
 at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
 at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
 at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
 at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
 at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
 at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
 at org.eclipse.core.launcher.Main.run(Main.java:973)
 at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.NullPointerException
 at com.bea.wlw.controls.service.ui.GenerateSCWizard$Finisher.run(GenerateSCWizard.java:501)
 at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
</pre>
I have tried different wsdls simple and complex and still getting the same error. What could be the problem? Is it a bug or my misconfiguration? Has anybody succeded to generate service control in workshop 9.0 and above?

Did you also get a CrashWeb dialog?
Andrey Adamovich wrote:
When trying to generate web service control from service control wizard I get the following error:
An error was encountered while generating types: null
The full stack trace is:
<pre>java.lang.reflect.InvocationTargetException
 at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:327)
 at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:830)
 at com.bea.wlw.controls.service.ui.GenerateSCWizard.performFinish(GenerateSCWizard.java:213)
 at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676)
 at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349)
 at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556)
 at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
 at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
 at org.eclipse.jface.window.Window.open(Window.java:787)
 at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:110)
 at org.eclipse.jface.action.Action.runWithEvent(Action.java:996)
 at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538)
 at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
 at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3125)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2758)
 at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
 at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
 at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
 at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
 at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
 at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
 at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
 at org.eclipse.core.launcher.Main.run(Main.java:973)
 at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.NullPointerException
 at com.bea.wlw.controls.service.ui.GenerateSCWizard$Finisher.run(GenerateSCWizard.java:501)
 at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
</pre>
I have tried different wsdls simple and complex and still getting the same error. What could be the problem? Is it a bug or my misconfiguration? Has anybody succeded to generate service control in workshop 9.0 and above?

Error While generating Web Service Proxy using Web Service Action in MII 12

Hi All,
We are using the Web Service action block in BLS transaction to call a web service from an external legacy system. When we provide the WSDL in the action block configuration and click Next we can see the Port and Operation of the web service which we have selected and finally clicked on Finish. On clicking Finish it is giving an error "[Fatal Error] :-1:-1: Premature end of file." and no web service request/response structures are being generated.
The WSDL file is attached herwith. Please check and provide the solution. We are using MII 12.2 SP02 with latest patch.
An error message is also added to the NetWeaver log as below:
XmlProxy Error: Premature end of file.
[EXCEPTION]
org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
at com.sap.lhcommon.schema.XmlHelper.loadDocument(XmlHelper.java:38)
at com.sap.lhcommon.schema.XmlHelper.loadDocumentNS(XmlHelper.java:28)
at com.sap.lhcommon.webservice.SoapMessage.getExampleXmlAsBytes(SoapMessage.java:103)
at com.sap.xmii.servlet.XmlProxy.service(XmlProxy.java:204)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
The wsdl file is as follows:
<wsdl:definitions
targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
>
<wsdl:types>
 <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
 xmlns="http://www.w3.org/2001/XMLSchema">
 <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
 <complexType name="ProductionOrderDetailsInput">
 <sequence>
 <element name="detailsString" type="xsd:base64Binary"/>
 <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
 <element name="fullExplosionFlag" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="ProductionOrderDetailsReceipt">
 <sequence>
 <element name="errorMessage" nillable="true" type="xsd:string"/>
 <element name="valid" type="xsd:boolean"/>
 </sequence>
 </complexType>
 </schema>
</wsdl:types>
<wsdl:message name="processOrderDetailsResponse">
<wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
</wsdl:message>
<wsdl:message name="processOrderDetailsRequest">
<wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
</wsdl:message>
<wsdl:portType name="PodService">
 <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
 <wsdl:input message="impl:processOrderDetailsRequest"
 name="processOrderDetailsRequest"/>
 <wsdl:output message="impl:processOrderDetailsResponse"
 name="processOrderDetailsResponse"/>
 </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="ProcessOrderDetails">
 <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
 <wsdl:input name="processOrderDetailsRequest">
 <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
 </wsdl:input>
 <wsdl:output name="processOrderDetailsResponse">
 <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
 </wsdl:output>
 </wsdl:operation>
</wsdl:binding>
<wsdl:service name="PodService_Service">
 <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
 <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
 </wsdl:port>
</wsdl:service>
</wsdl:definitions>

The WSDL file is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
targetNamespace="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://pod.service.server.mesassembly.cis.cat"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:intf="urn:cat.cis.mesassembly.server.service.pod"
xmlns:impl="urn:cat.cis.mesassembly.server.service.pod"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding"
>
<wsdl:types>
 <schema targetNamespace="http://pod.service.server.mesassembly.cis.cat"
 xmlns="http://www.w3.org/2001/XMLSchema">
 <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
 <complexType name="ProductionOrderDetailsInput">
 <sequence>
 <element name="detailsString" type="xsd:base64Binary"/>
 <element name="productionOrderNumber" nillable ="true" type="xsd:string"/>
 <element name="fullExplosionFlag" type="xsd:string"/>
 </sequence>
 </complexType>
 <complexType name="ProductionOrderDetailsReceipt">
 <sequence>
 <element name="errorMessage" nillable="true" type="xsd:string"/>
 <element name="valid" type="xsd:boolean"/>
 </sequence>
 </complexType>
 </schema>
</wsdl:types>
<wsdl:message name="processOrderDetailsResponse">
<wsdl:part name="podReturn" type="tns:ProductionOrderDetailsReceipt" />
</wsdl:message>
<wsdl:message name="processOrderDetailsRequest">
<wsdl:part name="input" type="tns:ProductionOrderDetailsInput" />
</wsdl:message>
<wsdl:portType name="PodService">
 <wsdl:operation name="ProcessOrderDetails" parameterOrder="input">
 <wsdl:input message="impl:processOrderDetailsRequest"
 name="processOrderDetailsRequest"/>
 <wsdl:output message="impl:processOrderDetailsResponse"
 name="processOrderDetailsResponse"/>
 </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ProdOrderDetailsSoapBinding" type="impl:PodService">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <wsdl:operation name="ProcessOrderDetails">
 <soap:operation soapAction="http://pod.service.server.mesassembly.cis.cat/NewOperation"/>
 <wsdl:input name="processOrderDetailsRequest">
 <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
 </wsdl:input>
 <wsdl:output name="processOrderDetailsResponse">
 <soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:cat.cis.mesassembly.server.service.pod" />
 </wsdl:output>
 </wsdl:operation>
</wsdl:binding>
<wsdl:service name="PodService_Service">
 <wsdl:port binding="impl:ProdOrderDetailsSoapBinding" name="ProdOrderDetails">
 <soap:address location="http:/localhost:8080/MESAssembly/services/ProdOrderDetails"/>
 </wsdl:port>
</wsdl:service>
</wsdl:definitions>

Invocation of Netweaver generated Web Service from XI

Similar Messages

Maybe you are looking for