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

Similar Messages

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

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

Invoking JAX-RPC service deployed in SunONE7.0 by jdk1.2/1.3 client

Hi,
Is it possible to invoke a JAX-RPC service deployed in SunONE7.0 by jdk1.2/1.3 client?. If possible what jars should the client have in order to do this?.
warm regards,
Vijay

I used tha JAX-RPC runtime jars that come with JSWDP and was able to sucessfully run the client on JDK1.3 environment. Is there a solution for JDK1.2 client?

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.

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

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

Web Service Stateless Session request using JDeveloepr 11g (JAX-RPC)

I have been trying to consume web Service by sending Stateless Session request to the system.
I generated the Java Proxy using JDeveloepr 11g, using JAX-RPC.
As it is Stateless I need to add following SOAP Header for authentication
<soap:Header>
<wsse:Security soap:mustUnderstand="1">
<wsse:UsernameToken>
<wsse:Username>[email protected]</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wssusername-
token-profile-1.0#PasswordText">adminOnDemand</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
To do this I tried clientuntcredentialprovider as suggested by most of the post online, but found of little help as the server complained of not be able to find the User Name and Password.
To add to the mess problem I hit was I was not able to View the SOAP Request or Response sent by JDeveloper hence not helping me in debugging the same
I have tried it on XML SPY by manually adding SOAP Header to the SOAP request and was able to find the response, but I have not been able to do the same using the JDeveloper 11g IDE.
I have tried HTTP Analyzer assuming it might help, but unfortunately due to the huge size of WSDL, tool hanged my PC each time I loaded it.
I know it should be fairly straight forward but just feel like missing something.
Has anybody has got this thing working ?
Regards,
Deepak

What exactly you mean that since your request is stateless you must send a Username token?
Also, can you put here the code you used to populate the UNT.
Finally, if possible, can you zip and email your wsdl, the http analyzer should be able to handle wsdls, even if they are huge.
Thanks,
Vishal

Jdeveloper 11g - Access bean value after method call.

Hi There,
I have created a command button to execute a PL/SQL method call as shown in the example: 37-11 http://download.oracle.com/docs/cd/E17904_01/web.1111/b31974/bcadvgen.htm#BABEIFAI
I have the following code, to populate a java bean in my ApplImpl class.
APIResultBean result = new APIResultBean();
// 7. Set value of dateValue property using first OUT param
result.setResultValue(st.getString(28));
// 8. Set value of stringValue property using 2nd OUT param
result.setMsgValue(st.getString(29));
System.out.println("Bean Set: " + st.getString(28) + " and: " + st.getString(29));
The java bean has the following code and is defined as a java class under my Model Controller:
package CELPAY.model;
import java.io.Serializable;
import oracle.jbo.domain.Date;
public class APIResultBean implements Serializable {
String ResultVal;
String MsgVal;
public void setResultValue(String ResultVal) {this.ResultVal=ResultVal;}
public String getResultValue() {return ResultVal;}
public void setMsgValue(String MsgVal) {this.MsgVal=MsgVal;}
public String getMsgValue() {return MsgVal;}
The procedure executes but I have no idea how to pull the out variables into a form as an output text. Ie, how do I access this bean? I have tried creating a data control, but the methods do not come through. I have also tried registering this in the adfc.-config.xml and refercing the variables.
My issue is tha the getResultValue methods are not showing in Jdevloper??
Big appreciation to any help, as I have been stuck on this all day

Duplicate {thread:id=2208612}

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

JDeveloper 11g Using EJB, JPA AND ADF DOES NOT WORK IN VERSION 11.1.1.1.0

Hi all,
I'm facing serious problems after the migration from jdev 11.1.1.0 version to new release 11.1.1.1.0, as i published with a sample at
Problems with create new record o in JDev 11 R1
is this a big bug in the ide? Should i return to previous version?
Thanks in advance
Enrique

Hi,
my best recommendation is to work with customer supports in this testcase.
Frank

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

Similar Messages

Maybe you are looking for