Encoding with weblogic.jar or wlclient.jar

I am using weblogic 9.0 on jrockit 1.5.0_03 I have an application deployed using stateless session EJB’s.
I have a webstart client that runs on jdk1.5.0_03. When using weblogic.jar on the client side, everything runs fine.
When using wlclient.jar on the client side, I don’t get data from the server which contains umlauts. The data are lost on the client side.
In the direction to the server I have no problems, I can store data with umlaut. I tried already setting the default encoding on server (-Dweblogic.webservice.i18n.charset=utf-16) and client (-Dfile.encoding=utf-16), with no success.
Any help will be appreciated.
Thanks in advance!

Hello Sir
Did u solve the problem
i am also getting the same problem
please help me if u found the solution

Similar Messages

  • RMI problem with weblogic.jar

    We have a pure Java client that connects to the Weblogic server.
    While trying to connect we receive the error message below.
    I have unjarred the weblogic.jar file and discovered that the
    Stub.class is actually in weblogic/rmi/extensions/server/
    while it expects it to be in weblogic/rmi/extensions .
    Is there a fix for this as we are trying to upgrade from a previous version of weblogic and go live in Jan.
    Thanks
    Dave F
    java.lang.NoClassDefFoundError: weblogic/rmi/extensions/Stub(

    I'd suggest that you run the vm with the debug flag (-verbose) and see where the classes are being loaded; and examine the classpath to determine where the old jar or classes are occurring.
    Rita wrote:
    We have re-jarred the Stub.class and put it under weblogic/rmi/extensions, but when the java app runs, it still tries to look in weblogic/rmi/extensions/server. So, I think somewhere in the weblogic.jar, the path specified is still weblogic/rmi/extensions. Do you know what need to be done?
    Thanks,
    Rita
    Eduardo Ceballos <[email protected]> wrote:
    Yes, please regenerate your stub classes. That is, re-run rmic or ejbc.
    David Furlong wrote:
    We have a pure Java client that connects to the Weblogic server.
    While trying to connect we receive the error message below.
    I have unjarred the weblogic.jar file and discovered that the
    Stub.class is actually in weblogic/rmi/extensions/server/
    while it expects it to be in weblogic/rmi/extensions .
    Is there a fix for this as we are trying to upgrade from a previous version of weblogic and go live in Jan.
    Thanks
    Dave F
    java.lang.NoClassDefFoundError: weblogic/rmi/extensions/Stub(

  • Issue with weblogic.jar parsing the wsdl

    Hi,
    Here is a very small program, for which i am facing the problem of getting the
    types from the wsdl. It works fine, as standalone....You do not have to deploy
    the code any where..just have weblogic.jar in the classpath. It does not work.
    It works when weblogic.jar is not in the classpath..any help is GREATLY APPRECIATED...
    java.wsdl.Types from the java.wsdl.Definition object and the schema in the types
    is null ( when weblogic.jar is present in the
    I am always getting null in the schema (
    import javax.wsdl.Definition;
    //import weblogic.soap.wsdl.binding.Definition;
    import javax.wsdl.xml.WSDLReader;
    import javax.wsdl.factory.WSDLFactory;
    public class Test {
    Definition definition = null;
    public static void main(String args[] ) {
    Test test = new Test();
    test.parseWSDL(args[0]);
    public void parseWSDL(String WSDLName)
    try
    WSDLFactory wsdlFactory = WSDLFactory.newInstance();
    WSDLReader wsdlReader = wsdlFactory.newWSDLReader();
    wsdlReader.setFeature("javax.wsdl.verbose",false);
    wsdlReader.setFeature("javax.wsdl.importDocuments",true);
    definition = wsdlReader.readWSDL(WSDLName);
    System.out.println("-----------" + definition.getTypes() );
    catch( Exception e ) {
    System.out.println("Exception" + e ); }
    Thank for your help.
    Nag

    Hi Nag,
    With little reference to Sir Walter Scott, it would be a very tangled
    web we weave in an attempt to factor out the inter-relationships of
    javax interfaces that are hindering your effort. All to say, we don't
    currently support JSR 110 (javax.wsdl.*) and it is not on the near term
    horizon.
    Have you considered using autotype [1]?
    Regards,
    Bruce
    [1]
    http://edocs.bea.com/wls/docs81/webserv/anttasks.html#1080062
    Nag wrote:
    >
    Hi,
    Here is a very small program, for which i am facing the problem of getting the
    types from the wsdl. It works fine, as standalone....You do not have to deploy
    the code any where..just have weblogic.jar in the classpath. It does not work.
    It works when weblogic.jar is not in the classpath..any help is GREATLY APPRECIATED...
    java.wsdl.Types from the java.wsdl.Definition object and the schema in the types
    is null ( when weblogic.jar is present in the
    I am always getting null in the schema (
    import javax.wsdl.Definition;
    //import weblogic.soap.wsdl.binding.Definition;
    import javax.wsdl.xml.WSDLReader;
    import javax.wsdl.factory.WSDLFactory;
    public class Test {
    Definition definition = null;
    public static void main(String args[] ) {
    Test test = new Test();
    test.parseWSDL(args[0]);
    public void parseWSDL(String WSDLName)
    try
    WSDLFactory wsdlFactory = WSDLFactory.newInstance();
    WSDLReader wsdlReader = wsdlFactory.newWSDLReader();
    wsdlReader.setFeature("javax.wsdl.verbose",false);
    wsdlReader.setFeature("javax.wsdl.importDocuments",true);
    definition = wsdlReader.readWSDL(WSDLName);
    System.out.println("-----------" + definition.getTypes() );
    catch( Exception e ) {
    System.out.println("Exception" + e ); }
    Thank for your help.
    Nag

  • Problem building application with weblogic.jar placed out of bea install.

    Weblogic version: 10.3
    EJB Version: 2.x
    Method for generating webservices fomr EJBs: servicegen task.
    Application Build steps:
    Step1) Maven to build the complete application and generate ejb-jar.jar and other projects jars and wars.
    Step2) Post maven build success there is an ant script used to generate webservices using ejb’s in the project using servicegen task. Attached is build.xml for ant.
    Following is the class path :
    .;C:\PROGRA~1\IBM\SQLLIB\java\db2java.zip;C:\PROGRA~1\IBM\SQLLIB\java\db2jcc.jar;C:\PROGRA~1\IBM\SQLLIB\java\sqlj.zip;C:\PROGRA~1\IBM\SQLLIB\java\db2jcc_license_cu.jar;C:\PROGRA~1\IBM\SQLLIB\bin;C:\PROGRA~1\IBM\SQLLIB\java\common.jar;C:\Program Files\IBM\RationalSDLC\ClearQuest\cqjni.jar;C:\bea10.3\wlserver_10.3\server\lib\weblogic.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\webservices.jar;%JAVA_HOME%\lib\tools.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\libslf4j-log4j12-1.5.2.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\struts.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\bootstrap.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\db2jcc.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\db2jcc_license_cu.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\ehcache-core-2.0.0.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\j2ee.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\jdom.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\log4j-1.2.9.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\slf4j-api-1.5.8.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\ulc-dto.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\ulc-jar.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\scheduler-ejb.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\com.bea.core.xml.beaxmlbeans_2.0.0.0_2-5-1.jar;
    Problem Area:
    As you could notice in the yellow highlighted one that am referring to weblogic.jar from bea installation folder. Now if I use the weblogic.jar from the installation folder then build happens successfully.
    However if I copy weblogic.jar to some other location say : C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\weblogic.jar
    And include this path in the class path in place of weblogic.jar from the installation path, then I get the following errors: Please refer red highlighted part below…
    C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\ulc-ear>ant
    Buildfile: build.xml
    ejbwebservice:
    [servicegen] weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed D
    OCTYPE header
    [servicegen] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:301)
    [servicegen] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:241)
    [servicegen] at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:320)
    [servicegen] at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:295)
    [servicegen] at weblogic.ejb20.dd.xml.DDUtils.processEjbJarXML(DDUtils.java:265)
    [servicegen] at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:118)
    [servicegen] at weblogic.webservice.dd.EJBJarIntrospector.<init>(EJBJarIntrospector.java:47)
    [servicegen] at weblogic.webservice.util.WebServiceEarFile.init(WebServiceEarFile.java:177)
    [servicegen] at weblogic.webservice.util.WebServiceEarFile.readDD(WebServiceEarFile.java:235)
    [servicegen] at weblogic.webservice.util.WebServiceEarFile.<init>(WebServiceEarFile.java:74)
    [servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:177)
    [servicegen] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    [servicegen] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [servicegen] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [servicegen] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [servicegen] at java.lang.reflect.Method.invoke(Method.java:597)
    [servicegen] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    [servicegen] at org.apache.tools.ant.Task.perform(Task.java:348)
    [servicegen] at org.apache.tools.ant.Target.execute(Target.java:357)
    [servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:385)
    [servicegen] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
    [servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [servicegen] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    [servicegen] at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
    [servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:758)
    [servicegen] at org.apache.tools.ant.Main.startAnt(Main.java:217)
    [servicegen] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
    [servicegen] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    [servicegen] --------------- nested within: ------------------
    [servicegen] Error processing file 'META-INF/ejb-jar.xml'. weblogic.xml.process.XMLProcessingException: XML document doe
    s not appear to contain a properly formed DOCTYPE header - with nested exception:
    [servicegen] [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed
    DOCTYPE header]
    --------------- nested within: ------------------
    weblogic.webservice.util.WebServiceJarException: Could not process ejb-jar C:\DOCUME~1\ac30416\LOCALS~1\Temp\ulc-ear.ear
    -86826932\ejb.jar - with nested exception:
    [weblogic.webservice.dd.EJBProcessingException: Can read in ejb DD files. - with nested exception:
    [Error processing file 'META-INF/ejb-jar.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear
    to contain a properly formed DOCTYPE header - with nested exception:
    [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE heade
    r]]]
    at weblogic.webservice.util.WebServiceEarFile.init(WebServiceEarFile.java:183)
    at weblogic.webservice.util.WebServiceEarFile.readDD(WebServiceEarFile.java:235)
    at weblogic.webservice.util.WebServiceEarFile.<init>(WebServiceEarFile.java:74)
    at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:177)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
    at org.apache.tools.ant.Main.runBuild(Main.java:758)
    at org.apache.tools.ant.Main.startAnt(Main.java:217)
    at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
    at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    Please help as its urgent for me as we cannot have local installation of weblogic. We may just use the required jars.

    Weblogic version: 10.3
    EJB Version: 2.x
    Method for generating webservices fomr EJBs: servicegen task.
    Application Build steps:
    Step1) Maven to build the complete application and generate ejb-jar.jar and other projects jars and wars.
    Step2) Post maven build success there is an ant script used to generate webservices using ejb’s in the project using servicegen task. Attached is build.xml for ant.
    Following is the class path :
    .;C:\PROGRA~1\IBM\SQLLIB\java\db2java.zip;C:\PROGRA~1\IBM\SQLLIB\java\db2jcc.jar;C:\PROGRA~1\IBM\SQLLIB\java\sqlj.zip;C:\PROGRA~1\IBM\SQLLIB\java\db2jcc_license_cu.jar;C:\PROGRA~1\IBM\SQLLIB\bin;C:\PROGRA~1\IBM\SQLLIB\java\common.jar;C:\Program Files\IBM\RationalSDLC\ClearQuest\cqjni.jar;C:\bea10.3\wlserver_10.3\server\lib\weblogic.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\webservices.jar;%JAVA_HOME%\lib\tools.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\libslf4j-log4j12-1.5.2.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\struts.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\bootstrap.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\db2jcc.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\db2jcc_license_cu.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\ehcache-core-2.0.0.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\j2ee.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\jdom.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\log4j-1.2.9.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\slf4j-api-1.5.8.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\ulc-dto.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\ulc-jar.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\Deployment\scheduler-ejb.jar;C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\com.bea.core.xml.beaxmlbeans_2.0.0.0_2-5-1.jar;
    Problem Area:
    As you could notice in the yellow highlighted one that am referring to weblogic.jar from bea installation folder. Now if I use the weblogic.jar from the installation folder then build happens successfully.
    However if I copy weblogic.jar to some other location say : C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\nordea-ulc\lib\weblogic.jar
    And include this path in the class path in place of weblogic.jar from the installation path, then I get the following errors: Please refer red highlighted part below…
    C:\Jeevesh DEV\ULM Core\UnitLinkCore\UnitLink\ulc-ear>ant
    Buildfile: build.xml
    ejbwebservice:
    [servicegen] weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed D
    OCTYPE header
    [servicegen] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:301)
    [servicegen] at weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.java:241)
    [servicegen] at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:320)
    [servicegen] at weblogic.ejb20.dd.xml.DDUtils.processXML(DDUtils.java:295)
    [servicegen] at weblogic.ejb20.dd.xml.DDUtils.processEjbJarXML(DDUtils.java:265)
    [servicegen] at weblogic.ejb20.dd.xml.DDUtils.createDescriptorFromJarFile(DDUtils.java:118)
    [servicegen] at weblogic.webservice.dd.EJBJarIntrospector.<init>(EJBJarIntrospector.java:47)
    [servicegen] at weblogic.webservice.util.WebServiceEarFile.init(WebServiceEarFile.java:177)
    [servicegen] at weblogic.webservice.util.WebServiceEarFile.readDD(WebServiceEarFile.java:235)
    [servicegen] at weblogic.webservice.util.WebServiceEarFile.<init>(WebServiceEarFile.java:74)
    [servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:177)
    [servicegen] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    [servicegen] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [servicegen] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [servicegen] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [servicegen] at java.lang.reflect.Method.invoke(Method.java:597)
    [servicegen] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    [servicegen] at org.apache.tools.ant.Task.perform(Task.java:348)
    [servicegen] at org.apache.tools.ant.Target.execute(Target.java:357)
    [servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:385)
    [servicegen] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
    [servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [servicegen] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    [servicegen] at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
    [servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:758)
    [servicegen] at org.apache.tools.ant.Main.startAnt(Main.java:217)
    [servicegen] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
    [servicegen] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    [servicegen] --------------- nested within: ------------------
    [servicegen] Error processing file 'META-INF/ejb-jar.xml'. weblogic.xml.process.XMLProcessingException: XML document doe
    s not appear to contain a properly formed DOCTYPE header - with nested exception:
    [servicegen] [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed
    DOCTYPE header]
    --------------- nested within: ------------------
    weblogic.webservice.util.WebServiceJarException: Could not process ejb-jar C:\DOCUME~1\ac30416\LOCALS~1\Temp\ulc-ear.ear
    -86826932\ejb.jar - with nested exception:
    [weblogic.webservice.dd.EJBProcessingException: Can read in ejb DD files. - with nested exception:
    [Error processing file 'META-INF/ejb-jar.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear
    to contain a properly formed DOCTYPE header - with nested exception:
    [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE heade
    r]]]
    at weblogic.webservice.util.WebServiceEarFile.init(WebServiceEarFile.java:183)
    at weblogic.webservice.util.WebServiceEarFile.readDD(WebServiceEarFile.java:235)
    at weblogic.webservice.util.WebServiceEarFile.<init>(WebServiceEarFile.java:74)
    at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.execute(ServiceGenTask.java:177)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
    at org.apache.tools.ant.Main.runBuild(Main.java:758)
    at org.apache.tools.ant.Main.startAnt(Main.java:217)
    at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
    at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    Please help as its urgent for me as we cannot have local installation of weblogic. We may just use the required jars.

  • Weblogic.jar vs wlclient.jar problems

    Hi,
    I have a swing client and am trying to get authentication working correctly.
    A problem i am running across occurs when i try to login using empty strings.
    new LoginContext("Sample", new SampleCallbackHandler("", "", server));
    With weblogic.jar, no exceptions are thrown.
    With wlclient.jar, this is thrown: "UsernamePasswordLoginModule Error: NamingException on authenticate, Unhandled exception in lookup"
    Is this a bug, or am i doing something wrong? Thanks in advance.
    Chetan

    Hello Sir
    Did u solve the problem
    i am also getting the same problem
    please help me if u found the solution

  • How to resolve setPrefix() in SOAP(saaj API) with weblogic/webservices jar?

    Hi,
    I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
    My environment is as below:
    1) Weblogic 8.1 SP2 server
    2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
    3) A method is exposed as web-service
    4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
         MessageFactory mf = MessageFactory.newInstance();
         SOAPMessage sm = mf.createMessage();
         SOAPPart sp = sm.getSOAPPart();
         sp.setPrefix("soapenv");
         SOAPEnvelope se = sp.getEnvelope();
         se.addNamespaceDeclaration("soapenv","http://orion:7001");
    giving the following error at runtime:
    Exception in thread "main" java.lang.AbstractMethodError:
    weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
    at Client.main(Client.java:39)
    I am able to compile without any error/warning all the time.
    This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
    I am able to run the same application(outside Web-application as a stand-alone java program) without
    any error while not using weblogic/webservices jar in the classpath.
    The saaj jars needed to run without any error are:
    saaj-api.jar
    saaj-impl.jar
    mailapi.jar
    activation.jar
    xercesImpl.jar
    xalan.jar
    dom.jar
    jdom.jar
    I thinks this is a compatibility issue. Please suggest to resolve it.
    Thanks in advance,
    pal_sk

    Hi,
    I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
    My environment is as below:
    1) Weblogic 8.1 SP2 server
    2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
    3) A method is exposed as web-service
    4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
         MessageFactory mf = MessageFactory.newInstance();
         SOAPMessage sm = mf.createMessage();
         SOAPPart sp = sm.getSOAPPart();
         sp.setPrefix("soapenv");
         SOAPEnvelope se = sp.getEnvelope();
         se.addNamespaceDeclaration("soapenv","http://orion:7001");
    giving the following error at runtime:
    Exception in thread "main" java.lang.AbstractMethodError:
    weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
    at Client.main(Client.java:39)
    I am able to compile without any error/warning all the time.
    This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
    I am able to run the same application(outside Web-application as a stand-alone java program) without
    any error while not using weblogic/webservices jar in the classpath.
    The saaj jars needed to run without any error are:
    saaj-api.jar
    saaj-impl.jar
    mailapi.jar
    activation.jar
    xercesImpl.jar
    xalan.jar
    dom.jar
    jdom.jar
    I thinks this is a compatibility issue. Please suggest to resolve it.
    Thanks in advance,
    pal_sk

  • Conflict of weblogic with jaas.jar

    Hi there,
    I am using weblogic6.0+sp1 for JAAS simple and SSL authentication. Sun's
    implementation class com.sun.security.auth.login.ConfigFile in jaas.jar
    is conflict with the Config class I implemented that extends
    Configuration to parse the login policy file and return the array of
    AppConfigurationEntry. If this jaas.jar gets picked up before
    weblogic.jar (For some jdk version, this jar is put under the jdk's
    lib/ext directory) the sun's implementation will be picked up instead of
    mine and this will results in failure. I am wandering if this is a bug
    or not?
    Thanks,
    Cathy

    This has nothing to do with the class name, since both my implementation and
    sun's are subclass of Configuration class. Runtime, it will pick up sun's if
    jaas.jar is put in front of weblogic.jar.
    Hellen Andersen wrote:
    An aside related question: isn't jaas.jar always installed in lib/ext?
    Otherwise, couldn't you rename your ConfigFile class so it doesn't match
    Sun's?
    "Cathy Wei" <[email protected]> wrote in message
    news:[email protected]..
    Hi there,
    I am using weblogic6.0+sp1 for JAAS simple and SSL authentication. Sun's
    implementation class com.sun.security.auth.login.ConfigFile in jaas.jar
    is conflict with the Config class I implemented that extends
    Configuration to parse the login policy file and return the array of
    AppConfigurationEntry. If this jaas.jar gets picked up before
    weblogic.jar (For some jdk version, this jar is put under the jdk's
    lib/ext directory) the sun's implementation will be picked up instead of
    mine and this will results in failure. I am wandering if this is a bug
    or not?
    Thanks,
    Cathy

  • Problem with protocol.jar with weblogic

    atg10.0.3 and weblogic 11g on 64bit linux.
    I've been plagued by this problem with ATG's protocol jar. While it loads the jar when starting up startWeblogic.sh it does not get loaded when starting a managed server thus i get the following errors:
    **** Error Fri Jun 15 15:56:43 MDT 2012 1339797403444 / Unable to start service "/atg/scenario/ScenarioManager": atg.nucleus.ServiceException: The configuration file XMLFile(/atg/scenario/scenarioManager.xml) could not be read: java.net.MalformedURLException: unknown protocol: dynamosystemresource
    **** Error Fri Jun 15 15:56:43 MDT 2012 1339797403544 /atg/scenario/ScenarioManager Unable to combine messaging information from the process manager component /atg/scenario/ScenarioManager. The process manager has not been classified yet so it cannot be determined if global messages should be listened for. This error indicates a problem with component startup order - the /atg/scenario/ScenarioManager component has been started before the /atg/dynamo/messaging/MessagingManager component
    **** Error Fri Jun 15 15:56:43 MDT 2012 1339797403583 /atg/dynamo/messaging/MessagingManager An exception occurred while trying to parse XML definition file "XMLFile(/atg/dynamo/messaging/dynamoMessagingSystem.xml)" java.net.MalformedURLException: unknown protocol: dynamosystemresource
    Following instructions has led me to place the protocol.jar from DAS/lib to the root of my domain directory and then apply the classpath entry in startWeblogic.sh script. protocol.jar shows up at the top of this scripts SDTOUT. But I cannot seem to get it included in the production.out logs when starting the managed server.
    Any ideas?
    Thanks!
    -Kip

    Yes I figured this out. The problem was the version of weblogic. I was using 1.3.6 when it should have been 1.3.5. After changing out the version, I no longer had problems with protocol.jar.
    Thanks!
    -Kip

  • The weblogic.jar has the javax.management.*, it is conflict with rt.jar's

    Hello guys:
    I want to use JMX 1.0 to communicate with weblogic 8.1. The client should be run in the Java 1.5
    It throw
    java.io.InvalidClassException: javax.management.ObjectName; local class incompatible:
    stream classdesc serialVersionUID = -5467795090068647408, local class serialVersionUID = 1081892073854801359
    java.io.InvalidClassException: javax.management.ObjectName; local class incompatible:
    stream classdesc serialVersionUID = -5467795090068647408, local class serialVersionUID = 1081892073854801359I know the reason is java 1.5 has JMX 1.2 in it.
    So how can I program a class loader to load the weblogic.jar classes in? I have tried a lot of code, but failed.
    Is there any sample here?
    I want to use the JMX 1.0 in weblogic.jar at jdk1.5 run time
    Thanks a lot,
    Qiang

    Thanks for your reply,
    But I have tried your sugestions.
    I use
    Thread.currentThread().setContextClassLoader(cl);I am not sure whether it is correct.
    import java.io.IOException;
    import java.net.URL;
    import java.net.URLClassLoader;
    import java.security.AllPermission;
    import java.security.CodeSource;
    import java.security.PermissionCollection;
    import java.security.Permissions;
    import com.sun.org.apache.bcel.internal.util.ClassPath;
    public class NonDelegatingClassLoader extends URLClassLoader {
         private final PermissionCollection permissions = new Permissions();
              permissions.add(new AllPermission());
         public NonDelegatingClassLoader(URL[] urls) {
              super(urls);
         @Override
         protected synchronized Class<?> loadClass(String name, boolean resolve)
                   throws ClassNotFoundException {
              // Bootstrap classes must be loaded by the bootstrap ClassLoader
              if (name.startsWith("javax.management")
                        || name.startsWith("com.sun.jmx")
                        || name.startsWith("com.sun.management")
                                                                    || name.startsWith("weblogic.")
                   Class c = findLoadedClass(name);
                   if (c == null) {
                        try {
                             c = findClass(name);
                        } catch (ClassNotFoundException e) {
                             byte[] classBytes;
                             try {
                                  ClassPath cp = new ClassPath();
                                  classBytes = cp.getBytes(name);
                             } catch (IOException e1) {
                                  throw new ClassNotFoundException(name);
                             c = defineClass(name, classBytes, 0, classBytes.length);
                   if (resolve) {
                        resolveClass(c);
                   return c;
              } else {
                   return getClass().getClassLoader().loadClass(name);
         protected PermissionCollection getPermissions(CodeSource codesource) {
              return permissions;
    import java.net.MalformedURLException;
    import java.net.URL;
    import java.util.Iterator;
    import java.util.Set;
    import javax.naming.Context;
    import org.omg.CORBA.TIMEOUT;
    import weblogic.jndi.Environment;
    import weblogic.management.MBeanHome;
    import weblogic.management.runtime.JVMRuntimeMBean;
    public class QueryWLSThread extends Thread {
         private String m_url = "";
         private String m_username = "weblogic";
         private String m_password = "weblogic";
         private int m_heapUT = -1;
         private Timer m_timer = null;
         public QueryWLSThread(String url, String username, String password,
                   int timeOut) {
              //System.setProperty("jmx.serial.form", "1.0");
              m_url = url;
              m_username = username;
              m_password = password;
              m_timer = new Timer(timeOut, this);
              try {
                   URL[] urls = { new URL("file:/f:/Downloads/weblogic.jar") };
                   ClassLoader cl = new NonDelegatingClassLoader(urls);
                   Thread.currentThread().setContextClassLoader(cl);
              } catch (MalformedURLException e) {
                   // TODO // block
                   e.printStackTrace();
         }It throw out
    java.lang.NoSuchMethodException: weblogic.jndi.internal.ServerNamingNode_811_WLStub.<init>(weblogic.rmi.internal.StubInfo)
         at java.lang.Class.getConstructor0(Unknown Source)
         at java.lang.Class.getConstructor(Unknown Source)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:804)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:790)
         at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)If I do not check the name with "weblogic."
    it will throw out method not found.
    If I do not set the system env, it is the same I still use the jdk 1.5 classes.
    I am not sure how to load my class without loading the jdk1.5's
    I also use the java -xbootpath/a:
    Cannot fix this currently.

  • Weblogic.jar conflict with my js-1.0.jar(org.mozilla.javascript )

    I am using js-1.0.jar in my application. It gets conflict with package inside the weblogic.jar. For this issue i set the js-1.0.jar in server start-up and it works. But is there any way to resolve the (js-1.0.jar) package conflict without setting it in the classpath.

    I am using js-1.0.jar in my application. It gets conflict with package inside the weblogic.jar. For this issue i set the js-1.0.jar in server start-up and it works. But is there any way to resolve the (js-1.0.jar) package conflict without setting it in the classpath.

  • Wlthint3client.jar with WebLogic 10.0

    Can I use wlthint3client.jar instead of wlfullclient.jar with WebLogic 10.0 (and Tomcat 6.0)?
    I tried to use it and it seems to work. However as far as I know wlthint3client.jar was released as a part of WebLogic 10.3,
    so I'd like to make sure that there's no side effects.
    The reason to give up wlfullclient.jar is its size (~ 60 MB).

    See here:
    http://download.oracle.com/docs/cd/E14571_01/web.1111/e13717/wlthint3client.htm#SACLT362
    and here:
    http://download.oracle.com/docs/cd/E14571_01/web.1111/e14529/compatibility.htm#INRMP118
    The key section:
    A WebLogic Server 10.3.3 client can invoke RMI-based applications hosted on a WebLogic Server 8.1, 9.x, 10.0, 10.3, 10.3.1 and 10.3.2 server using IIOP, T3, T3S, HTTP, and HTTPS. JMS applications can be invoked using T3, T3S, HTTP, and HTTPS.
    For Tomcat look here:
    http://download.oracle.com/docs/cd/E14571_01/web.1111/e13717/wlthint3client.htm#BABGDFEA
    Tomcat is not mentioned explicitly, so while not certified it may still work.

  • Principals set empty when wlclient.jar used instead of weblogic.jar

    Hi,
    I have a swing client that makes use of JAAS for security.
    When I use weblogic.jar in classpath the client works perfectly. But if I use wlclient.jar in classpath the LoginContext.login() is working fine, loginContext.getSubject() is working fine, but subject.getPrincipals() is returning a empty set. I will be using this principals to display different screens for different principals. Does any one what the solution is?
    Thanks in advance
    Danny

    With the thin client jars there is no current programmatic way that a client could ever retrieve the principals.
    Thin client uses IIOP internally and so this is currently not possible

  • Partial redeployment of a static jar file with weblogic.Deployer

    Hello,
    We are working on an application serving jar files to customers, via Java Web Start, hence that are considered from our point of view as static files, like our HTML and Javascript pages.
    Moreover, we have one jar that changes regularly, so every time it's loaded on the server we need to do a partial redeployment of this jar file, as documented here: http://docs.oracle.com/cd/E13222_01/wls/docs103/deployment/redeploy.html#wp1025739
    However, it does not work, as I believe WebLogic doesn't consider my jar file as a static file.
    C:\>java -cp weblogic.jar weblogic.Deployer -adminurl http://mymachine:7001 -user weblogic -password mystrongpassword -name myapp -redeploy launcher/downloadme.jar
    weblogic.Deployer invoked with options: -adminurl http://mymachine:7001 -user weblogic -name myapp -redeploy launcher/downloadme.jar
    <Mar 8, 2013 7:09:36 PM CET> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, myapp [archive: null], to configured targets.>
    Task 24 initiated: [Deployer:149026]redeploy application myapp [Version=7] on WebServer.
    Task 24 failed: [Deployer:149026]redeploy application myapp [Version=7] on WebServer.
    Target state: redeploy failed on Server WebServer
    weblogic.management.DeploymentException:
    The application myapp#7 cannot have the resource launcher/downloadme.jar updated dynamically. Either:
    1.) The resource does not exist.
    or
    2) The resource cannot be changed dynamically.
    Please ensure the resource uri is correct, and redeploy the entire application for this change to take effect.
    As a side note, if I rename downloadme.jar to downloadme.jar.*html*, then WebLogic agrees to redeploy it!
    Is there any way to force the static redeployment of my jar file?
    Thanks and regards,
    Julien

    Hi,
    The feature you are trying to use works only when web application is deployed in exploded format. Is your app deployed in exploded format?
    Also jars are never considered static, so I doubt this will work here.
    As an alternative you can go for Oracle Weblogic Production redployment feature. Refer to - http://middlewaresupport.wordpress.com/2013/03/21/production-redeployment-feature-in-weblogic/
    Thanks,
    Ranjan
    Edited by: Ranjan K on Apr 12, 2013 5:45 AM

  • Problem with weblogic-ejb-jar.xml

    while trying to deploy a session bean to Weblogic Server 6.1 it gives a message "encoding not supported".The xml encoding set in weblogic-ejb-jar file by JDeveloper is "windows-1252" which is the cause for error...Can anybody help me on this...
    tia
    monmohan

    You need to use UTF-8 encoding for WebLogic.
    Check out the bea quickstart to learn how to change this.
    http://otn.oracle.com/products/jdev/htdocs/vcmigration/weblogic/content.html

  • Toplink-ejb-jar.xml config with weblogic-ejb-jar.xml

    Hello,
    To use toplink with EJB's deployed in Weblogic.
    I changed weblogic-ejb-jar.xml :
    (Because, it does not allow me to change <type-identifier> and <type-version> elements)
    <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
    <type-version>7.0</type-version>
    <type-storage>META-INF/toplink-ejb-jar.xml</type-storage>
    Here, is the toplink-ejb-jar.xml:
    (Because, I am asked to give PUBLIC value for Weblogic 8.1.0....)
    <!DOCTYPE toplink-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB RDBMS Persistence//EN" "file://D:/Toplink10g/toplink/config/dtds/toplink-wls-ejb-jar_10_0_3.dtd">
    <toplink-ejb-jar>
    <session>
    <name>myUniqueSession</name>
    <project-xml>META-INF/project.xml</project-xml>
    <login>
    <connection-pool>demoPool</connection-pool>
    </login>
    </session>
    </toplink-ejb-jar>
    1. I have also given full path to the "toplink-wls-ejb-jar_10_0_3.dtd", but I still get parsing error:
    "myBeans.jar": [EJB:011019]While reading META-INF/toplink-ejb-jar.xml, the persistence layer of the Entity EJB failed to deploy. The error was:
    "myBeans.jar": Error in descriptor line 5: Error parsing file at line: 5 column: 18. Element type "toplink-ejb-jar" must be declared..
    2. Also, How I can avoid the full path to the DTD???
    Thanks for your help in this regard!

    You are not properly configured to use TopLink with Weblogic. You need to place the TopLink_CMP_Descriptor.xml install file in your Weblogic lib/persistence directory. Add "TopLink_CMP_Descriptor.xml" to your persistence.install file and then update weblogic-ejb-jar.xml to reference the correct TopLink persistence type and versions, ie,
    <type-identifier>TopLink_CMP_2_0</type-identifier>
    <type-version>10</type-version>
    <type-storage>META-INF/toplink-ejb-jar.xml</type-storage>
    See the TopLink developer guide for more information and configuration details.
    http://download-east.oracle.com/docs/cd/B10464_05/web.904/b10313/pkg_depl.htm#1124524
    Cheers,
    Guy

Maybe you are looking for