BIweb service proxy JAX-RPC 1.1 method is not supported in WLS 8.1 clients

Hello
I have an application in oracle Application server and I'm migrating to weblogic 11g .
I have used web service proxy for BIPublisher 10.1.3.4 , careated by jdeveloper web service proxy wizard , when I want using it in weblogic , In corresponding form that uses BI Publisher web service proxy , I encounter following error :
"JAX-RPC 1.1 method is not supported in WLS 8.1 clients , if you attempting to run oc4j 10.1.3 JAX-RPC client in WLS,please see Web service Migration Guide for Instructions"
What should I do?
Regards
Mehdi

Spoke to dev and there was a bug logged, it seems to be down to Weblogic's implementation.
+This is pure WLS issue. The root cause of this problem is that Weblogic's
SAAJ implementation. No codechange on BIP server side
WLS 10 ships with two SAAJ implementations. By default the buggy 9.x
implementation is used (which lives in the package
weblogic.webservice.core.soap), but there is a new implementation, which
supports SAAJ 1.3 (which lives in the package weblogic.xml.saaj). I also
checked in a debugging jsp page, which could help looking at the DEBUG
logging to see which SAAJ implementation is used.
JSP testpage xmlponline/wwwroot/wsclient/soapclient-wls-8270711.jsp
To use this new version, you have to make sure setting the
-Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl
in startWebLogic script. +
Please give the solution a try and let me know if it works.
Regards
tim

Similar Messages

Java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

We have some web services that run under OC4J 10.1.3.4. We have various JEE 'client' apps (JSF, servlets etc.) that use these web services. These JEE apps also run under OC4J.
We started a migration project from oc4j to weblogic 10.3.2. In phase 1 we want to move these JEE 'client' apps to weblogic. In phase 2 we want to move the web services themselves to weblogic with adjustments to the JEE 'client' apps as needed.
However we ran into an issue during this phase 1. Deploying these JEE 'client' apps to weblogic results in an error like this:
java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions.
We are including Oracle web services client libraries (http://download.oracle.com/otn/java/oc4j/1013/wsclient_extended.zip) in these JEE 'client' apps's war files because weblogic does not have them.
What part of Web Service Migration Guide is the above error message talking about? Do we have to re-generate the client side proxies for all these web services using weblogic's clientgen task in 'JAXRPC' mode? Many of these web services are doc/literal jax-rpc web services. Or does the migration guide recommend we migrate the web services first to weblogic? Any other specific information on working around this error message would be greatly appreciated.

Hi,
I had the same issue but I just managed to fix it. You must upgrade and/or regenerate you proxy. This creates new classes (possibily in a new package) that you must use in your code. I had this error because the classes directory was not clean after the rebuild and the old classes (in the old package) were still present, so the compilation was successful with the old classes. So clean your classes directories, regenerate your proxy and use the new classes in your code.
Regards,
Sylvain

Jdeveloper 11g - JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

Hi,
I am using Jdeveloper 11g and migrating a web Service Proxy created using jdeveloper 10g.
I imported all the proxy classes and when I try to run web service client In Jdeveloper 11g I get the following error
"JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions."
Please advise on how to solve this?
which is the offending jar/library file in Jdeveloper 11g which is causing the above error?.
Is the above problem there in the WebLogic Server Runtime also?
Please let me know.
2) I cannot generate web server proxies also with jdev11g because the wsdl has overloaded methods omitting the name property within the input and output message, ie, they have a null name. therefore Jdeveloper 11g is using the library which
when called with an overloaded operation that contains null input/output message names, a duplicate error occurs because it sees other operations with the same name. so it is effectively not allowing to create the web service proxies.
Thanks,
Appreciate your quick response to the above

Have you checked the 'Web Service Migration Guide' mentioned in the error message?
Timo

Web Deploy error - "This method is not supported by this class"

I have an MVC project which I am trying to deploy to one of our internally-hosted web front end servers via a TFS build process. Our server hosts the MS Deploy service, and other solutions deploy without problems to the same box. The parameters for the build
process are as follows:
/p:DeployOnBuild=True /p:DeployTarget=MsDeployPublish /p:MSDeployPublishMethod=WMSVC /p:MsDeployServiceUrl=https://<server>:8172/msdeploy.axd /p:DeployIISAppPath="<internal.site.com>" /p:username=<username> /p:password=<password>
/p:IncludeIisSettingsOnPublish=false /p:AllowUntrustedCertificate=True /p:OutputPath=bin\ /p:SkipExtraFilesOnServer=True /p:VisualStudioVersion=11.0
The error message I receive at the point the build reaches the deployment activity is:
Web deployment task failed. (Could not complete the request to remote agent URL 'https://<server>:8172/msdeploy.axd?site=<internal.site.com>'.)
Could not complete the request to remote agent URL 'https://<server>:8172/msdeploy.axd?site=<internal.site.com>'.
The request was aborted: The request was canceled.
This method is not supported by this class.
We've found
this StackOverflow post which describes the same error we're experiencing, however the suggested solution is something we already do in our server configuration, so this doesn't resolve the issue for us.
Has anyone seen this error before, or is able to make any suggestions why it is happening?

Hi Matt,
You have to have a look in the build log then copy the command that is under Run MSBuild node and executed it on the build agent.
You should find something like below:
C:\Program Files (x86)\MSBuild\12.0\bin\amd64\MSBuild.exe /nologo /noconsolelogger "C:\Builds\....sln" /nr:False /fl /flp:"logfile=C:\Builds\...log;encoding=Unicode;verbosity=normal" /p:SkipInvalidConfigurations=true /p:CreatePackageOnPublish=true /p:DeployOnBuild=true /p:SkipExtraFilesOnServer=True /m /p:OutDir="C:\Builds\...\bin\\" /p:Configuration="DEV" /p:Platform="Any CPU" /p:VCBuildOverride="C:\Builds\....sln.Any CPU.DEV.vsprops" /dl:WorkflowCentralLogger,"C:\Program Files\Microsoft Team Foundation Server 12.0\Tools\Microsoft.TeamFoundation.Build.Server.Logger.dll";"Verbosity=Normal;BuildUri=vstfs:///Build/Build/31630;IgnoreDuplicateProjects=False;InformationNodeId=14;TargetsNotLogged=GetNativeManifest,GetCopyToOutputDirectoryItems,GetTargetPath;LogProjectNodes=True;LogWarnings=True;TFSUrl=http://...-tfs:8080/tfs/...;"*WorkflowForwardingLogger,"C:\Program Files\Microsoft Team Foundation Server 12.0\Tools\Microsoft.TeamFoundation.Build.Server.Logger.dll";"Verbosity=Normal;" /p:BuildId="aa2d3857-27e9-4854-b44f-4ca625ccd786,vstfs:///Build/Build/31630" /p:BuildLabel="..._2015.02.27.2" /p:BuildTimestamp="Fri, 27 Feb 2015 11:16:41 GMT" /p:BuildDefinition="..."
Daniel

This method should not be called anymore. The client was already released i

Hi,
while configuring Business Packager for Projects 50.3 fo, we made few changes in R/3 side as per the documentation. after that we are getting following error in portal
"This method should not be called anymore. The client was already released into the pool or the pool entry was deleted"
all the chages were reverted in R/3 system still we are getting the same error.
Can any one help on this issue....
Thanks in advance and for early responce higher marks would be awarded!!!..
Regards
Ravi Sankar Karri

Hi,
Well there were errors in how stop works:
"Stopping a thread with Thread.stop causes it to
unlock all of the monitors that it has locked (as a
natural consequence of the unchecked ThreadDeath
exception propagating up the stack). If any of the
objects previously protected by these monitors were in
an inconsistent state, the damaged objects become
visible to other threads, potentially resulting in
arbitrary behavior. "
I do understand that you want to have something like
killTheTreadIDontCareAboutConcequences-method, but
it's better to let all your methods that you want to
be able to terminate take a timeout argument, and deal
with the termination in the method. (Close the
sockets/streams etc that you are blocking on).
/KajThe point is, it is not always possible to make those blocking methods stop, via some magic "timeout" thingamabob. The bottom line is still that the blocking methods were written incorrectly to begin with (to possibly block indefinitely), so one cannot come up with an across-the-board solution, other than getting the root cause fixed in the first place. However, one is not always in control of fixing the root cause.

GetCollectionMetaData: this method is not supported by 'OracleXMLDataSetGenJdbc' cla

The following Java code:
// Create an OracleOCIConnectionPool instance with default configuration
OracleOCIConnectionPool cpool = new OracleOCIConnectionPool("appserver", "9ias", url, null);
// Print out the default configuration for the OracleOCIConnectionPool
System.out.println ("-- The default configuration for the OracleOCIConnectionPool --");
displayPoolConfig(cpool);
// Get a connection from the pool
OracleOCIConnection conn1 = (OracleOCIConnection) cpool.getConnection("usecase", "uml");
// Create a Statement
Statement stmt = conn1.createStatement ();
// Select the ENAME column from the EMP table
ResultSet rset = stmt.executeQuery ("select * from usecases_ov");
OracleXMLQuery q = new OracleXMLQuery(conn1,"select * from usecases_ov");
System.out.println(q.getXMLString());
Produces:
-- The default configuration for the OracleOCIConnectionPool --
Min poolsize Limit: 1
Max poolsize Limit: 1
Connection Increment: 0
NoWait: false
Timeout: 0
PoolSize: 1
ActiveSize: 0
<?xml version = '1.0'?>
<ERROR>oracle.xml.sql.OracleXMLSQLException: getCollectionMetaData: this method is not supported by 'OracleXMLDataSetGenJdbc' class. Please use 'OracleXMLDataSetExtJdbc' instead.</ERROR>
Any Suggestions?

One import piece of info: This OracleXMLQuery works against a standard table. The query that fail goes against the following view and uses nested tables(object lists).
SELECT v.name as PACKAGE,
u.name,
u.version,
u.iteration,
u.summary,
u.events_basic,
u.author,
u.rev_date,
u.ext_points,
u.assumptions,
u.preconditions,
u.revision_notes,
u.trigger_event,
u.package as PUID,
u.ALTERNATE_PATHS AS ALTERNATE_PATHS_LIST,
u.EXCEPTION_PATHS AS EXCEPTION_PATHS_LIST,
u.BUSINESS_RULES AS BUSINESS_RULE_LIST
FROM USECASE u, DESIGN_PACKAGE v
WHERE u.package=v.puid
AND EXISTS(SELECT 'X'
     FROM DESIGN_CUR_VER d
     WHERE d.name = u.name
     AND d.version = u.version
     AND d.design_date = u.rev_date)
AND EXISTS (SELECT 'X'
     FROM USECASE_AUDIT a
     WHERE a.package = u.package
     AND a.name = u.name
     AND a.version = u.version
     AND a.timestamp = u.rev_date
     AND a.status_code IN('created','modified','rejected'))
ORDER BY v.name, u.name

HTTP Method Post not supported by this URL

We are running WL6.0sp1 on Win2000. When we try to open a JSP page which calls
a servlet we get a "HTTP Method Post not supported by this URL". This same setup
(WL 6.0sp1 on Win2000) on another machine works absolutely fine running from the
same client. Is there any setup that needs to be done in Weblogic for this? Any
pointers on this would be appreciated.
Rgds

Normally when you get this error, your username/password is not correct.
It's not a clean way of errorhandling. I have had the same issue and after a while i noticed the password i entered was not correct.

The :pserver: access method is not supported by this port of CVS

i receive the following error when trying to connect to cvs
the :pserver: access method is not supported by this port of CVS

i receive the following error when trying to connect to cvs
the :pserver: access method is not supported by this port of CVS Use the CVS 1.11.2 from http://www.cvshome.org, sounds like you are using a version of cvs which (is maybe CVSNT) doesn't support pserver.
Rob

Last() method was not supported by "resultset type of TYPE_FORWARD_ONLY "

Hi all,
I got this exception
java.sql.SQLException: JZ0BT: The last() method is not supported for ResultSets of type TYPE_FORWARD_ONLY.
but while creating statement object i am dong like this
stmt = con.prepareCall(sql.toString(),ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY);
then also it is giving the same exception.
my bean code is like this,
try {
//Dynamically get the row size for the o/p dataset
from result set
rs.last();
System.out.println(rs);
int numrows =rs.getRow();
can anyone help me out to get the total number of rows in Resultset
Thanks in advance
Ravi

There's no easy way to do it that I know of. All you can do is iterate through and count. - MOD

GetCollectionMetaData method is not supported by OracleXMLDataSetGenJDBC

Hi,
We are in the process of migrating our Web Application from Oracle 9i to Oracle 10.1.0.5. Our Web Application runs under WebLogic 9.1 Server and uses Oracle XSQL APIs to store CLOB Data in Database. We are using ojdbc14.jar as well as xsu12.jar and other required Oracle XSQL Libraries.
We observed the following error
===============================
ORA-29532: Java call terminated by uncaught Java exception: oracle.xml.sql.OracleXMLSQLException: Invalid context handle specified. ORA-06512: at XSU.DBMS_XMLQUERY , line 178 ORA-06512: at XSU.XSU$XML_XCHANGE , line 293 ORA-29532: Java call terminated by uncaught Java exception: oracle.xml.sql.OracleXMLSQLException: getCollectionMetaData: this method is not supported by OracleXMLDataSetGenJdbc class. Please use OracleXMLDataSetExtJdbc instead. ORA-06512: at line 1
===============================
When we printed the underlying connection object class name, it appeared as "oracle.jdbc.driver.T4CConnection".
What is the cause of this issue? How to resolve this issue?

One import piece of info: This OracleXMLQuery works against a standard table. The query that fail goes against the following view and uses nested tables(object lists).
SELECT v.name as PACKAGE,
u.name,
u.version,
u.iteration,
u.summary,
u.events_basic,
u.author,
u.rev_date,
u.ext_points,
u.assumptions,
u.preconditions,
u.revision_notes,
u.trigger_event,
u.package as PUID,
u.ALTERNATE_PATHS AS ALTERNATE_PATHS_LIST,
u.EXCEPTION_PATHS AS EXCEPTION_PATHS_LIST,
u.BUSINESS_RULES AS BUSINESS_RULE_LIST
FROM USECASE u, DESIGN_PACKAGE v
WHERE u.package=v.puid
AND EXISTS(SELECT 'X'
     FROM DESIGN_CUR_VER d
     WHERE d.name = u.name
     AND d.version = u.version
     AND d.design_date = u.rev_date)
AND EXISTS (SELECT 'X'
     FROM USECASE_AUDIT a
     WHERE a.package = u.package
     AND a.name = u.name
     AND a.version = u.version
     AND a.timestamp = u.rev_date
     AND a.status_code IN('created','modified','rejected'))
ORDER BY v.name, u.name

One project with two different web services styles (JAX-RPC and JAX-WS)

Hi theres,
how come the same project doesn't support two different web services styles?
First time I create a web service proxy using the wizard, the second step is to choose between JAX-RPC and JAX-WS. After that, this step is removed from the wizard and all subsquent web services are assumed to be the same style as the first one.
Can someone explain me why?
thanks in advance,
Manuel Leiria

Hi,
yes, I think to remember that there is support for a single style only. If you need another one too then you create a new project.
Frank

J2EE Web services and JAX-RPC

Hello..
While working with J2EE web services using JDeveloper and OC4J, I noticed that it really doesn't confirm to Sun's JAX-RPC standard. The Web Service interface class does not extend the "Remote" and all methods don't throw "RemoteException" as mandated by JAX-RPC standard.
I have few questions:
(1) Are the OC4J J2EE web services completey different from JAX-RPC based web services.??
(2) Does Oracle have any implementation of JAX-RPC??
(3) Is Sun the only one promoting and implementing the JAX-RPC standard? Or are there other players?
thanks...

(1) Are the OC4J J2EE web services completey different from JAX-RPC based web services.??
OC4J J2EE Web Services originate from Oracle/Apache SOAP with several differences:
a. A model where each type of implementation gets a specific servlet (e.g. one for EJB's, one for PL/SQL, one for stateless and stateful Java classes. Architecturally, you can see the picture here:
http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/b10004/orawebservices.htm#1024808
(scroll down a half page for the picture)
b. The packaging of the Web services rather than using the Apache SOAP registration mechanism uses something closer to JSR 109 (also known as Web Services for J2EE, part of J2EE 1.4 with JAX-RPC, SAAJ [SOAP API forAttachments in Java] and JAXP [Java API for XML Parsing]), where the Web service is packaged as an ordinary ear file for deployment.
Oracle built this implementation by extrapolating from the JAX-RPC documentation that was available last year before it was a final specification in an effort to release a production quality Web services implementation that was aligned with JAX-RPC. It has been through two releases - Oracle9iAS 9.02 and Oracle9iAS 9.0.3 and is now being evolved to JAX-RPC as we move to J2EE 1.4.
(2) Does Oracle have any implementation of JAX-RPC??
We are planning to release a JAX-RPC implementation in the new year (I don't have specific dates yet) on OC4J. The production implementation of this will be as seamless a migration as possible from the existing implementation. Oracle9i JDeveloper will also add support for JAX-RPC as a 3rd option in its list of choices available. You can get a sense of how such a migration would work by running the Web services wizard in JDev for Apache SOAP and then, in a separate project, running it for Oracle9iAS J2EE Web Services - imagine there being another option for JAX-RPC. The work to migrate should be as simple as running a wizard or command line utility (known as the Web Services Assembler tool in Oracle9iAS).
(3) Is Sun the only one promoting and implementing the JAX-RPC standard? Or are there other players?
Pretty much every one in the Java side of industry will be implementing JAX-RPC. The important time to note is when J2EE 1.4 is released ... sometime in the new year ... I believe around March but may be mistaken. Part of J2EE 1.4 is required support for JAX-RPC, SAAJ, Web Services for J2EE etc etc. This will standardize the implementation of Web services. Oracle, like others in the industry, supports the standard protocols, (SOAP), interfaces (WSDL) and registries (UDDI) - what J2EE 1.4 does is standardize the packaging, deployment and implementation (the wrappers generated by the tooling).
My guess is that around JavaOne (June 2003) there will be a rash of announcements from J2EE vendors announcing support of JAX-RPC and J2EE 1.4 (or early implementations) as we will be in the same race that happened in 2001/2002 when J2EE 1.3 was the spec to announce implementations around.
Mike.

Problem verify web services HelloWorld JAX-RPC

I have executed the tutorial Jax-RPC HelloWorld,
but when I verify the web service my browser display
A Web Service is installed at this URL.
This endpoint is incorrectly configured. Please check the location and contents of the configuration file.
which it is the problem?
you can help me?
thanks

Check if the endpoint property of the build.properties file
(ex. endpoint=...ttp://localhost:8080/SmsWSservice/SMS/SmsWSIF)
matches exactly (is case sensitive) the url pattern element content (ex. <servlet-mapping>
          <servlet-name>JAXRPCEndpoint</servlet-name>
          <url-pattern>/SMS/*</url-pattern>
     </servlet-mapping>) of the web.xml file.
In the examples above the url-pattern "SMS" must match the part of the URL between "...ttp://localhost:8080/SmsWSservice/" and the reference of the interface ("SmsWSIF).
Hope it helps

JAX-RPC 9.0.4 --- Data Types Supported

Hi,
does any body know is java.util.List is a supported Datatype on OC4j 9.0.4.2 for JAX-RPC.
Cheers
Gaurav

Gaurav,
Not sure which version of JAX-RPC you are intended to run on top of 9.0.4.2 ?
In any way, if you want your service to work with the majority of the clients, you need to focus on the XML types; not the java types.
To my knowledge, the List will be mapped to a proprietary type, at best, which make it harder to re-use.
All the best,
Eric

Unable to call the service using JAX-RPC

Hi,
I created a web service in Weblogic6.1 using the ant wsgen utility.
When i tried to invoke the service using my client program, i get the following error.
Exception in thread "main" modeler error: model error: invalid entity name: "string" (in namespace: "http://www.w3.org/1999/XMLSchema"
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:137)
at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:77)
at com.sun.xml.rpc.client.dii.ServiceInfoBuilder.getModel(ServiceInfoBuilder.java:96)
at com.sun.xml.rpc.client.dii.ServiceInfoBuilder.buildServiceInfo(ServiceInfoBuilder.java:59)
at com.sun.xml.rpc.client.dii.ConfiguredService.<init>(ConfiguredService.java:44)
at com.sun.xml.rpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:32)
at JAXRPCClient.main(JAXRPCClient.java:20)
CAUSE:
model error: invalid entity name: "string" (in namespace: "http://www.w3.org/1999/XMLSchema")
at com.sun.xml.rpc.processor.schema.InternalSchemaBuilder.buildTypeDefinition(InternalSchemaBuilder.java:61)
at com.sun.xml.rpc.processor.schema.InternalSchema.findTypeDefinition(InternalSchema.java:45)
at com.sun.xml.rpc.processor.modeler.wsdl.SchemaAnalyzer.schemaTypeToSOAPType(SchemaAnalyzer.java:66)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.processSOAPOperationRPCStyle(WSDLModeler.java:592)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.processSOAPOperation(WSDLModeler.java:423)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.processPort(WSDLModeler.java:344)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.processService(WSDLModeler.java:231)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:196)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:103)
at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:77)
at com.sun.xml.rpc.client.dii.ServiceInfoBuilder.getModel(ServiceInfoBuilder.java:96)
at com.sun.xml.rpc.client.dii.ServiceInfoBuilder.buildServiceInfo(ServiceInfoBuilder.java:59)
at com.sun.xml.rpc.client.dii.ConfiguredService.<init>(ConfiguredService.java:44)
at com.sun.xml.rpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:32)
at JAXRPCClient.main(JAXRPCClient.java:20)
CAUSE:
invalid entity name: "string" (in namespace: "http://www.w3.org/1999/XMLSchema")
at com.sun.xml.rpc.wsdl.framework.AbstractDocument.find(AbstractDocument.java:110)
at com.sun.xml.rpc.processor.schema.InternalSchemaBuilder.buildTypeDefinition(InternalSchemaBuilder.java:54)
at com.sun.xml.rpc.processor.schema.InternalSchema.findTypeDefinition(InternalSchema.java:45)
at com.sun.xml.rpc.processor.modeler.wsdl.SchemaAnalyzer.schemaTypeToSOAPType(SchemaAnalyzer.java:66)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.processSOAPOperationRPCStyle(WSDLModeler.java:592)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.processSOAPOperation(WSDLModeler.java:423)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.processPort(WSDLModeler.java:344)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.processService(WSDLModeler.java:231)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:196)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:103)
at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:77)
at com.sun.xml.rpc.client.dii.ServiceInfoBuilder.getModel(ServiceInfoBuilder.java:96)
at com.sun.xml.rpc.client.dii.ServiceInfoBuilder.buildServiceInfo(ServiceInfoBuilder.java:59)
at com.sun.xml.rpc.client.dii.ConfiguredService.<init>(ConfiguredService.java:44)
at com.sun.xml.rpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:32)
at JAXRPCClient.main(JAXRPCClient.java:20)
My wsdl file is
- <definitions targetNamespace="java:com.mountain.molehill.ejb.controller" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:tns="java:com.mountain.molehill.ejb.controller" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
- <types>
<schema targetNamespace="java:com.mountain.molehill.ejb.controller" xmlns="http://www.w3.org/1999/XMLSchema" />
</types>
- <message name="getPointBalanceRequest">
<part name="arg0" type="xsd:string" />
</message>
- <message name="getPointBalanceResponse">
<part name="return" type="xsd:string" />
</message>
- <portType name="WSManagerPortType">
- <operation name="getPointBalance">
<input message="tns:getPointBalanceRequest" />
<output message="tns:getPointBalanceResponse" />
</operation>
</portType>
- <binding name="WSManagerBinding" type="tns:WSManagerPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="getPointBalance">
<soap:operation soapAction="urn:getPointBalance" />
- <input>
<soap:body use="encoded" namespace="urn:WSManager" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
- <output>
<soap:body use="encoded" namespace="urn:WSManager" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
- <service name="WSManager">
<documentation>todo</documentation>
- <port name="WSManagerPort" binding="tns:WSManagerBinding">
<soap:address location="http://blrkec17805:7001/WS/rpc_URI" />
</port>
</service>
</definitions>
Could anybody help me in resolving this problem?
Thanks in advance,
Rajadurai

Hello,
edit the wsdl file and change 'http://www.w3.org/1999/XMLSchema' to 'http://www.w3.org/2001/XMLSchema' for both xmlns:xsd and xmlns then try again.
Andre

BIweb service proxy JAX-RPC 1.1 method is not supported in WLS 8.1 clients

Similar Messages

Maybe you are looking for