Document Create web service

Good day,
Does anyone know how to use the ECC_DOCUMENTCRTRC1 web service for attaching documents?
Thanks,
Shaun

Hi Shaun,
regarding this question I remeber that I worked on a similar SAP support ticket from you. During this ticked the issue could be solved and you provided me the following information:
I found a solution to the problem.
It has to do with the raw data encoding I am sending to the proxy class.
When I fixed it it worked.Can you kindly return this message so that I can close it.
So could you please inform us if this issue got solved and maybe explain the solution a bit more detailed for all other users of the forum too.
Best regards,
Christoph

Similar Messages

How do I create a "document-centric" Web Service?

By document-centric I'm talking about receiving a SOAP message on the server-side, where the initial parsing and security processing (this aspect is very important) is performed but then allowing the developer to access the delivered "payload", i.e. the XML, and perform whatever mapping/processing that is required without automatically mapping to the "standard" auto-generated Java objects.
It is important that the client receives the "full" complex WSDL and can therefore generate their proxy classes with whatever tool (or language) that is appropriate.
On the server side we do not want to create hundreds (if not thousands) of Java Bean clases as we already have the legacy code to map XML to Java. The idea is that JAX-RPC only instantiates the SOAPElements that represent the "raw" message, or, if possible, doesn't instantiate any objects whatsoever.
I've spent many days now trying to find a single well-worked example for this type of Web Service without success - many, many references of the style "..and you can then create a document style web service.." but without the all important "how".
From what I've read a custom type-mapping and/or serializer/deserializer could be the answer but again no good, solid examples are forthcoming.
Another alternative seems to be to create the server side stub-classes using a "dummy" WSDL with the elements set to "anyType" but then distribute the "genuine" WSDL to the clients - we've got a simple example of the kind working but I don't like the idea of "tricking" the system in this way.
I'm working with WASD 5.1, which in theory conforms with JAX-RPC so any ideas offered here should also apply in that environment.
Has ANYONE successfully created a service of this type?
Any help with this issue would be very much appreciated and rewarded (with Duke Dollars of course).
Chris.

Chris,
I too noticed that most vendors take the RPC centric approach. Its because most of the industry examples of how WSs were used were simple enough to implement using RPC and anything more (document literal) would add to the complexity of implementation. This is something that is feared by many developers, especialy the .Net crowd who seem to want everything done through a wizard menu interface and don't care about other WS implementations at all.
This is sort of changing. J2EE 1.4 is WS-I compliant, so when you compile server side ties from WSDL you can specify a document literal option and WS-I compliance. This gives you access to the SOAPElement objects. There's still issues with going between W3C DOM and SOAP elements but that's just API inconvenience, not a show stopper. As the inudustry develops more complex WSs we will see the vendors change their tools to better support this...
Anyway, some more help...
I use the the following wscompile options to build from WSDL for document literal WSs.
wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -import config.xml
wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -gen:server config.xml
My "wrapper" elements look like this...
<xs:element name="AComplexXMLResponse">
     <xs:complexType>
          <xs:sequence>
               <xs:element ref="myNS:MYComplexXMLType"/>
          </xs:sequence>
     </xs:complexType>
</xs:element>
If I do this:
<xs:element name="ASimpleXMLResponse">
     <xs:complexType>
          <xs:sequence>
               <xs:element name="AName" type="xs:string"/>
          </xs:sequence>
     </xs:complexType>
</xs:element>
I still get the JAXRPC language bindings to a string, but in my case I don't really care. This may well be different for you.
What I do to manage these elements is to split up the WSDL, WS wrapper element definitions and actual data XML schema definitions into separate documents. This means I have a WSDL which IMPORTS my message schema (this is where I define wrappers for in and out XML) which INCLUDES the actual DATA XML schema that I have.
The WSDL import looks like this:
<types>
     <xs:schema>
          <xs:import namespace="http://schemaURI" schemaLocation="./relativePath/WrapperElementSchema.xsd"/>
     </xs:schema>
</types>
The wrapper element schema has:
<xs:include schemaLocation="./ActualDataSchema.xsd"/>
This way I can easily replace the wrapper documents with just anyType references if something doesn want to play nice. The data schema file and the WSDL stay the same. This minimises the impact on what you have to change in your distribution. This is important as the WSDL is often generated on the fly by your WS environment and so can not be easily changed once you build your WSs, but the schema files it references are easily changed without affecting your code.
Another reason for the wrapper elements was a JWSDP 1.2 issue (I don't know if this has been fixed in 1.3), where if you had the same method parameter signature in a web service (the parameters it took were the same XML types, for instance if you have an add and update methods for the same document input) JWSDP would get confused at runtime. It did not take account of the SOAP action that came along with the request to determine which operation to call. It just took the incoming XML, saw that it was of a certain type and it passed it to the first operation that took this element, which is VERY wrong. By using the wrapper elements, I could give all my input and output elements for each method different names (I used a naming stragegy that appended a 'request' or 'response' string to the method name to form a method parameter element name. This is a pain in the ass, but works and does wonders for interoperability with other WS vendors. Like I said before, I've got this working with JWSDP, BEA and .Net servers and clients.
Hope this helps,
If you think there is a real need for a public HOWTO on this, I could write one with a full step by step guideline that shows where I broke my legs getting this stuff to work. But this would eat into my sleep time :-/ TO JUDGE INTEREST I call on all people interested in a tutorial to respond to this thread (esp people involved with the JWSDP WS tutorial documentation). If I get 5 or more different people responding I will loose some sleep for the good of this community. Otherwise, I will just try to help you when I have time to read the forums.
Kuba

How to create document/literal web services with WLS7

How do you create document/literal web services with WLS7 ( not workshop)
- Is it possible with servicegen and stateless EJBs as the backend component?
The default is RPC/Soap-encoded is there anyway to craft the web-services.xml
to make it document/literal
- Is it possible with the JMS-implemented web services - have not tried this yet
- Is there another mechanism?

That would be the <web-service> element in the web-services.xml file, of course.
"Michael Wooten" <[email protected]> wrote:
>
Hi Rich,
Try adding a style="document" attribute to the starting <web-service>
element.
The might be a way to get <servicegen> to do this for you, but I haven't
found
it yet :-)
Regards,
Mike Wooten
"Rich Muth" <[email protected]> wrote:
How do you create document/literal web services with WLS7 ( not workshop)
- Is it possible with servicegen and stateless EJBs as the backend component?
The default is RPC/Soap-encoded is there anyway to craft the web-services.xml
to make it document/literal
- Is it possible with the JMS-implemented web services - have not tried
this yet
- Is there another mechanism?

How to create Web Service based on PI WSDL message

Hi all,
we have following scenario:
Within PI (version 7.1) we set up a message type and inbound service interface. This service interface should send the PI message to a web service running on a SAP J2EE (version 7.01). As the PI message is sent as WSDL I thought it should be easy to build a web service on the SAP J2EE based on this WSDL from PI.
Unfortunately, I have problems creating the Web Service.
For my current project we integrated the NWDI to the SAP NetWeaver Developer Studio and I'm required to add the Web Service to an existing DC (Development Component) within the NWDI.
What I tried so far is:
- I created a Deployable Proxy Project and within this I created a Client Proxy Definition based on the WSDL from the PI. But I can't add this Proxy to the DCs of the NWDI and I don't know how to implement my own coding here in order execute specific functions.
- I created a new class within the NWDI DC and a public method. Based on this I created a Virtual Interface and a Web Service Definition (WSD). Then I added this to a Web Service Deployment Descriptor. I uploaded this to the SAP J2EE. But I'm not able to access this and I don't know hoe to assign the WSDL here.
I also tried here to create a client proxy based on this WSD as I thought I might assign the WSDL here. But I don't see the WSD in the list of Web Services uploaded to the SAP J2EE...
Can you please advice me how to create a Web Service in such an environment?
regards
René Jurmann

Hi Tahir,
sorry that you needed to wait this long - but this is how I created the web service:
The steps on how to create the web service in NetWeaver Developer studio are nearly the same as described in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5838. [original link is broken] [original link is broken] [original link is broken]
Some steps I just skipped and some others I added. Some of the steps I did the way I described it as I needed to connect the web service with the SAP PI.
Prerequisites:
Add Java Perspective and J2EE Development Perspective to the open perspectives.
Within "Window - Preferences - Web Services" check "Soap extensions visible in the virtual interface editor"
The SDM of the corresponding SAP J2EE is configured within "Window - Preferences"
Create a Development Component (DC) with type "J2EE -> EJB Module"
The business logic of the web service will be implemented in an Enterprise Java Bean (EJB). So first the EJB component must be created:
     Choose "File -> New -> Other"
     In opening PopUp choose "Development Component -> Development Component Project"
     Select the Software Component for which you want to add the DC (e.g. "Local Development -> MyComponents")
     Choose now vendor, name and type:
          vendor is an alpha-numeric string of 20 characters starting with a letter - all in lower case
          name is an alpha-numeric string starting with a letter - all in lower case
          vendor and name concatenated must not be longer then 40 characters
          the name can be separated into different part using "/" as separator
          each part of the name must not be longer than 8 characters
          the type is "J2EE - EJB Module"
          you can specify a Caption as general description for the web service
Create new EJB
To create the EJB itself:
     In J2EE DC Explorer of J2EE Development Perspective expand new DC and right-click on folder "ejbModule"
     Choose "New - EJB" with following details:
          EJB Name: <name as for PI service Interface to be created - starting in upper case>
          EJB Project: <pre selected>
          Bean Type: Stateless Session Bean
          Default EJB Package: <corresponds to namespace in PI>
          generate default interfaces: Checked
Regarding the "Default EJB Package" this should be created according the namespace in PI for which all PI objects will be created. This only applies if you have some naming conventions here.
Example:
Namespace in PI is: http://company.net/pi/SOFTWARE_COMP/Application
The corresponding package then is: net.company.pi.software_comp.application
Implement coding for web service
As the web service will be called via PI some transfer variables will be submitted. Most likely, those variables will not be standard type (e.g. String) but a complex type. Those types must be generated as Java classes. Below an example of a complex type I needed:
Data Type
net.company.pi.software_comp.application.types.MessageProcessingInformation
Structure:
     Element name          Element type
     sendingSystemID          String
     interfaceID               String
     businessProcessVariantCode     String
     testIndicator               Boolean
For every element described a public "get", "set" and "has" method must be created in the corresponding Java class:
package net.company.pi.software_comp.application.types;
import java.io.Serializable;
public class MessageProcessingInformation implements Serializable {
     protected String sendingSystemID;
     protected String interfaceID;
     protected String businessProcessVariantCode;
     protected Boolean testIndicator;
     public String getSendingSystemID() {
          return sendingSystemID;
     public void setSendingSystemID(String value) {
          this.sendingSystemID = value;
     public boolean hasSendingSystemID() {
          if(sendingSystemID != null && !sendingSystemID.equals("")){
               return true;
          return false;
All Java classes representing complex types and all classes referenced here (used for sub-types) must implement java.io.Serializable. Java standard types which do not implement this class must not be used as sub-types.
As soon as all data types are declared the real business logic can be implemented:
     In J2EE DC Explorer of J2EE Development Perspective expand DC - "ejb-jar.xml" - <Name> and double click on "ejbCreate"
     In detail view select folder "Business Methods" and click "Add"
     choose name of business method - this should be the same as the PI message type used for the service interface - starting lower case
     return type should be "void"
     add needed parameters fully qualified - including package (as specified in PI and created previously in DC)
     you can mark certain parameters as array if necessary
Remark:
It might be that after saving you get an error. This might be as the package name of one component is copied to the corresponding Java class at the very beginning (before the package declaration within the Java class). Simply delete the string here.
It also might be, that the new business method is only defined in the remote interface class but not in the bean class. Just create an according method in the bean class.
Within the newly created business method within the bean class you can now implement the business logic.
Create a DC with type "J2EE -> Enterprise Application"
In order to create the "real" web service and deploy it to the J2EE an Enterprise Application project has to be created. So create a new DC as for the EJB Module but choose as type "J2EE -> Enterprise Application".
After the DC is created right click on the EJB DC and choose "Add to EAR Project". Choose the new DC.
Create web service for EJB
As soon as you implemented the business logic you can create the "real" web service. Therefore:
     Right click on the EJB name below "ejb-jar.xml"
     Choose "New - Web Service"
     Choose proper "Web Service Name" and "Configuration Name" (probably oriented at the EJB name)
     Copy the URL of the web service - you'll need it later for PI configuration
     on the second next screen use the same name for "Virtual Interface" and "Web Service Definition" (the name should be the name of the "Endpoint")
     the "EAR Project" should be preselected
Unfortunately, the web service can't be used in its current configuration to be accessed by PI. Therefore the Virtual Interface must be changed. To do so, expand folder "Virtual Interfaces" and double click the virtual interface created.
Within the detail view expand in tabs "Mapping" and "Types" the complete folder structure. For any "SOAP Extension" where a namespace can be defined use as namespace the corresponding namespace in PI (e.g. http://corpintra.net/pi/CBFC_GLOBAL_SAP_APPL/BillerDirect) but do not change any "Soap Extension" of a standard Java type. (if you don't have any naming convetions for namespaces in PI you can leave the SOAP Extension here. But then the namespace in PI should be set accordingly.)
Probably it can be necessary on top level "Soap Extensions" in tab "Mapping" to leave "Use Namespaces for Parameters" unchecked. For some of my web services this parameter must be checked for others not - just try.
If you can define a "New Name", "Local Name" or "Item Label" for a Soap Extension then use a name with starting upper case letter. (For Java Naming conventions most of the data type names will start with lower case letters.) Especially the method name must be renamed this way in order to stick to the PI namings.
As a last point to change here check in tab "Mapping" all "Incoming Parameters" which you specified as array. Use for those as "New Name" a different name - do not just simply change from lower case to upper case. This is necessary as on PI we need to create two levels although here only one is specified.
For any own sub-type declared as array the name within the coding should also differ from the corresponding Java Class name the type refers to.
If all this is done you can deploy the web service to the J2EE:
     right click on "Enterprise Application" DC and choose "Development Component - Build..." and build all corresponding components
     right click on "Enterprise Application" DC and choose "Development Component - Deploy"
Test the new web service via <J2EE URL>/wsnavigator/enterwsdl.html
Create PI interface
After the web service is created successfully the PI integration can be started.
Therefore, within the Enterprise Services Builder create a data type according to the web service definition. All components defined on top-level for this data type should be declared as incoming parameter for the web service business method. Therefore it could be necessary to create some sub data types on PI first and add those to the "master" data type.
Ensure that the names of the components correspond to the names defined in the web service (see virtual interface here). Those names must exactly be the same - including lower/upper case. Also take care for the ordering of the components.
In case you need to include arrays following applies:
The upper level is of occurrence "1:1". This has only one sub-entry with occurrence "1:n". The names for upper and sub-level must not equal.
Based on the data type a message type is created. The name of the message type must be exactly the same as the name of the web service business method. (Hint: the name of the web service business method was most likely changed in the virtual interface. Then this name must correspond to the message type name.) Based on the message type an asynchronous inbound interface is to be created (which will be referred in the Integration Directory). The operation name for this interface (left panel) should be the same as the name for the web service business method.
Create PI mappings and routings
How to map (message mapping and operation mapping) from source to the web service message I wont explain here as this depends on the source message. The only important things here are:
     When creating the SOAP communication channel within the Integration Builder the "Target URL" is:
          <J2EE URL>/<Access URL as specified in web service creation>?wsdl&style=document
     The soap action is the name of the web service business method.
     Most likely the web service needs authentication to be executed.

Error while creating web service reference

Hi,
I have very limited knowledge of web services. we have a BPEL implementation and I have been handed location to 3 wsdl files for which I am trying to create a web service reference(under shared component->logic) in apex(3.1.1). I am successfully able to create for 1 wsdl but for other two i get the below error.
"1 error has occurred
The WSDL document contains multiple SOAP bindings. Application Express only supports WSDL's with one SOAP binding. Click Create Web Service Reference Manually to continue creating a reference for this service."
looking at the working and not working wsdls, i see the following difference. i collapsed all the xml tags in the wsdl file and found that the one that is not working and giving above error has the below two tags twice with data in it.
<wsdl:portType name=
<wsdl:binding name=
any help to parse this wsdl in APEX be greatly appreciated.
thanks,
khan

I have just read that " APEX does not support multiple binding web services currently" at http://oraclebizint.wordpress.com/category/apex/
..still reading it. though the post is dated back in 2008, I wonder why this functionality wasn't added to Apex.

Validation error while creating Web Service Proxy.

Hi,
I'm trying to create Web Service Proxy. But I'm stuck with a Validation error
model error: type
+"{http://xmlns.oracle.com/2001/XMLSchema/DOM}+
+org.w3c.dom.Document" not found.+
I'm using "Create Web Service Proxy" wizard. There are 6 steps in creating proxy through JDev. wizard.
First step itself displaying the above validation error when I click on "Next" button.
Few points
We have created web service using "oracle.j2ee.ws.StatelessJavaRpcWebService" servlet
Thanks in advance.
-Sukumar

Hi,
It might be that the .net service which you have is not WS-I compliant. Can you first run WS-I Analyzer on the wsdl to see it the test passes.
Thanks,
Vishal

Error creating web service from WSDL in 11.1.2.0.0

Hello,
I have just installed JDeveloper 11.1.2.0.0. I tried to test a web service created (and successfully tested) in 11.1.1.5.0. The service is deployed to internal WebLogic server but when I call "Test Web Service" this is the error I get:
The Web Service Tester cannot be invoked, because the WSDL document of the selected service cannot be read.
java.lang.IllegalStateException: SSLContextImpl is not initialized
     at com.sun.net.ssl.internal.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:145)
     at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
     at oracle.jdevimpl.credential.LazySSLContextSpi.engineGetSocketFactory(LazySSLContextSpi.java:67)
     at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getNewReaderInstance(CachedWSDLReader.java:398)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:298)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:294)
     at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:141)
     at java.lang.ThreadLocal.get(ThreadLocal.java:131)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getReaderImpl(CachedWSDLReader.java:308)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLInternal(CachedWSDLReader.java:531)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLDirect(CachedWSDLReader.java:471)
     at oracle.jdevimpl.webservices.tcpmonitor.ServiceTester$3.run(ServiceTester.java:262)
     at java.lang.Thread.run(Thread.java:662)
Then I tried to create a new project and Java web service from WSDL, but on the second step of the "Java Web Service from WSDL" wizard when I select WSDL file from the disk and click "Next" I get
java.lang.IllegalStateException: SSLContextImpl is not initialized
java.lang.IllegalStateException: SSLContextImpl is not initialized
     at com.sun.net.ssl.internal.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:145)
     at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
     at oracle.jdevimpl.credential.LazySSLContextSpi.engineGetSocketFactory(LazySSLContextSpi.java:67)
     at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getNewReaderInstance(CachedWSDLReader.java:398)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:298)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:294)
     at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:141)
     at java.lang.ThreadLocal.get(ThreadLocal.java:131)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getReaderImpl(CachedWSDLReader.java:308)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLInternal(CachedWSDLReader.java:531)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDL(CachedWSDLReader.java:484)
     at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDL(CachedWSDLReader.java:455)
     at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel.fetchWSDL(SpecifyWsdlPanel.java:1050)
     at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel$1.run(SpecifyWsdlPanel.java:364)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
     at java.lang.Thread.run(Thread.java:662)
I performed fresh install of this new JDeveloper version in new Middleware home with all the default options and this is the first thing I tried.
Any hints?
Thanks,
Bruno

Hi Vishal,
no, I don't see any HTTPS security settings defined. The thing is that this worked just fine in 11.1.1.5.0 version. I installed 11.1.2.0.0 and the first thing I tried was testing this web service. Right away I get this error. I also tried creating Web Service Client Proxy for this web service and I get the same exception. I looks to me that this happens when wizard tries parsing WSDL...
But, I got another error when I opened "Java Web Service Editor" for this web service and selected "Methods":
NPE in o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel:702
Performing action (35) Project Properties... [ from ProjectNavigatorWindow ] [ for ( VegaService.jpr, VegaService.jpr, DMSVegaAdapter.jws ) ]
oracle.jdevimpl.webservices.index:Jun 9, 2011 9:05:02 AM IndexFacade runQuery
INFO: Having to guess workspace
oracle.jdevimpl.webservices.index:Jun 9, 2011 9:05:28 AM IndexFacade runQuery
INFO: Having to guess workspace
Performing action (23) Find... [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
Performing action (56) Properties... [ from ProjectNavigatorWindow ] [ for ( VegaService, VegaService.jpr, DMSVegaAdapter.jws ) ]
oracle.jdevimpl.webservices.index:Jun 9, 2011 9:09:32 AM IndexFacade runQuery
INFO: Having to guess workspace
java.lang.NullPointerException
java.lang.NullPointerException
o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel.populateListImpl(SelectMethodsPanel.java:702)
o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel.access$600(SelectMethodsPanel.java:82)
o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel$4$1.run(SelectMethodsPanel.java:603)
j.a.event.InvocationEvent.dispatch(InvocationEvent.java:209)
j.a.EventQueue.dispatchEventImpl(EventQueue.java:642)
j.a.EventQueue.access$000(EventQueue.java:85)
j.a.EventQueue$1.run(EventQueue.java:603)
j.a.EventQueue$1.run(EventQueue.java:601)
j.security.AccessController.doPrivileged(Native Method)
j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
j.a.EventQueue.dispatchEvent(EventQueue.java:612)
o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:178)
j.a.Dialog$1.run(Dialog.java:1046)
j.a.Dialog$3.run(Dialog.java:1098)
j.security.AccessController.doPrivileged(Native Method)
j.a.Dialog.show(Dialog.java:1096)
j.a.Component.show(Component.java:1585)
j.a.Component.setVisible(Component.java:1537)
j.a.Window.setVisible(Window.java:842)
j.a.Dialog.setVisible(Dialog.java:986)
o.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:395)
o.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:356)
o.i.dialogs.WizardLauncher.runDialog(WizardLauncher.java:55)
o.i.panels.TDialogLauncher.showDialog(TDialogLauncher.java:225)
o.ji.webservices.wizard.jaxrpc.WebServicesEditor.showDialog(WebServicesEditor.java:313)
o.ji.webservices.WebServicesAddin.findAndInvokeWizard(WebServicesAddin.java:1672)
o.ji.webservices.WebServicesAddin.handleEvent(WebServicesAddin.java:870)
o.i.controller.IdeAction$ControllerDelegatingController.handleEvent(IdeAction.java:1469)
o.i.controller.IdeAction.performAction(IdeAction.java:662)
o.i.controller.IdeAction.actionPerformedImpl(IdeAction.java:1140)
o.i.controller.IdeAction.actionPerformed(IdeAction.java:617)
jx.s.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
jx.s.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
jx.s.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
jx.s.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
jx.s.AbstractButton.doClick(AbstractButton.java:357)
jx.s.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:809)
jx.s.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:850)
j.a.Component.processMouseEvent(Component.java:6289)
jx.s.JComponent.processMouseEvent(JComponent.java:3267)
j.a.Component.processEvent(Component.java:6054)
j.a.Container.processEvent(Container.java:2041)
j.a.Component.dispatchEventImpl(Component.java:4652)
j.a.Container.dispatchEventImpl(Container.java:2099)
j.a.Component.dispatchEvent(Component.java:4482)
j.a.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
j.a.LightweightDispatcher.processMouseEvent(Container.java:4238)
j.a.LightweightDispatcher.dispatchEvent(Container.java:4168)
j.a.Container.dispatchEventImpl(Container.java:2085)
j.a.Window.dispatchEventImpl(Window.java:2478)
j.a.Component.dispatchEvent(Component.java:4482)
j.a.EventQueue.dispatchEventImpl(EventQueue.java:644)
j.a.EventQueue.access$000(EventQueue.java:85)
j.a.EventQueue$1.run(EventQueue.java:603)
j.a.EventQueue$1.run(EventQueue.java:601)
j.security.AccessController.doPrivileged(Native Method)
j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
j.a.EventQueue$2.run(EventQueue.java:617)
j.a.EventQueue$2.run(EventQueue.java:615)
j.security.AccessController.doPrivileged(Native Method)
j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
j.a.EventQueue.dispatchEvent(EventQueue.java:614)
o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
j.a.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
j.a.EventDispatchThread.run(EventDispatchThread.java:122)
Regards,
Bruno

AxisFault seen while invoking document style web service

I am seeing the following stacktrace when I try to invoke a document-style web service.
<partnerRole name="MyWebService1_Role">
<ServiceName>{http://idm.oracle.com/}MyWebService1</ServiceName>
<PortType>{http://idm.oracle.com/}MyWebService1</PortType>
<Address>null</Address>
</partnerRole>
<conversationId>bpel://localhost/default/ProvisioningFromDAS~1.0/4202-BpInv0-BpSeq0.3-3</conversationId>
<properties>{}</properties>
</partnerLink>
<2005-09-06 09:23:37,650> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:caught exception while handling request: expected element is missing: {http://idm.oracle.com/}attribute
at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
What could this mean ?

Hi,
I am getting a similar issue. I created a Document-style/literal webservice and deployed on Weblogic 9.2 . Then I generated client stubs using clientgen. I get the following exception stack trace:
java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SOAPException:
failed to serialize class java.lang.Objectweblogic.xml.schema.binding.SerializationException: type mapping lookup failure on
class=class com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl TypeMapping=TYPEMAPPING SIZE=3
ENTRY 1:
class: java.lang.Object
xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocumentResponse
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@1125127
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@18dfef8
ENTRY 2:
class: java.lang.Object
xsd_type: ['http://xmlns.ozarkexpress.com/business/sell']:stns:echoDocument
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@15e83f9
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@2a5330
ENTRY 3:
class: java.lang.Object
xsd_type: ['http://www.w3.org/2001/XMLSchema']:xsd:anyType
ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@bb7465
deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@d6c16c

Creating web service from pl/sql procedure

Hello.
I need to create a web service from pl/sql procedure and i chose JDeveloper for this implementation. I have wsdl, but I never created web services. So, I created web service with document/literal message format.
But I have several troubles:
1. All element names have lower case letters.
2. The SOAP envelope must begin from words soapenv:Envelope but i have soap:Envelope.
3. And operation name has tail like "Element".
I know bad way for implement 1 and 3 points. It's a modification of java_wsdl_mapping.xml and wsdl files. But if I want to add new method to my service all changes will be cleaned. It's not critical but inconvenient to support.
But for point 3 i have no ideas.
This task is very important for me. Can somebody help me?
JDeveloper 10.1.3.3
Regards,
Aleksey

http://www.oracle.com/technology/obe/obe1013jdev/10131/wsfromplsqlpackage/devwsfrom%20plsql.htm
Frank

Queries regarding creating Web Services in Oracle EBS 11i[Workaround found]

Hi,
We have an E-Business Suite 11i installation(11.5.10.2). In our implementation we are using some of the public APIs to insert & update data in EBS tables. Earlier this was done by calling the required PL/SQL procedures through dblinks.
Now, we need to do the same by using Web Services. That is we need a Web Service which can be invoked from a different application(SAP) and the Web Service in turn will call the APIs.
I am new to Web Services/SOA and as far as I could understand from reading the documentation, we need the following:
1. Install Oracle 10g Application Server with BPEL Process Manager ONLY(Oracle AS Adapter will be installed as part of BPEL PM. The Oracle AS Adapter will connect 10gAS to EBS)
2. JDeveloper to create and deploy the BPEL process.
I have a few questions here:
1. Are the above two points the only prerequisites for what I want to achieve? Do I need to install anything else?
2. How do I expose the created Web Service? I mean how will the 3rd party application invoke this Web Service?
Answers and/or links to helpful documents awaited.
Regards,
-Sujoy
Found an alternate and more cost-effective solution. Turns out that the SAP PI/XI engine can use JDBC to connect to the Oracle DB. SAP PI/XI will host the Web Service and will internally access the API through a JDBC connection.
Edited by: Sujoy on Feb 3, 2011 7:41 PM
Edited by: Sujoy on May 16, 2012 6:49 PM

Hi Helios,
I had checked the note that you are referring to before posting here. It did provide me with a start but otherwise it wasn't a great help (also some of the links are broken) . Since I am quite new to this...I am not sure whether I am proceeding in the right direction. An example/tutorial is what would be pretty useful.
Thanks anyway!
-Regards,
Sujoy

Document style web service receive and send org.w3c.Element

All,
I have created a simple Document-oriented web service and deployed to a standalone OC4J container using the following code:
********************* Interface ***********************
import org.w3c.dom.*;
interface PrimeNumberService
//method to check the primality of the number passed in Element variable
public Element isPrime(Element e) ;
******************** Implementation *******************
@version 1.0
Development Environment : Oracle9i JDeveloper
Name of the File : PrimeNumberServiceImpl.java
Creation/Modification History :
13-Apr-2002 Created
Overview:
This class file defines methods to implement PrimeNumberWebService.
The method isPrime() is exposed by the Web Service.
import org.w3c.dom.*;
import oracle.xml.parser.v2.*;
import java.io.*;
public class PrimeNumberServiceImpl implements PrimeNumberService
public PrimeNumberServiceImpl()
* This method is exposed by the Web Service to check if the number is
* prime. It extracts the number for input element and checks if it is
* prime or not and return the output in the XML Element.
* The input element is of the form <number>23</number>
public Element isPrime(Element e)
// define an XML Element that will be returned to the client
Element processedEl=null;
try{
// get the first clild of input element
Node enode = e.getFirstChild();
//get the value of input element and parse it
String value= enode.getNodeValue();
double number = Double.parseDouble(value);
String answer=null;
// check if the input number is prime
answer = checkPrime(number);
// create element from the answer
processedEl =createElement(answer);
}catch(Exception ex){
ex.printStackTrace();
return null;
// return output to client
return processedEl;
* This method creates an XML element from the input string values and return it
* The Element is of the form <answer>value</answer>
private Element createElement(String value){
// create a Document object
Document xmldoc = new XMLDocument();
// create an element with name "answer"
Element e1 = xmldoc.createElement("answer");
// append the element to document object
xmldoc.appendChild(e1);
// create a Text object from input values and append it to above element
Text t = xmldoc.createTextNode(value);
e1.appendChild(t);
return (Element)xmldoc.getFirstChild();
* This method check if the input number is prime or not
private String checkPrime(double num){
//For a prime number mod(power(2,number),number) is equal to 2
if ( Math.IEEEremainder( Math.pow(2.0,num) ,num)==2){
System.out.println ("the number is: " + num);
return "The number " + num + " is prime";}
else{
System.out.println ("the number is: " + num);
return "The number " + num + " is not prime";}
************************ Generated WSDL ***************
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="PrimeNumberService"
targetNamespace="http://tempuri.org/PrimeNumberService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://tempuri.org/PrimeNumberService.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" >
<documentation>
WSDL for Service: PrimeNumberService, generated by Oracle WSDL toolkit (version: 1.1)
</documentation>
<types>
<schema targetNamespace="http://tempuri.org/PrimeNumberService.xsd" xmlns:tns="http://tempuri.org/PrimeNumberService.xsd" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
</types>
<message name="isPrimeOutput">
<part name="return" element="xsd:any"/>
</message>
<message name="isPrimeInput">
<part name="param0" element="xsd:any"/>
</message>
<portType name="PrimeNumberServicePortType">
<operation name="isPrime">
<input message="tns:isPrimeInput"/>
<output message="tns:isPrimeOutput"/>
</operation>
</portType>
<binding name="PrimeNumberServiceBinding" type="tns:PrimeNumberServicePortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="isPrime">
<soap:operation soapAction="urn:PrimeNumberService/isPrime"/>
<input>
<soap:body use="literal" namespace="urn:PrimeNumberService"/>
</input>
<output>
<soap:body use="literal" namespace="urn:PrimeNumberService"/>
</output>
</operation>
</binding>
<service name="PrimeNumberService">
<port name="PrimeNumberServicePort" binding="tns:PrimeNumberServiceBinding">
<soap:address location="http://hp-xeon-01:9799/primenumberws/primenumberService"/>
</port>
</service>
</definitions>
I get the following error when trying to deploy:
Error:
[Error ORABPEL-10902]: compilation failed
[Description]: XML parsing failed because "undefined part element.
In WSDL at "http://hp-xeon-01:9799/primenumberws/primenumberService?WSDL", message part element "{http://www.w3.org/2001/XMLSchema}any" is not defined in any of the schemas.
Please make sure the spelling of the element QName is correct and the WSDL import is complete.
[Potential fix]: n/a.
Please let me know what I'm doing wrong.
Regards,
Jeff

Here is the error code that I'm getting at the invoke:
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
<part name="code">
<code>Client</code>
</part>
<part name="summary">
<summary>parsing error: oracle.xml.parser.v2.XMLParseException: Expected name instead of /.</summary>
</part>
<part name="detail">
<stackTrace xmlns="http://xml.apache.org/axis/">parsing error: oracle.xml.parser.v2.XMLParseException: Expected name instead of /. at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221) at org.collaxa.thirdparty.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128) at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1083) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.collaxa.thirdparty.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:226) at org.collaxa.thirdparty.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:645) at org.collaxa.thirdparty.apache.axis.Message.getSOAPEnvelope(Message.java:424) at org.collaxa.thirdparty.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.collaxa.thirdparty.apache.axis.client.AxisClient.invoke(AxisClient.java:173) at org.collaxa.thirdparty.apache.axis.client.Call.invokeEngine(Call.java:2725) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:2708) at org.collaxa.thirdparty.apache.axis.client.Call.invoke(Call.java:1738) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeAXISMessaging(WSIFOperation_ApacheAxis.java:1902) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.invokeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1464) at com.collaxa.cube.ws.wsif.providers.axis.WSIFOperation_ApacheAxis.executeRequestResponseOperation(WSIFOperation_ApacheAxis.java:1029) at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:455) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:359) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:161) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:605) at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317) at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3501) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1906) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:101) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:186) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5604) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1301) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:117) at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:146) at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.syncCreateAndInvoke(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:483) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:489) at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:425) at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:132) at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:82) at IDeliveryBean_StatelessSessionBeanWrapper22.request(IDeliveryBean_StatelessSessionBeanWrapper22.java:479) at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:101) at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:65) at ngDoInitiate.jspService(_ngDoInitiate.java:220) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121) at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267) at displayProcess.jspService(_displayProcess.java:303) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220) at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:138) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192) at java.lang.Thread.run(Thread.java:534)</stackTrace>
</part>
</remoteFault>

Document Literal Web Service Stub Error

I am using jdeveloper 9.0.3 (necessary because we are doing OAF) and have created a Document Literal Web Service Stub. The stub runs perfectly in Jdeveloper, but when I move it to our 9iAS server (1.0.2.2.2), I get the error that it can not find the class \oracle\jdeveloper\webservices\runtime\WrappedDocLiteralStub.
On my local machine this file is located in jdev-rt.jar, which is in /jdevbin/jdev/lib. Is there a special way to package the web service so that the jar file is included? Or is there a patch I need to apply to the apps server?
Any help would be much appreciated.

I am using jdeveloper 9.0.3 (necessary because we are doing OAF) and have created a Document Literal Web Service Stub. The stub runs perfectly in Jdeveloper, but when I move it to our 9iAS server (1.0.2.2.2), I get the error that it can not find the class \oracle\jdeveloper\webservices\runtime\WrappedDocLiteralStub.
On my local machine this file is located in jdev-rt.jar, which is in /jdevbin/jdev/lib. Is there a special way to package the web service so that the jar file is included? Or is there a patch I need to apply to the apps server?
Any help would be much appreciated.

Leverage Inheritance Benefits in 'document/literal' Web Services

Greetings,
I have developed a document/literal web service that receives an object I created, say ParentObject.
I developed it under the assumption that once I create a web service for ParentObject, I'll be able to use the same web service for ChildObject as well, which is a sub-class from ParentObject. Unfortunately, it did not work.
Please correct me if I'm wrong; is it really not possible to leverage inheritance capabilities web services? And if it's not possible, what workaround(s) do you use in such scenarios when you don't want to create a new web service for each object type despite that they all have the same logic?
Your thoughts are highly appreciated.
Thanks in advance,
Ahmed Motaz

Jason, have you made any progress with CF7 and WS Security?
It doesn't seem like enough information on this is available. Is it
even possible? and how?

Problem Generating Document/Literal Web Service

Hi folks..
I am currently using JDeveloper 10.1.3 (Preview Edition) and I am having trouble getting the Create Java Web Service wizard to work correctly when generating a document/literal web service. After going through the wizard selecting the appropriate settings to generate a document/literal web service from my implementation I get the following error during generation.
oracle.j2ee.ws.common.tools.api.SeiValidationException
oracle.j2ee.ws.common.processor.modeler.rmi.RmiModeler.modelPort(RmiModeler.java:587)
oracle.j2ee.ws.common.processor.modeler.rmi.RmiModeler.buildModel(RmiModeler.java:455)
oracle.j2ee.ws.common.processor.config.ModelInfo.buildModel(ModelInfo.java:160)
oracle.j2ee.ws.common.processor.Processor.runModeler(Processor.java:76)
oracle.j2ee.ws.common.tools.wscompile.CompileTool.run(CompileTool.java:510)
oracle.j2ee.ws.tools.wsa.JavaToWsdlTool.createWSDL(JavaToWsdlTool.java:234)
oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:313)
oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:205)
oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:131)
oracle.j2ee.ws.tools.wsa.Util.processAnnotations(Util.java:77)
oracle.jdeveloper.webservices.model.java.JavaGenerator.generateWSDLFromAnnotations(JavaGenerator.java:1188)
oracle.jdeveloper.webservices.model.java.JavaGenerator.doGeneration(JavaGenerator.java:362)
oracle.jdeveloper.webservices.model.Generator.generateImpl(Generator.java:330)
oracle.jdeveloper.webservices.model.Generator.access$1000071(Generator.java:100)
oracle.jdeveloper.webservices.model.Generator$1$ReturningRunnable.run(Generator.java:250)
oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:344)
oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:526)
java.lang.Thread.run(Thread.java:534)
When I googled this error I actually get a hit for a thread here on this board, that looks VERY promising... but when I attempt to access it I get a message "Duscussion Forms Error" and I cant access it. (Very frustrating believe me.. :-)
Any help that you can give would be appreciated...
Thanks
Dave

Hi Dave,
One reason to have the SeiValidationException is when you do not follow the java bean convention for getter/setter or some of the public methods you want to expose are not throwing the right execption.
Using the command line utility genProxy [or the ant task] with the debug flag may give you some informations about the WSDL constructs WSA do not understand. Look at the following how-to to get started:
http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-ws-bottomup/doc/how-to-ws-bottomup.html
If this does not help, can you share your WSDL with us ?
Thanks,
Eric

Bug: JDeveloper 10.1.2.1.0 (1913) Cant create Web Service

Hello,
I have several java files that I usually right click on to create J2EE web services. Today I cannot create web services for any of the files, as I receive a nullpointer exception. I checked that all classes in the project compile. Specifically, I have a [main] method in the PatientWS file for which I wish to create a web service, and the class runs just fine. Based on another post, it seems the problem is with web.xml. I have deleted web.xml and it continues to get re-created so maybe it is not it. Any help will be appreciated. Please let me know if there is any other information that I need to provide.
java.lang.NullPointerException
     at oracle.jdevimpl.webservices.generator.WARGenerator.addToClassesGroup(WARGenerator.java:280)
     at oracle.jdevimpl.webservices.generator.WARGenerator.generate9iASWarFile(WARGenerator.java:261)
     at oracle.jdevimpl.webservices.generator.WARGenerator.generateWarFile(WARGenerator.java:187)
     at oracle.jdevimpl.webservices.generator.WARGenerator.generate(WARGenerator.java:162)
     at oracle.jdevimpl.webservices.generator.JAXRPCGenerator.generateNonJAXJavaService(JAXRPCGenerator.java:1852)
     at oracle.jdevimpl.webservices.generator.JAXRPCGenerator.generateNonJAXService(JAXRPCGenerator.java:1544)
     at oracle.jdevimpl.webservices.generator.JAXRPCGenerator.generateService(JAXRPCGenerator.java:223)
     at oracle.jdeveloper.webservices.JAXRPCSvcModel.saveEdit(JAXRPCSvcModel.java:1613)
     at oracle.jdeveloper.webservices.JAXRPCJavaModel.createWebServiceFromClass(JAXRPCJavaModel.java:2852)
     at oracle.jdevimpl.webservices.WebServicesAddin.handleEvent(WebServicesAddin.java:1663)
     at oracle.ide.IdeAction.performAction(IdeAction.java:649)
     at oracle.ide.IdeAction$1.run(IdeAction.java:857)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Oracle IDE     10.1.2.18.38
Business Components Version     10.1.2.18.73
UML Modelers Version     10.1.2.16.83
Versioning Support     10.1.2.16.83
WebDAV Support Version     10.1.2.16.83
Struts Modeler Version     10.1.2.6.27
Designer Generators Framework     10.1.2.7.68
CVS Client Version     (CVSNT) 2.0.51d (client/server)
ADF UIX     2.2.20
java.version     1.4.2_06
java.home     C:\jdev1012\jdk\jre
java.vm.name     Java HotSpot(TM) Client VM
java.vm.vendor     Sun Microsystems Inc.
java.vm.version     1.4.2_06-b03
user.language     en
user.region     <no value assigned>
user.name     Mobile
user.home     C:\Documents and Settings\Mobile
user.dir     C:\jdev1012\jdev\bin
os.name     Windows XP
os.version     5.1
os.arch     x86
http.proxyHost     <no value assigned>
http.proxyPort     <no value assigned>
http.nonProxyHosts     <no value assigned>
ide.patches
ide.user.dir

I got the issue resolved by deleting all deployment descriptors from the project and the web.xml.
Thanks,
Frank

Document Create web service

Similar Messages

Maybe you are looking for