Doubt about Web Service Client

Hi,
I'm triyng consuming a WSDL file. When I create a Web Service Client with the URL of the WSDL, the compilation shows this message:
init:
wscompile-init:
Created dir: C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\classes
Created dir: C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc
IISelector-client-wscompile:
Copying 1 file to C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\wsdl
advertencia: Procesando la operación "GeneraTurno" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "ActivaTurno" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "EliminaTurno" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "DevOcupacion" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "DevTurnosADesp" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "Helloword" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
advertencia: Procesando la operación "DevElementosDigiturno" que no se ajusta a WS-I con el estilo RPC y la codificación SOAP
BUILD SUCCESSFUL (total time: 3 seconds)
What does it mean?, and how can I solve it?
Thanks in advance.

When I build the project shows this warnings:
init:
deps-jar:
wscompile-init:
IISelector-client-wscompile:
web-service-client-generate:
Created dir: C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\empty
Compiling 63 source files to C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\classes
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_RequestStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_RequestStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_ResponseStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_ResponseStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_ActivaTurno_ResponseStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_RequestStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_ResponseStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_ResponseStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevElementosDigiturno_ResponseStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_RequestStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_ResponseStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_ResponseStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevOcupacion_ResponseStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_RequestStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_RequestStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_ResponseStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_ResponseStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_DevTurnosADesp_ResponseStruct_SOAPSerializer.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_EliminaTurno_RequestStruct.java:3: warning: unmappable character for encoding UTF-8
// JAX-RPC Standard Implementation (1.1.3, compilaci?n R1)
C:\Documents and Settings\ooliveros\Mis documentos\NetBeansProjects\Selector1\build\generated-sources\jax-rpc\selector1\IISelector_EliminaTurno_RequestStruct_SOAPBuilder.java:3: warning: unmappable character for encoding UTF-8
62 warnings

Similar Messages

Question about web service client

Hi,
I am creating the a client to call non wls web serveice.
First I need to create the client jar using clientgen. My question is when i create the client jar I need the wsdl file. where is the correct place to store the wsdl file? Also I have development and production wsdl file with the different service location. Do I have to store both of the wsdl files? It's a trouble to remember to build the different client jar for development and production (using different wsdl), is there anyway that I can build the client jar once and somehow dynamically configure to use different wsdl (ie service location) in different environment? Thanks

Hi Holy,
If you know the WSDL hasn't changed since you used it when running the clientgen Ant task, you can just use the one that is inside the JAR that clientgen produces. To do this, you just need to not specify an argument to the XXX_Impl constructor. For instance:
AttachmentPartsService_Impl service = new AttachmentPartsService_Impl();
This has some performance benefits, because it reduces the total number of network calls, the client-side Web Services stack makes. If you specify the URL for the WSDL to the constructor (as recommended by someone else here), the client-side Web Services stack will issue an HTTP GET to get it. Now if the WSDL that is returned uses types that are different than the ones the clientgen Ant task generated classes for (i.e. the ones in the JAR generated by the clientgen Ant task), you are in trouble because the client-side Web Services doesn't generate serialization/deserialization classes (i.e. the ones in the JAR generated by the clientgen Ant task) "on-the-fly".
The service endpoint for a Web Service call can (and should) be set programmatically, from a properties or configuration file. This will look something like this in the code:
import java.util.Properties;
import javax.xml.rpc.Stub;
private static Properties loadProperties(String fileName) throws IOException
if (fileName == null || fileName.length() == 0) return null;
Properties props = new Properties();
FileInputStream fis = null;
try
fis = new FileInputStream(fileName);
props.load(fis);
finally
if (fis != null) try { fis.close(); } catch (Exception ignore){}
return props;
public static void main() throws Exception
Properties props = loadProperties("MyProperties.properties");
Client client = new Client(props);
public Client(Properties properties)
AttachmentPartsService_Impl service = new AttachmentPartsService_Impl();
AttachmentPartsServiceSoap port = service.getAttachmentPartsServiceSoap();
if (schemeHostPort == null) schemeHostPort = "http://localhost:7001";
((AttachmentPartsServiceSoap_Stub)port)._setProperty(
Stub.ENDPOINT_ADDRESS_PROPERTY,
properties.getProperty("production.AttachmentPartsService.serviceEndpointURL"));
This way, you can have a different properties file for each environment you propagate the web service to, as opposed to saving copies of WSDL files just to have the "correct" service endpoint address. It also has the additional benefit of letting you store the service endpoint URLs for more than just one web service.
Regards,
Mike Wooten

Web service client timeout

Hi,
I'm trying to set a timeout on my web service client. But its not working. Your tutorials do not seem to address this.
I am using weblogic 10.3.2, with Java 1.6.
============
Properties propSys = System.getProperties();
propSys.put( "weblogic.webservice.UseWebLogicURLStreamHandler", "true" );
Stub stub = (Stub)portObject;
BindingInfo bindingInfo = (weblogic.webservice.binding.BindingInfo)stub._getProperty("weblogic.webservice.bindinginfo");
bindingInfo.setTimeout(1);
Iterator itr = stub._getPropertyNames();
while (itr.hasNext()){
Object element = itr.next();
log("\n properties that can be set: "+element);
stub._setProperty("weblogic.webservice.rpc.timeoutsecs","1");
===========
I've also tried setting the transaction-timeout and the remove-client-timeout in the weblogic-ear-jar.xml.
===========
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>ExternalEntryEJB</ejb-name>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>ExternalEntry</jndi-name>
<remote-client-timeout>1</remote-client-timeout>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>InternalEJB</ejb-name>
<local-jndi-name>Internal</local-jndi-name>
<enable-call-by-reference>True</enable-call-by-reference>
<remote-client-timeout>1</remote-client-timeout>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
===========
in case it matters, I am using weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask as the clientgen task in my build.xml
============
<clientgen autotype="False" ear="${dist}/${app.earname}" warName="${servlet.warname}" packageName="MyPackage.webservices.client"
keepgenerated="False" useServerTypes="True" clientJar="${dist}/MyAppClient.jar">
<classpath refid="build.classpath.builddir"/>
</clientgen>
============
I am testing by putting a Thread.sleep(75000) in the method which is called in the internal EJB. But the method runs to completion and returns the reply object after 90 seconds or so (it normally takes about 12 seconds), but does not timeout.
I've been told that because it is a web services client, the remote-client-timeout will be ineffective. I've also been told that because the EJBs run in the same JVM, the transaction-timeout will be ineffective. Is this so?
Thanks,
Walter

Can you change the clientgen task to weblogic.wsee.tools.anttasks.ClientGenTask this is for jax-rpc 1.1.
<taskdef name="clientgen"
classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
Hope that helps.

Web service Client developing!

Hi,
I've developed a web service client with JDeveloper 9i.
I did it using the WSDL file location and the stub/skeleton generator wizard.
Once made it, I wrote a client class with a method as follows:
// code beggining
public static Integer calculator (Integer a,Integer b) throws Exception {
Integer result= null;
if (a==null || b==null){
a= new Integer(0);
b= new Integer(0);
try {
CalculadoraWSStub calc= new CalculadoraWSStub();
result= calc.calculator(a,b);
catch (Exception ex)
throw new Exception ("\nMy Exception: " + ex.toString());
return result;
// code ending
Ok, now the main point of the problem.
If we execute this code under JDeveloper, everything goes well, BUT if we execute it as a function under Oracle database appears a Exception telling us something about a internal error because HttpClient/RetryModule constructor is private!
Can you help us?
-- we can't solve this problem because it only appears when we are trying to connect to a web service.
Thanks in advance, people!

Yes, this is correct. ANM 4.1 does not allow more that 5 logins per account and unfortunately this is not configurable. I suggest the you mention this to your local Cisco Account Team.

Web Service Client - SOAP/jms: Specific response queue (not default queue)?

Hi @ll
I try to define a specific jms response queue for a web service client that communicates SOAP/jms, running on a WLS 9.2. The web service itself runs also on a WLS 9.2 where also the request and response queues are located. By default the client receives the responses from a temporary response queue. Is there a way to define a specific response queue e.g. setting the JMSReplyTo property in the request on the client side?
/cheers&greetz
Dani

WLS do not have a light SOAP client with callbacks yet. It is
not a planed feature for 7.0, but we will considering this for
post 7.0.
regards,
-manoj
"markhu" <[email protected]> wrote in message
news:[email protected]..
Hi, guys:
I have a system : client written in Java/Swing, HTTPS authentication,
and then subscribes to a WLS 61. SP2 based JMS Topic and also has the
ability to send message to a Queue, since I can not bring down the size of
the client side WLS JMS dependency lib, I am thinking about using SOAP /
web service as the communication tier between my client and server, so the
question is: since the client need get the price updates in a real time
mode, I need build a server side based PUSH for all the new price updates
which come into the JMS Topic, and broadcast as SOAP messages to client,is
this mean that I have to build the Call - Back for the Java Swing Client,so
it can automatically get the new price updates as it's getting from JMS
Topic now ? Any Idea on how to build server side PUSH based SOAP message
center as web service ?? Thanks a lot.
regards,
mark
FYI:
I need the same PUSH service for my .NET based client as well.

Web service client ignores http proxy settings

I have a web service client using Weblogic's web service client library. I'm trying to instruct it to use a http proxy. I've set all the following system properties:
-Dhttp.proxyHost=127.0.0.1
-Dhttp.proxyPort=8080 -Dweblogic.webservice.transport.http.proxy.host=127.0.0.1 -Dweblogic.webservice.transport.http.proxy.port=8080
No traffic is passing through the proxy.
When the proxy is down, the application works fine too. I suspect that the proxy settings are completely ignored for some reason.
I'm using Weblogic 8.1 SP4 on a Windows XP box and JDK 1.4.2 (Sun's bundled JDK with Weblogic).

Sorry about the delay,
You just need to use the standard java http proxy properties, take a look at:
http://download-west.oracle.com/docs/cd/A97329_03/web.902/a95453/useservices.htm
Does this help?
Gerard

Pass Username token in Web Service Client

I am totally new to Java....I work primarily with .Net. I am trying to send a Username token to a web service. I looked at the examples...can't get them to run.
My question is, without using config files, can I specify username token in the class. You can do this in .Net.
I am working with .NetBeans IDE 5.0.

I looked at this example....didn't get to far because I couldn't setup the samples.
http://java.sun.com/webservices/docs/1.6/tutorial/doc/XWS-SecuritySamples5.html#wp569635
Here is the guide I followed to setup the samples.
http://java.sun.com/webservices/docs/1.6/tutorial/doc/XWS-SecuritySamples2.html
I didn't do the part about the keystore. I got stuck on the "Setting Build Properties", and I don't know how to run the samples.
Are you saying there is no way of creating a java application, creating the web service client with JWSDP 2.0 and then modifying either the generated code or my main.class to set the username and token properties?
Thanks, Mike L.

Setting connect timeout and read timeout on a Web service Client

How can I set timeout values for a SOAP Web service client?
I don't want to set timeout values for the complete JVM, but on a call-by-call basis. I was looking for something like:
SOAPConnection c = ....
c.setTimeout(...);Anyone?

Thanks again fsato4, but i still can not resolve my problem. I must use the java 1.2.2 and i think the package java.nio.charset is not supported. I have read documentation about the use of encodings but i can not understand clearly what is happening in my application. Let me explain what i am thinking and ask you some things.
I send a message from the client in VB using soap toolkit, obviously in UTF-8 format. When the message is received in my Java Web service, Do i need to do something in order to my Java string understands the message?.
What i am doing is to obtain the byte array with the following line:
byte[] utf8Bytes = strXmlFile.getBytes("UTF8");
And then i use the constructor of the string as follows:
String ostr = new String (utf8Bytes,"UTF8"); I think that in this point i have my string in a valid representation for my server (Sun solaris) Rigth?. And finally i use my new string to pass that value to my function which expects a java.lang.String, but the result is that all the special characters are replaced.
Just after of the new String line, i write my string to an Buffered Writer pointed to a FileOutputStream (just for Doublecheck) using the "ISO8859_1" encoding and for my surprise i can read very well that xml in my browser and the special characters are displayed in a correct way. Could you please explain me why?
Thanks for your help.

How to get info about web service caller inside Web Service

Hi..
I want to know that can we get info about Web Service Caller inside called web service..
Info Like IP Address, User Id, User Name
Regards,
Ajay Sharma

Hi,
I tested following code using JDevloper 11g
@Resource
    WebServiceContext wsc;
    @WebMethod
    public String webMethod() {
                MessageContext msgCtxt = wsCtxt.getMessageContext();
        HttpServletRequest req = (HttpServletRequest)msgCtxt.get(MessageContext.SERVLET_REQUEST);
        System.out.println("Client IP = " + req.getRemoteAddr());
        return req.getRemoteAddr();
    }It is giving me IP address but when i tested this web service from another computer there also it is giving my machine address instead of the machine IP from where the web service is called.
What is wrong in my code ?
Regards,
Ajay
Edited by: Ajay Sharma on Dec 31, 2012 1:06 PM

What is the steps to create the web service client

I'm quite new to web service and currently need to work on a web application that will call web service by passing the request data. Then will handle the response data. Following are questions that I would like to get your advice.
First, should I manually develop a schema? The request data will be passed as some element type (I thought a class should be generated and put in the class path), which will be some class with set/get(). Then I will use the schema to get a jar that contains the class file by using the xmlbean? Any example or suggestion on this?
Secondly, how does the java code in web application send/get the request/response data to/from the web service. Your example will greatly help.
I read article about WSDL and Schema and Soap. Get very confused on what really should be to follow step by step. Thanks in advance for your help!

I propose that you start with some introductory tutorials. At seekda you will find two tutorials for newbies:
1) [Finding and Testing Web Services|http://seekda.com/blog/write-your-first-web-services-client-%e2%80%93-part-1-finding-and-testing-services/]
2) [Using Web Services|http://seekda.com/blog/write-your-first-web-services-client-part-2-using-services/]
The second tutorial actually addresses most of your questions.
Greetings,
Michal

BigInteger in J2ME web service client

I have a problem about sending parameter of BigInteger in J2ME web service client.
To send a BigInteger as parameter web service, i change into array of byte then i change again into HexString.
After that, the String value send to web service.
The String value change into array of byte again then i build new object BigInteger.
I think the way i try is correct, but in J2ME as web service client the value of BigInteger that i send has change.
I tried in J2SE as web service client with the same way, then the value of BigInteger didn't changed.
Is it the class BigInteger in library lcrypto-j2me (BouncyCastle) cannot apply into BigInteger in java?
Or i've missing something???
Thanks a lot for the answer...
Best regards,
Meis

I have a problem about sending parameter of BigInteger in J2ME web service client.
To send a BigInteger as parameter web service, i change into array of byte then i change again into HexString.
After that, the String value send to web service.
The String value change into array of byte again then i build new object BigInteger.
I think the way i try is correct, but in J2ME as web service client the value of BigInteger that i send has change.
I tried in J2SE as web service client with the same way, then the value of BigInteger didn't changed.
Is it the class BigInteger in library lcrypto-j2me (BouncyCastle) cannot apply into BigInteger in java?
Or i've missing something???
Thanks a lot for the answer...
Best regards,
Meis

Create web service client for javafx project in netbeans 6.8

I here have a javafx project and need to create a web service client for it (in netbeans 6.8).
However when I right click this project -> new -> web service client -> input wsdl location\package -> finish, it seems that the client code is never generated. This is quite different from what happens when creating web service client for a java project.
Anyone knows how is this happening?

Thanks for your reply.
I did write my own ws client code but I need to create a web proxy based on an appointed wsdl path. That requires me to create a web service client from netbeans 6.8, like what I described in my first post. Unfortunately, it's not behaving like what I imagined it should do for a java project, even the javafx file itself doesn't have any error. The error occurs in package definition line.
package fx;For the definition above, it cannot access java.lang.builtins.
The question now is about the possibility to include javafx file in an non-javafx, say, java project. Any comments?
---Regards.

Change jsp's in web service client when creating a web service in WID

Hi, Actually , when we a web service, on websphere Integration Developer,JSP's get generated after creating the web service client.
Those JSP's are named as input.html, invoke.jsp etc, I need to change the jsp's for good look and feel,
But I am unalble to do that as there is no configuration information included in the jsps created by default, Please let me know, if any has come across this kind of situation and knows how to deal with.

Hi,
Not sure if you can get answer to WID specific questions on the Oracle-WebServices forum. Here, we are mainly talking about SOAP and WSDL, and mostly with the Oracle OC4J implementation.
When you generate a static proxy, you can set the endpoint URL dynamically using a helper method on the class generated by JDeveloper - look for setEndpoint()
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Stub;
    public void setEndpoint(String endpoint) {
        ((Stub) _port)._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, endpoint);
    }The generated code uses the JAX-RPC APIs under the cover, which may also apply to Websphere's internal implementation.
Hope it Helps,
-Eric

XML Parser Error while creating Web service Client using JAX RPC

hello evryone,
Im facing XML Parser Error while creating web service client using JAX RPC. Im using Net Beans IDE for development purpose. I have wrote configuration file for client. Now i want to create Client stub. However i dont know how to do this in Net Beans. So i tried to do it from Command promt using command :
wscompile -gen:client -d build -classpath build config-wsdl.xml
here im getting Error:
error parsing configuration file: XML parsing error: com.sun.xml.rpc.sp.ParseException:10: XML declaration may only begin entities
Please help me out.
Many thanks in advance,
Kacee

Can i use the client generated using jdeveloper 11g to import into the oracle forms 10g, i.e., form builder 10g. Currently this is the version we have in our office.

How to prevent downloading wsdl in weblogic web service client

Hi,
I get a problem regarding weblogic web service client. My working environment:
weblogic server 8.1
Windows XP SP2
JDK 1.4
I use the weblogic tool to generate the client jar file from the wsdl file.
     <target name="generate-client">
          <clientgen wsdl="ACCESS.wsdl"
               packageName="xxxxxx.client"
               clientJar="${client}/${AccessClient_jar_file}"
               keepGenerated="true"
               saveWSDL="true"
          />
          <javac srcdir="${source}"
          destdir="${client}"
          includes="**/AccessClient.java">
          <classpath>
          <pathelement path="${client}/${AccessClient_jar_file}"/>
          </classpath>
          </javac>
     </target>
After that, I create a client java file to invoke the service deploy in the server.
public static void main(String[] argv)
throws Exception
     int transactionId = 100;
     int id = 1000;
// Setup the global JAXM message factory
System.setProperty("javax.xml.soap.MessageFactory", "weblogic.webservice.core.soap.MessageFactoryImpl");
// Setup the global JAX-RPC service factory
System.setProperty( "javax.xml.rpc.ServiceFactory", "weblogic.webservice.core.rpc.ServiceFactoryImpl");
AccessServicePorts ws = new AccessServicePorts_Impl(argv[0]);
AccessService port = ws.getAccessService();
// Resource - create
Resource resource = new Resource();
resource.setRES_CD("Create ResCo");
resource.setCODE_CODE("code_cod");
resource.setRES_TYPE("Resource typ");
resource.setCOMMON_FIELD(common);
AccessDefaultResult resultItems = port.createResource(resource);
System.out.println("createResource : " + resultItems);
I find that this web service client always issue 2 http requests to invoke an web service method deployed in server.
1st http reqeust:
GET /AccessEpol/EpolServiceSoap?WSDL HTTP/1.1
User-Agent: Java/1.4.2_08
Host: 127.0.0.1:8001
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
the return result is the wsdl downloaded from the server.
2nd http request is the real web service request.
The question is how could I eliminate the 1st http request because it's really unnecessary. I use other web service client like Axis 1.x, Axis client never has the http request to download the wsdl from the server.
I read through weblogic web service document. It do mentions that put saveWSDL="true" in the clientgen ant task. the default value for saveWSDL is true already. I did try saveWSDL="false" also. None of them can eliminate the 1st http request.
appreciate for any answer my question?

Hi David,
thanks for the reply.
More or less I agree some points you mentioned above.
I did use Axis 1.x to test the inter-operability. The web service was developed in Weblogic 8.1 and is a part of an existing web application. It will be merged to existing application deployed in weblogic 8.1.
I also program the web service client to test the web service.
The implementation of the server and client will be handed over the project team and training for supporting or continuous development have to be conducted by me. So I don't like to use two types of technologies which will make thing complex.
I found this issue when I tried to protected the web service endpoint, eg http://localhost:7001/epol/service, using the web application Basic mechanism. The wsdl URL http://localhost:7001/epol/service?WSDL is also protected in this case. Unfortunately the username/password pair is not sent to the server when the weblogic client download the WSDL from the server. In this case, the client failed and throw exception.

Doubt about Web Service Client

Similar Messages

Maybe you are looking for