Custom serializer/deserializer in Weblogic 9 web service

We are able to select XML from the database which is properly formatted to the schema definition of the method return type. Therefore, the serialization/deserialization of XML to JAVA and then back to XML does not make sense.
Is there a way to use a custom serializer/deserializer in a Weblogic 9.1 web service like we could do in Weblogic 8.1? I have read where the 8.1 web services are still supported but we would like to migrate everything over now. In 8.1 the serializer/deserializer was defined in the deployment descriptor. However, I have seen nothing of this kind in Weblogic 9 documentation and all of those classes are now marked Deprecated.
Any help is greatly appreciated. Thanks!

Why dont you try removing the ejb-jar.xml and using annotations. You can use @JndiName and @FileGeneration annotations, this should work ...
-Jesus

Similar Messages

How to Serialize/Deserialize Beans with Web Services using DII client

Dear All;
I had developed a web serivce by Oracle JDeveloper [J2EE 1.4 (JAX-RPC)] and trying to invoke methods within through DII client using Apache Axis 1.
The Beans I am using are structured as follows:
public class InBean {
public InBean() {
private int x;
private float y;
public setters/getters for x
public setters/getters for y
public class OutBean {
public OutBean() {
private String inString;
private String outString;
public setters/getters for inString
public setters/getters for outString
The (InBean) is used as method input and the (OutBean) is used as method output.
The problems I am facing are as follows:
[1] How to serialize/desrialize the Beans as they are not registered with Apache Axis 1?
[2] How to invoke the Beans using Dynamic client DII and not classic proxy and Stubs?
[3] How to create the Beans using WSD2Java of the Apache Axis 1 ?
In case you have any helping URL's, Book names or sample code, please attach as they will be very helpful.
Thanks alot for the help.-----
Best Regards,
Ahmed M. Abbas

You will find some working code at :
http://ksoap.objectweb.org/software/downloads/index.html
It's code that use kSOAP and kXML implementations ....
If you will also find some useful information here :
http://developers.sun.com/techtopics/mobility/apis/articles/wsa/
http://www-106.ibm.com/developerworks/wireless/library/wi-jsr/
http://www-106.ibm.com/developerworks/wireless/library/wi-xmlparse/
Regards.

Sending WSSE security headers to non-weblogic web service

I have been trying to send wsse headers to a non-weblogic web service. I am looking for a way to do this using the control file I generated from the wsdl or the page flow where I implement the control, or the message handler file. I have username and password parameters but I cannot get this to function.
Here is the signature I need:
<?xml version="1.0" encoding="UTF-8" ?>
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <env:Header>
- <wsse:Security env:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
- <wsse:UsernameToken wsu:Id="Id-dFQDZm_34ewPYtaARIJ_4BfI" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>weblogic</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">weblogic</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</env:Header>
- <env:Body>
<n1:hello xmlns:n1="http://workshop.bea.com/WebServiceB" />
</env:Body>
</env:Envelope>
Of course the Body is different, but this is the security signature that I need to get into the header. After looking at all the examples, I only see the option of using a java proxy class to call the web service, which would be a little difficult to use as my whole page flow application so far is calling the web service from a generated control. There are also lots of coplex datatypes that are being sent to the web service so a jave proxy would be a little difficult. I have tried to take the code from the java proxy class example and put it in my handler class, but the handler seems to only use MessageContext, not WebServiceContext and will not let me add the username password tokens. When I have tried to case a WebServiceContext out of a MessageContext, it gives me a runtime error "Class Cast Exception" even though workshop lets me do it.
This is extremely urgent. Please help me! I am using the sample handler class called MessageHandler.java and the sample WSSE java proxy class called WebServiceBClient.java that generated the above signature.

More information:
Here is the first part of my Java Control where I am calling the web service and the message handler:
package controls;
* @jc:location http-url="http://localhost:7001/Checking.jws"
* @jc:wsdl file="#CheckingWsdl"
* @jc:handler callback="MessageHandler" operation="MessageHandler"
public interface CheckingService extends com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class CustomerInfo
implements java.io.Serializable
public java.lang.String FirstName;
public java.lang.String LastName;
public java.lang.String MiddleName;
public int SSN;
public int CustomerNumber;
public java.util.Calendar CreationDate;
public java.util.Calendar LastModifiedDate;
public static class FundingInfo
implements java.io.Serializable
public float Amount;
public java.util.Calendar CurrentDate;
public int AccountNumber;
public static class anyType
implements java.io.Serializable
public com.bea.xml.XmlObject[] t;
public static class AccountInfo
implements java.io.Serializable
public int AccountNumber;
public float Balance;
public int CustomerNumber;
public java.util.Calendar LastModifiedDate;
* @jc:protocol form-post="false" form-get="false"
public AccountInfo CreateAccountChecking (CustomerInfo CustomerInfo, FundingInfo FundingInfo, anyType CommonHeader);
static final long serialVersionUID = 1L;
Here is the section of the MessageHandler class where I am attempting to add security token to the header:
protected void addSecurityHeader (MessageContext mc)
* Registers a handler for the SOAP message traffic.
HandlerRegistry registry = mc.getHandlerRegistry();
List list = new ArrayList();
list.add(new HandlerInfo(WSSEClientHandler.class, null, null));
registry.setHandlerChain(new QName("hello"), list);
try
WebServiceContext context = (WebServiceContext)WebServiceContext.currentContext().getLastMessageContext();
//(WebServiceContext)mc;
WebServiceSession session = context.getSession();
* Set the username and password token for SOAP message sent from the client, through
* the proxy, to the web service.
UserInfo ui = new UserInfo("weblogic", "weblogic");
session.setAttribute(WSSEClientHandler.REQUEST_USERINFO, ui);
//mc.setProperty(WSSEClientHandler.REQUEST_USERINFO, ui);
* Adds the username / password token to the SOAP header.
SecurityElementFactory factory = SecurityElementFactory.getDefaultFactory();
Security security = factory.createSecurity(null);
security.addToken(ui);
session.setAttribute(WSSEClientHandler.REQUEST_SECURITY, security);
//mc.setProperty(WSSEClientHandler.REQUEST_SECURITY, security);
} catch (Exception ex) {System.out.println("EXCEPTION CAUGHT DOING SECURITY STUFF " + ex.getMessage());}
I tried to use the MessageContext to do this but it came out null. I tried to cast the MessageContext to WebServiceContext and it gave me a Class Cast Exception. I tried to add the HandlerRegistry section to this but of course the assignment mc.getHandlerRegistry is improper and is not compiling so don't let that confuse you.

Unable to pass xmlbeans object in weblogic web services using OEPE

Migrating Weblogic web services from Weblogic Workshop 10.3 to Oracle Enterprise for Eclipse...Passing xmlbean generated types in arguments of webservice call
How to work around the following errors? I do not have this error when in workshop 10.3 only in OEPE eclipse
"oracle.eclipse.tools.webservices.compiler.CompilationException: Errors: JAX-WS web services must not have xmlBean parameter or return type"
PLease note that I want DocType to be xmlbeans generated or inherited from org.apache.xmlbeans.XmlObject....
@WebMethod
     public void upload(String filename, DocType doc) {
Hi, I have legacy codes from Weblogic workshop 10.1 and 10.3.....
I am able to compile and run in Weblogic workshop 10.3 by passing the xmlbean generated DocType as arguments in the web services call.... but why am I not able to do this in Oracle Enterprise for Eclipse OEPE......
If I were to generate the web service from teh wsdl...it will generate it's own DocType.class in the jar files and not use the xmlbean generated class one....
How to get iOEPE to generate the classes in build\jws\ for
testWSService-annotation.xml
weblogic-webservices.xml etc like in workshop
How can I resolve this??? Am I stuck with Workshop on this?? How to work around??
Any help or clarifications would be much appreciated.
Inside testWS.java,
package ws;
import java.io.File;
import javax.jws.*;
import org.example.doc.DocType;
@WebService
public class testWS {
     @WebMethod
     public void upload(String filename, DocType doc) {
          try {
               doc.save(new File(filename));
          catch(Exception e) {
               System.out.println(e);
Inside xmlbeans generated DocType.java.....and DocTypeDocuments.java
* XML Type: DocType
* Namespace: http://www.example.org/doc
* Java type: org.example.doc.DocType
* Automatically generated - do not modify.
package org.example.doc;
* An XML DocType(@http://www.example.org/doc).
* This is a complex type.
public interface DocType extends org.apache.xmlbeans.XmlObject
public static final org.apache.xmlbeans.SchemaType type = (org.apache.xmlbeans.SchemaType)
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(DocType.class.getClassLoader(), "schemaorg_apache_xmlbeans.system.testWSTypeSystem").resolveHandle("doctypec217type");
* Gets the "element1" element
java.lang.String getElement1();
* Gets (as xml) the "element1" element
org.apache.xmlbeans.XmlString xgetElement1();
* Sets the "element1" element
void setElement1(java.lang.String element1);
* Sets (as xml) the "element1" element
void xsetElement1(org.apache.xmlbeans.XmlString element1);
* Gets the "element2" element
java.lang.String getElement2();
* Gets (as xml) the "element2" element
org.apache.xmlbeans.XmlString xgetElement2();
* Sets the "element2" element
void setElement2(java.lang.String element2);
* Sets (as xml) the "element2" element
void xsetElement2(org.apache.xmlbeans.XmlString element2);
* A factory class with static methods for creating instances
* of this type.
public static final class Factory
public static org.example.doc.DocType newInstance() {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance( type, null ); }
public static org.example.doc.DocType newInstance(org.apache.xmlbeans.XmlOptions options) {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newInstance( type, options ); }
/** @param xmlAsString the string value to parse */
public static org.example.doc.DocType parse(java.lang.String xmlAsString) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xmlAsString, type, null ); }
public static org.example.doc.DocType parse(java.lang.String xmlAsString, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xmlAsString, type, options ); }
/** @param file the file from which to load an xml document */
public static org.example.doc.DocType parse(java.io.File file) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( file, type, null ); }
public static org.example.doc.DocType parse(java.io.File file, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( file, type, options ); }
public static org.example.doc.DocType parse(java.net.URL u) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( u, type, null ); }
public static org.example.doc.DocType parse(java.net.URL u, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( u, type, options ); }
public static org.example.doc.DocType parse(java.io.InputStream is) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( is, type, null ); }
public static org.example.doc.DocType parse(java.io.InputStream is, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( is, type, options ); }
public static org.example.doc.DocType parse(java.io.Reader r) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( r, type, null ); }
public static org.example.doc.DocType parse(java.io.Reader r, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( r, type, options ); }
public static org.example.doc.DocType parse(javax.xml.stream.XMLStreamReader sr) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( sr, type, null ); }
public static org.example.doc.DocType parse(javax.xml.stream.XMLStreamReader sr, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( sr, type, options ); }
public static org.example.doc.DocType parse(org.w3c.dom.Node node) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( node, type, null ); }
public static org.example.doc.DocType parse(org.w3c.dom.Node node, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( node, type, options ); }
/** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
public static org.example.doc.DocType parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xis, type, null ); }
/** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
public static org.example.doc.DocType parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
return (org.example.doc.DocType) org.apache.xmlbeans.XmlBeans.getContextTypeLoader().parse( xis, type, options ); }
/** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
public static org.apache.xmlbeans.xml.stream.XMLInputStream newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream xis) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
return org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newValidatingXMLInputStream( xis, type, null ); }
/** @deprecated {@link org.apache.xmlbeans.xml.stream.XMLInputStream} */
public static org.apache.xmlbeans.xml.stream.XMLInputStream newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream xis, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
return org.apache.xmlbeans.XmlBeans.getContextTypeLoader().newValidatingXMLInputStream( xis, type, options ); }
private Factory() { } // No instance of this class allowed
Edited by: user11079482 on Jan 1, 2010 2:09 AM

Ok just as I expected. So I guess I am left with the following two options
1) either I switched to using JAXB in my apps instaed of xmlbeans....
2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
Programming Web Services for WebLogic Server (ant tasks)
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
Getting Started With WebLogic Web Services Using JAX-RPC
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

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.

Authenticating to weblogic web service using a client cert with webserver

I am trying to think of how to authenticate a client to a weblogic web service
using a client certificate. The wrinkle is that a Web Server (iis or whatever)
will be handling the ssl part and forwarding non-secure to weblogic. The cert
will still be accessable in the request using: HttpServletRequest req.getAttribute("javax.net.ssl.peer_certificates).
At this point it is not clear to me what I can do. When does CertAuthenticator
get called? Can I even use it? Will I have to write my own version of the weblogic.soap.server.servlet.StatelessBeanAdapter
class?
Any help will be appreciated, even explaining why it can't be done.
Thanks,
Scott

I am trying to think of how to authenticate a client to a weblogic web service
using a client certificate. The wrinkle is that a Web Server (iis or whatever)
will be handling the ssl part and forwarding non-secure to weblogic. The cert
will still be accessable in the request using: HttpServletRequest req.getAttribute("javax.net.ssl.peer_certificates).
At this point it is not clear to me what I can do. When does CertAuthenticator
get called? Can I even use it? Will I have to write my own version of the weblogic.soap.server.servlet.StatelessBeanAdapter
class?
Any help will be appreciated, even explaining why it can't be done.
Thanks,
Scott

Calling a WebLogic web service from a WebLogic web application

We would like to call a WebLogic web service from WebLogic web application. The current architecture looks like:
LoadBalancer--->iPlanet-1/iPlanet-2--->Firewall--->WebLogic-AppServer-1/WebLogic-AppServer-2
The web application and web service are in the same WebLogic cluster. We would prefer that the web services do not get published externally.
Does the WebLogic web application need to make a call back outside the firewall to the load balancer?
Is there a way the web services can be called locally with load balancing?
Can web service calls be made over the t3 protocol?
Thanks,
Mike

I think one solution is to use a Java proxy to call the Web services.
In the Java proxy you can have a method that accepts the user/pass and sets them correctly for the Web service.
Then you expose that Java proxy as a data control (right click, create data control) - and then create a page that invokes that method.
(For the basics of working with a POJO data control see: http://blogs.oracle.com/shay/2009/07/java_class_data_control_and_ad.html )

Stateful WebLogic Web Services using cookie

Hi all,
How do I configure WebLogic Web Services to return cookie in the HTTP header?
In my weblogic.xml I included the following attributes but no cookie is returned in the HTTP header.
<session-descriptor>
<cookie-http-only>false</cookie-http-only>
     <tracking-enabled>true</tracking-enabled>
     <cookies-enabled>true</cookies-enabled>
     <cookie-name>JSESSION_ID</cookie-name >
</session-descriptor>
Thanks
SMT

Ok just as I expected. So I guess I am left with the following two options
1) either I switched to using JAXB in my apps instaed of xmlbeans....
2) or if I still wanna use the old JAX-RPC web services to deploy on the Weblogic 10gR3 server i will have to create my own ant task jwsc directly......as shown below in your docs
Programming Web Services for WebLogic Server (ant tasks)
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/webserv/anttasks.html
Getting Started With WebLogic Web Services Using JAX-RPC
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_rpc/index.html
Will OEPE be supporting the old JAX-RPC anytime in the near future release? or have to create own build ant task to call jwsc ant task directly to compile JAX-RPC web services??

WebLogic Web Services Home Page and authentication

I've generated a set of web services using a session bean and have secured
my EJB methods. I'd like to enable testing of these methods via the WebLogic
Web Services Home Page service, but I can't figure out how to pass along the
authentication parameters. I've tried appending
'&username=myUser&password=myPassword' to the URL and this doesn't appear to
work (yeah, I know, but you can't blame me for trying).
Any ideas on how I might do this?
Thanks,
Rob

Looks like a bug. filed CR086448.
Contact support for patch.
regards,
-manoj
"Rob Moore" <[email protected]> wrote in message
news:[email protected]..
Hi, Manoj,
We're using WLS 7.0.0.1.
Thanks,
Rob
"manoj cheenath" <[email protected]> wrote in message
news:[email protected]..
The browser should pop up the user name/passwd dialog,
if the WS is secured. Which version of WLS are you using?
This could be a bug.
regards,
-manoj
"Rob Moore" <[email protected]> wrote in message
news:[email protected]..
I've generated a set of web services using a session bean and have
secured
my EJB methods. I'd like to enable testing of these methods via theWebLogic
Web Services Home Page service, but I can't figure out how to pass
along
the
authentication parameters. I've tried appending
'&username=myUser&password=myPassword' to the URL and this doesn't
appear
to
work (yeah, I know, but you can't blame me for trying).
Any ideas on how I might do this?
Thanks,
Rob

Simple question re invoking non-WebLogic web services

I have a very simple question that I haven't been able to resolve elsewhere.
I need to invoke 3rd-party SOAP interfaces from my WebLogic 6.1 client EJB. All
the Bea documentation I've found refers to invoking "WebLogic Web Services" and
speaks of downloading the client.jar -- however, in my case it's not a "WebLogic
Web Service" I'm invoking, it's a non-WebLogic web service.
Does WebLogic 6.1's WebServiceProxy (or other tool) allow this? Or must I use
some other SOAP tool such as Apache Axis in this case?
Thanks.
Cheers,
allan

Could this interopability problem have something to do with a problem
I'm experiencing on 61.sp3?
I have an EJB that accesses SOAP services on a Tomcat server. The SOAP
service sends back a SOAP exception which is correct in what I am asking
in to do. However, the weblogic app server is returning a SOAP
exception to my EJB rather than passing the SOAP exception to the API
that I am using to make my SOAP calls.
Has anyone seen something like this?
Sandy Mustard
john wrote:
>
The 'samples/examples/webservices/rpc/javaClient/XMethodClient'
is an example of how to invoke a non-WL webservice. You can
use that code within your EJB.
The javadocs for the WebServiceProxy class (from BEA's site)
will give you more methods that may be useful to you.
Note that your best bet, if possible, is to use the JAX-RPC
APIs within WebLogic 7. The SOAP support in WL6.1 has
interoperability issues.
-john
"Allan Halme" <[email protected]> wrote:
I have a very simple question that I haven't been able to resolve elsewhere.
I need to invoke 3rd-party SOAP interfaces from my WebLogic 6.1 client
EJB. All
the Bea documentation I've found refers to invoking "WebLogic Web Services"
and
speaks of downloading the client.jar -- however, in my case it's not
a "WebLogic
Web Service" I'm invoking, it's a non-WebLogic web service.
Does WebLogic 6.1's WebServiceProxy (or other tool) allow this? Or must
I use
some other SOAP tool such as Apache Axis in this case?
Thanks.
Cheers,
allan

Oracle web services or WebLogic web services ?

On " Oracle® Fusion Middleware Introducing Web Services" I read that on Oracle Fusion Middleware 11g platform there are 2 type of web services :
1) SOA, ADF, and WebCenter services
2) WebLogic Web services (Java EE Web services)
But what is the difference ? both web services aren't based on java specification ? why there is the distinction ?
Anyone can help me ?
Edited by: kronos72it on Nov 18, 2009 4:43 AM

It depends what you intend to do. The Oracle WebServices stack adds dynamics (needed for BPEL, etc.) and the OWSM security interceptors to the stack. Both have different security policy models and are not interoperable in this sense. I would go for the Oracle stack as the OWSM security is much easier to administer...
--olaf

Welcome to WebLogic Web Services forum!!

Hello WebLogic customers/developers,
This is a new forum dedicated to discussion on web service development on WebLogic server. You can continue to use the existing "web services" forum for questions on OC4J web services.
For a start, you can go to http://edocs.bea.com/wls/docs103/webservices.html for the latest product documentation, samples, and other relevant resources.
WebLogic web service dev/pm team will try to be respond to questions posted on this forum ASAP with crystal-clear information. Looking forward to hearing from you.
Regards,
Pyounguk

Hii,
I have deployed a web service on admin server.
I tested the web service by clicking on the test page link available.
Now i have enabled the administration port.
As the url changes automatically for the console to 9002 and protocol to https.
The url of the test page still shows the old url of the admin server and it doesnt change dynamically to 9002 .
I am able to test it only when i change the port manually as 9002 and protocol as https.
I just want some explanation regarding why it is behaving like this.

Generating Weblogic Web Services with OEPE

The OEPE plugin set allows you to generate JAX-WS Weblogic Web Services via a menu option by rick clicking a WSDL and choosing Weblogic Web Services -> Generate Web Service. The downside is this plugin overrides the existing service implementation file. There is a dialogue box that warns you and asks you if you want to replace it, but in order to generate the Java classes from the XML schema, it forces you to replace your implementation file. If you have version control you can get it back, but it can be annoying and dangerous if the file was not version controlled at that time.
Suggestion is to have a checkbox on the first menu screen to preserve the existing service implementation file.

This is a great suggestion, currently other than creating an alternate src folder, it forces you to overwrite. We really appreciate this feedback and knowing how the features are used.

Accessing config information in XML file in a Weblogic web service (JWS)

Problem:
I have implemented a web service for sending emails and pages via Java Mail and SNPP respectively using WebLogic Workshop on the BEA WebLogic 8.1 platform. In the service, I use certain pieces of information that are currently stored in an XML file on disk. Also, in its current state, the web service is implemented with public methods directly in the .jws Java file and not as a session bean. The file read from disk is performed every time the web service operation to send a message is invoked. As we all know, the I/O files access is very expensive and a performance bottleneck, especially when it is incurred on every invocation of the web service ‘sendMessage’ [operation.
Without radically re-writing the application, I am looking for a way to improve the performance of the web service and can only come up with the following 2 ways:
1) Move the code out of the sendMessage operation: Here, the main question I have is 'to where should I move it to'? I have seen in the WebLogic Workshop documentation that WebLogic Server maintains only a single instance of a Java class that implements a Web Service operation, and each invoke of the Web Service uses this same instance. In that case, I should be able to put the code in the constructor so that the files is read only at the time the class is instantiated, but a constructor in the .jws file that contains the web service operations itself does not seem to be invoked by the container (I tried to put a breakpoint in the constructor, but it seems that the constructor code never gets called)
2) Move the configuration variables into some type of standard configuration file of WebLogic, something like web.xml or wlw-config.xml or jws-config.properties files. But I found that these XML files have an associated schema to conform to and do not provide any custom elements or attributes that I could add for my application(is that true?). Also, if I can somehow put the configuration information into any of these standard files, how do I access it from within the application 'without' doing a file read from disk? Are these configuration file items available in memory for access and use by the web service and if they are, what API can I use to access and use them?
Any and all ideas are welcome!
Thanks!

I have been looking into a similar problem. Since web services are by design stateless, they aren't good for 'remembering' information between calls. Aside from a file read, the only other solution I have found is to use a database. You can make use of an entity bean or simply make some kind of JDBC call. I don't know if you need to stick with the config file, but if so maybe you could read the config data into a database once and then you might have faster access than reading from a file. I'm not sure about which would have better performace, but its all I have come up with so far. What parser are you using to read your XML file? Have you tried others to see if they have better performance?

Custom/Complex data types in web services

Hi,
I've read in several articles here on otn that JDev 9.0.3 would have better support for
creating web services with complex datatypes (like java.util.LinkedList), but still (in the 9.0.3 Preview)
theese methods are greyed out on the web service wizard. Am I missing something?
Until now I've worked with Custom Serializers, but they are time consuming and hard to work with.
/Mattias

Here are the two articles that will help:
JavaBeans as Web services parameter types:
http://otn.oracle.com/tech/webservices/htdocs/samples/customtype/content.html
Registering Web services custom serializers:
http://otn.oracle.com/tech/webservices/htdocs/samples/serialize/content.html
The new support in JDev 9.0.3 is that JavaBean parameters are now recognized by the JDev publishing wizards whereas in JDev 9.0.2 there was the workaround pointed to by the first article. In 9.0.2 the publishing support was only for primitive data types.
The upside of the custom serializers, is you can re-use your existing serializers if they happen to have been written to Apache SOAP.
Mike.

Custom serializer/deserializer in Weblogic 9 web service

Similar Messages

Maybe you are looking for