Weblogic 10.3 not supporting SAAJ1.1

Hi,
I am manipulating the SOAPHeader using SAAJ API in Weblogic 10.3 in the following way:-
MessageFactory factory = MessageFactory.newInstance();
     SOAPMessage message = factory.createMessage();     
     SOAPHeader header = message.getSOAPHeader();
     SOAPElement security =header.addChildElement("Security", "wsse", "http://schemas.xmlsoap.org/ws/2002/07/secext");
     SOAPElement usernameToken =security.addChildElement("UsernameToken", "wsse");
//usernameToken.addAttribute(new QName("xmlns:wsu"), "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd");
     SOAPElement username =usernameToken.addChildElement("Username", "wsse");
username.addTextNode("*******");
SOAPElement password =usernameToken.addChildElement("Password", "wsse");
password.setAttribute("Type", "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText");
     password.addTextNode("*******");
But getting the below exception:
java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1
     at weblogic.webservice.core.soap.SOAPMessageImpl.getSOAPHeader(SOAPMessageImpl.java:639)
Please suggest how we can resolve the above error?Do we require any patches or some configuration files need to be change?What all SAAJ versions are supported by Weblogic10.3?
Thanks..

try :
cd servers /AdminServer/data/ldap
rm -rf *
simply try to remove all the files present in the ldap dir and then try to start the Admin Server.
Always back up data before deleting.

Similar Messages

  • Weblogic 10.0 MP1: Client VM not supported

    Dear All,
    Installation of Weblogic serever completed successfully but, while starting the weblogic server I am getting the following error/message: Client VM not supported.
    Please provide suggestion or an idea on what to do. The details are provided below.
    Processor: Intel Quad core 64bit
    OS: windows server 2008 R2 64 bit
    Java: JDK 1.5 update 21 64 bit
    Weblogic: Server 10.0 MP1 64 bit for windows
    Regards,
    Edited by: user4198347 on Feb 5, 2011 11:49 PM

    Re: Installation error: Weblogic Server 10.0 MP2

  • Error -- ISO8859_1 Not Supported in Weblogic 6.1 SP2

    I've installed Weblogic 6.1 Service Pack 2 on Solaris 8, and when I go to install
    and deploy and applications (including the Petstore Demo) I get an error message
    which says 'ISO8859_1 is not supported'.
    If I stop and then restart the Weblogic Server, I get the following StackTrace
    included below.
    I've noticed there have been several posts on this topic, but no response. Thanks
    in advance to anyone who can help me out!
    Gary Smith
    [email protected]
    --Stack Trace of Error when Server Startup:
    weblogic.xml.process.XMLParsingException: The encoding "ISO8859_1" is not supported.
    - with nested exception:
    [org.xml.sax.SAXParseException: The encoding "ISO8859_1" is not supported.] Line:
    0 Column: 0
    at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:135)
    at weblogic.j2ee.dd.xml.J2EEDeploymentDescriptorLoader_J2EE12.process(J2EEDeploymentDescriptorLoader_J2EE12
    .java:137)
    at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:114)
    at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:85)
    at weblogic.management.mbeans.custom.Application.getDD(Application.java:670)
    at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:487)
    at weblogic.management.mbeans.custom.Application.load(Application.java:387)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy11.load(Unknown Source)
    at weblogic.management.mbeans.custom.ApplicationManager.loadApplications(ApplicationManager.java:556)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:367)
    at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy38.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_Cach
    ingStub.java:480)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
    at weblogic.management.Admin.finish(Admin.java:590)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)

    Gary:
    Please try using a valid XML (also called MIME or IANA) encoding name
    (ISO-8859-1) instead of the Java encoding name (ISO8859_1).
    The IANA character set registry can be found at:
    <http://www.iana.org/assignments/character-sets>
    Regards --
    Jim Brown
    Gary Smith wrote:
    >
    I've installed Weblogic 6.1 Service Pack 2 on Solaris 8, and when I go to install
    and deploy and applications (including the Petstore Demo) I get an error message
    which says 'ISO8859_1 is not supported'.
    If I stop and then restart the Weblogic Server, I get the following StackTrace
    included below.
    I've noticed there have been several posts on this topic, but no response. Thanks
    in advance to anyone who can help me out!
    Gary Smith
    [email protected]
    --Stack Trace of Error when Server Startup:
    weblogic.xml.process.XMLParsingException: The encoding "ISO8859_1" is not supported.
    - with nested exception:
    [org.xml.sax.SAXParseException: The encoding "ISO8859_1" is not supported.] Line:
    0 Column: 0
    at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:135)
    at weblogic.j2ee.dd.xml.J2EEDeploymentDescriptorLoader_J2EE12.process(J2EEDeploymentDescriptorLoader_J2EE12
    java:137)
    at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:114)
    at weblogic.j2ee.dd.xml.J2EEUtils.loadDeploymentDescriptor(J2EEUtils.java:85)
    at weblogic.management.mbeans.custom.Application.getDD(Application.java:670)
    at weblogic.management.mbeans.custom.Application.adminLoad(Application.java:487)
    at weblogic.management.mbeans.custom.Application.load(Application.java:387)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy11.load(Unknown Source)
    at weblogic.management.mbeans.custom.ApplicationManager.loadApplications(ApplicationManager.java:556)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:367)
    at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy38.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_Cach
    ingStub.java:480)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
    at weblogic.management.Admin.finish(Admin.java:590)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)--
    Jim Brown
    Developer Relations Engineer
    BEA Support

  • Weblogic 8.1 SP2 does not support 'Order by' clause in EJB-QL

    It seems that Weblogic 8.1 SP2 does not support 'Order by' clause in EJB-QL. EJB 2.1 spec supports 'Order by' clause in EJB-QL. Am I right when I say that it indicates : "Weblogic 8.1 SP2 does not support EJB 2.1" ? In that case, what can be the alternative since I am using Weblogic 8.1 and I require 'Order by' clause in Ejb-QL as well.

    In WL 8.1 SP4 I can use the ORDERBY just fine.
    Try ORDERBY instead of Order by

  • Native VM not supported error when start WebLogic Server on Solaris

    I created a weblogic domain and server using configuration wizard from workshop 8.1, the JVM is jdk142_05. When I start weblogic server, get follwing error: native VM not supported. The enviroment is
    Solaris.
    We used the same jdk started medrec example without problem. Any idea for the possible cause?
    Thank any one who can help.
    Zhong
    uberpeer% ./startWebLogic.sh
    JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=:/rg2/opt/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/rg2/opt/bea/weblogic81/common/lib/log4j.jar:/rg2/opt/bea/weblogic81/server/lib/debugging.jar:/rg2/opt/bea/weblogic81/server/lib/knex.jar:/rg2/opt/bea/weblogic81/javelin/lib/javelin.jar:/rg2/opt/bea/weblogic81/server/lib/wlw-lang.jar:/rg2/opt/bea/jdk142_05/lib/tools.jar:/rg2/opt/bea/weblogic81/server/lib/weblogic_sp.jar:/rg2/opt/bea/weblogic81/server/lib/weblogic.jar:/rg2/opt/bea/weblogic81/server/lib/ant/ant.jar:/rg2/opt/bea/jdk142_05/jre/lib/rt.jar:::/rg2/opt/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/rg2/opt/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/rg2/opt/bea/weblogic81/server/lib/webserviceclient.jar:/rg2/opt/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/rg2/opt/bea/weblogic81/server/lib/xbean.jar:/rg2/opt/bea/weblogic81/server/lib/wlxbean.jar:/rg2/opt/bea/weblogic81/server/lib/xqrl.jar:/rg2/opt/bea/weblogic81/server/lib/netui/netui-compiler.jar:/rg2/opt/bea/weblogic81/server/lib/wli.jar:/rg2/opt/bea/weblogic81/server/lib/fop.jar:/rg2/opt/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
    PATH=/rg2/opt/bea/weblogic81/server/bin:/rg2/opt/bea/jdk142_05/jre/bin:/rg2/opt/bea/jdk142_05/bin:/opt/bea/weblogic700/server/lib/solaris:/opt/bea/jdk131_03/jre/bin:/opt/bea/jdk131_03/bin:/rg1/users/zhongw/weblogic/PMDomain:/rg2/opt/bea/weblogic81/workshop:/rg1/users/zhongw/bin:/bin:/usr/bin:/usr/sbin:/usr/java/bin:/usr/openwin/bin:/opt/local/bin:/usr/ccs/bin:/usr/per15/bin:/usr/local/SUNWspro/bin:/usr/local/accurev/bin:/opt/jakarta-ant/bin:/usr/local/accurev/bin:/usr/ccs/bin:/usr/local/bin:/opt/enJin/2.3.1/bin:/usr/java/bin:/usr/openwin/bin:/usr/dt/bin:/rg1/users/zhongw/Borland/JBuilder2005/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.4.2_05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
    Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
    Starting WLS with line:
    /rg2/opt/bea/jdk142_05/bin/java -client -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -native -Xverify:none -da -Dplatform.home=/rg2/opt/bea/weblogic81 -Dwls.home=/rg2/opt/bea/weblogic81/server -Dwli.home=/rg2/opt/bea/weblogic81/integration -Dlog4j.configuration=file:/rg2/opt/bea/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=cgServer -Djava.security.policy=/rg2/opt/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
    Error: native VM not supported
    Stopping Pointbase server...
    Pointbase server stopped.

    I believe this is the error you get when you try to start up a JVM with the commandline option '-native'.
    Remove this flag from your startup script and retry.
    By the way, it may be that you have the environment variable 'JAVA_OPTIONS' set to '-native' in which case:
    (first confirm this is the case)
    $ echo $JAVA_OPTIONS
    -native
    (Then edit the startup script if you get the result above)
    add in a line:
    # To remove '-native' flag
    unset JAVA_OPTIONS
    and retry.
    I have to confess I don't know what the '-native' flag is actually supposed to do, but my JVM also reports back that this is unsupported.

  • Weblogic Server 10.0 MP1 while starting: Client VM not supported

    Dear All,
    Installation of Weblogic serever completed successfully but, while starting the weblogic server I am getting the following error/message: Client VM not supported.
    Please provide suggestion or an idea on what to do. The details are provided below.
    Processor: Intel Quad core 64bit
    OS: windows server 2008 R2 64 bit
    Java: JDK 1.5 update 21 64 bit
    Weblogic: Server 10.0 MP1 64 bit for windows
    Regards,
    Edited by: user4198347 on Feb 5, 2011 11:48 PM

    Re: Installation error: Weblogic Server 10.0 MP2

  • Crystal rpeort java(crj) not support weblogic 10.3.6 jdk1.6

    Hi,
    My system use weblogic 10.0 jdk1.5 with crystal report java (crjava-runtime_12.2.217) is work find, but we want to upgrade server to weblogic 10.3.6.
    In the crystal report java (crjava-runtime_12.2.217) document say weblogic 10.3.6 only support 1.5.0_04.
    I install jdk1.5 with weblogic 10.3.6 the server can't started success, it well say bad version for .class.
    I can't accept is any brand application server have support jdk1.6.
    Only Weblogic not support jdk1.6(Tomcat support 1.6 and is free).
    Someone can help me to finish server upgrade?
    Thank you very much.
    crystal report java (crjava-runtime_12.2.217) support document:
    Web Application Servers       
    JDK Support
    ===========================================================
    * JBoss 4.2
    1.5
    * JBoss 5
    1.5
    * JBoss 7.1
    1.6
    * Oracle Application Server 10g R3 (10.1.3)
    1.5.05
    * SAP Web Application Server 7.1
    1.5
    * SAP Web Application Server 7.31 SP4
    1.6
    * SAP Web Application Server 7.40
    1.6
    * Tomcat 5.5
    1.5.0_x
    * Tomcat 6.0
    1.5+/1.6
    * Tomcat 7.0.25
    1.6
    * WebLogic 9.2
    1.5.0_04
    * WebLogic 10.2
    1.5.0_04
    * WebLogic 10.3
    1.5.0_04
    * WebSphere 6.1
    1.
    * WebSphere 7.0
    1.5
    * WebSphere 8.5
    1.6

    Hi,
    The standalone weblogic 10.3.6 does support jdk 1.6 and not jdk1.5
    if crystal report works only with wls 10.3.6 with jdk 1.5, then you need to check if there is any other version of crystal report that can be used with wls 10.3.6 + jdk 1.6
    Thanks,
    Sharmela

  • URGENT: Is Weblogic 10.3.4 not supported for OIM 11g ?

    Hi Everyone,
    Is Weblogic 10.3.4 not supported for OIM 11g ?
    I installe & configured all IAM suite components (OAM,OIM,OAAM,SOA) on WLS 10.3.4. I am able to start all servers including OIM. However it is unable deploy "oim". After doing some research , I found below URL which tells WLS 10.3.4 is NOT SUPPORTED for OIM 11g.
    Not able start oim_server1, could not open oim url
    If that is true, Is there anyway to downgrade Weblogic to 10.3.3 ?
    Please provide your inputs and suggestions.
    Thanks
    GK

    No. 11G has been released with all type of supporting infrastructure components to be residing at the same level (i.e 11G only). So you would not be able to just downgrade weblogic to any lower versions.

  • Papi Client:: The WebLogic Server 9.x-style policy is not supported in JAX

    Ive generated a papi WS client using Ant <clientgen>. When I deploy and run it in weblogic 10.3.4 I get this error:
    Caused by: weblogic.wsee.ws.init.WsDeploymentException: The WebLogic Server 9.x-style policy is not supported in JAX-WS web services.
    at weblogic.wsee.security.wssp.deploy.WssDeploymentListener.process(WssDeploymentListener.java:55)
    at weblogic.wsee.jaxws.framework.jaxrpc.TubelineDeploymentListener.createClient(TubelineDeploymentListener.java:56)
    Im setting the username/password using a ClientUNTCredentialProvider:
              BindingProvider bindingProvider = (BindingProvider) port;
              Map<String, Object> requestContext = (Map<String, Object>) bindingProvider.getRequestContext();
              List<CredentialProvider> credentailProviders = new ArrayList<CredentialProvider>();
              credentailProviders.add(new ClientUNTCredentialProvider(credentials.getUserName().getBytes(), credentials
                        .getPassword().getBytes()));
              requestContext.put(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credentailProviders);
              requestContext.put(BindingProvider.USERNAME_PROPERTY, credentials.getUserName());
              requestContext.put(BindingProvider.PASSWORD_PROPERTY, credentials.getPassword());
    What else do I need to do?

    I have exactly the same problem.
    how you solved this issue?

  • It is true that Weblogic 10.3 does not support the 1.2.840.113549.1.1.11?

    It is true that Weblogic 10.3 does not support the 1.2.840.113549.1.1.11. - SHA1 with RSA signature encryption?

    Refer: Re: SSL not working with 10.3 and jdk 1.6.0_13
    -Akshay

  • IIS proxy 5.1 and Weblogic 6.1 does not support sticky session

    Dear Sir,
    Our system is migrating from Weblogic 5.1 to Weblogic 6.1. After testing on
    development environment, it is found that IIS proxy for 5.1 plug-in and Weblogic
    6.1 server is perfect match for our case. Since our appliction system hit some
    bugs of IIS proxy for 6.1. In development environment, one IIS match with one
    Weblogic.
    During production launch, another problem found. It seems that IIS proxy 5.1
    plug-in with Weblogic 6.1 does not support the sticky load balancing. A sticky
    service is one where a client sends its requests to the same instance and those
    requests are not redirected to other instances. In production, two IIS match with
    two Weblogic. Below is
    #WebLogicHost=10.0.3.12
    #WebLogicPort=8012
    WebLogicCluster=10.0.3.12:8012,10.0.3.13:8012
    COnnectionTimeoutSecs=10
    ConnectionRetrySecs=2
    ErrorPage=https://www.xxxx.com/eBank/sysnotready.htm
    CookieName=eBankingWebLogicSession
    Anyone have idea on out case?
    Thanks,
    KAI

    My test was with 6.1 SP3.
    The way to tell is by analyzing the cookie(JSESSIONID).
    Perhaps the behaviour changed post SP1. I can't say for sure.
    Eric
    "Gary Rudolph" <[email protected]> wrote in message
    news:[email protected]...
    Is that entirely true concerning you don't need the persistence set to
    replicated in the weblogic.xml to gain sticky load balancing?
    The reason I ask was that in our situation sticky wouldn't work without
    having the persistence set to replicated. This was with NSAPI and WLS 6.1
    SP1. The weblogic servers were configured in a weblogic cluster. So..based
    on this statement we should not have needed to set the persistence, but in
    practice we did for it to work.
    Gary
    "Eric Gross" <[email protected]> wrote in message
    news:[email protected]...
    I just checked, and you are correct. You just need to have clustering
    enabled in 6.1. You do not necessarily need to have persistence set to
    replicated.
    Of course, you won't get failover, but you will get the sticky load
    balancing.
    Regards,
    Eric
    "Ricky Wong" <[email protected]> wrote in message
    news:[email protected]...
    Why do we need to set session persistence to replicate in order to
    perform
    sticky load balancing ? There is no such requirement in WebLogic 5.1.
    As
    far
    as I know, the IIS plugin simply interprets the value of the sessioncookie,
    which should be embedded with the application server address, then
    forward
    the request to that particular application server.
    We didn't use session replication in our environment because not allsession
    variables are serializable.
    "Eric Gross" <[email protected]> wrote in message
    news:[email protected]...
    The problem you mentionned in the other newsgroup post has been
    fixed
    and
    will be in SP4. If you are in production or nearing production and
    need
    a
    resolution now, then please open a case with support.
    You should not need any other parameters to do the load balancing.
    But
    to
    have the sticky load balancing, you must make sure you have session
    persistence set to replicated for the webapp in question.
    I'm not sure I am understanding your 3rd question.
    In any case, my advice is to either wait for SP4 to bereleased(scheduled
    sometime this month) or if you really need to go into production
    soon,
    contact support to obtain the latest IIS plugin.
    Regards,
    Eric
    "Mike" <[email protected]> wrote in message
    news:[email protected]...
    Dear Eric,
    Thanks very much for you kindly information, but we still have thefollowing issues
    regarding the WL IIS proxy:
    1. We have already tried the IIS proxy that comes with WL6.1 SP3.However, the
    result from that version of IIS proxy is not satisfactory, as weexperienced cases
    where the web page is not displayed correctly (as in
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.develo
    per.interest.plug-in&item=994&utag=).
    If there is any IIS proxy released after WL6.1 SP3, Could you
    kindly
    give
    us
    a pointer to the plugin?
    2. In WL5.1 case, we are only required to have "WebLogicCluster"
    parameter
    set
    to two weblogic servers in order use the load balancing features.
    In
    WL6.1, we
    do not come across any additional settings required to support
    load
    balancing.
    Is there any such settings required (e.g. in
    config.xml,weblogic.xml,
    application.xml,
    etc?)
    3. Does WL IIS proxy problem has anything to do with the version
    of
    the
    IIS server/windows
    versions that are using? we have already tried with IIS4 and IIS5
    and
    have
    different
    kinds of issues.
    Thanks in advance for your kind assistance.
    Mike
    "Eric Gross" <[email protected]> wrote:
    Yes, the session format has changed when using clustering and you
    cannot
    use
    the 5.1 plugin to proxy to 6.1.
    What problems did you have using the 6.1 plugin? Maybe you need
    the
    latest
    6.1 plugin.
    Regards,
    Eric
    "KAI" <[email protected]> wrote in message
    news:[email protected]...
    Dear Sir,
    Our system is migrating from Weblogic 5.1 to Weblogic 6.1.
    After
    testing on
    development environment, it is found that IIS proxy for 5.1
    plug-in
    and
    Weblogic
    6.1 server is perfect match for our case. Since our appliction
    system
    hit
    some
    bugs of IIS proxy for 6.1. In development environment, one IIS
    match
    with
    one
    Weblogic.
    During production launch, another problem found. It seems
    that
    IIS
    proxy 5.1
    plug-in with Weblogic 6.1 does not support the sticky load
    balancing.
    A
    sticky
    service is one where a client sends its requests to the same
    instance
    and
    those
    requests are not redirected to other instances. In production,
    two
    IIS
    match with
    two Weblogic. Below is
    #WebLogicHost=10.0.3.12
    #WebLogicPort=8012
    WebLogicCluster=10.0.3.12:8012,10.0.3.13:8012
    COnnectionTimeoutSecs=10
    ConnectionRetrySecs=2
    ErrorPage=https://www.xxxx.com/eBank/sysnotready.htm
    CookieName=eBankingWebLogicSession
    Anyone have idea on out case?
    Thanks,
    KAI

  • Null keys not supported

    Hi. I have created a simple Entity Bean called User with just 2 fields and no business methods. I am using Personal Oracle8 database and sun's JdbcOdbcDriver. The connection pool is configured properly.
    When I try to deploy this bean, I get an error saying "Null keys not supported". I think it is a problem related to the driver. But is there any way to fix it without changing the driver.
    The detailed error message is as follows:
    Exception:weblogic.management.ApplicationException: activate failed for User Module: User Error: Exception activating module: EJBModule(User,status=PREPARED) Unable to deploy EJB: UserEJB from User.jar: Null keys not supported. Nested Exception: java.lang.IllegalArgumentException: Null keys not supported at weblogic.utils.collections.WeakConcurrentHashMap.get(WeakConcurrentHashMap.java:189) at weblogic.utils.wrapper.WrapperFactory.getCachedWrapperClass(WrapperFactory.java:51) at weblogic.utils.wrapper.WrapperFactory.getWrapperClass(WrapperFactory.java:183) at weblogic.utils.wrapper.WrapperFactory.getWrapperClass(WrapperFactory.java:171) at weblogic.jdbc.wrapper.JDBCWrapperFactory.getWrapper(JDBCWrapperFactory.java:146) at weblogic.jdbc.jts.Driver.newConnection(Driver.java:674) at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:196) at weblogic.jdbc.jts.Driver.connect(Driver.java:154) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305) at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247) at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyDatabaseType(RDBMSPersistenceManager.java:2459) at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:198) at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:253) at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:210) at weblogic.ejb20.manager.DBManager.setup(DBManager.java:154) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1057) at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1322) at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610) at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515) at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317) at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2399) at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2311) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2479) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    [Deployer:149033]preparing application User on SamServer
    [Deployer:149033]prepared application User on SamServer
    [Deployer:149033]activating application User on SamServer
    [Deployer:149033]failed application User on SamServer
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application User on SamServer.: Exception:weblogic.management.ApplicationException: activate failed for User Module: User Error: Exception activating module: EJBModule(User,status=PREPARED) Unable to deploy EJB: UserEJB from User.jar: Null keys not supported. Nested Exception: java.lang.IllegalArgumentException: Null keys not supported at weblogic.utils.collections.WeakConcurrentHashMap.get(WeakConcurrentHashMap.java:189) at weblogic.utils.wrapper.WrapperFactory.getCachedWrapperClass(WrapperFactory.java:51) at weblogic.utils.wrapper.WrapperFactory.getWrapperClass(WrapperFactory.java:183) at weblogic.utils.wrapper.WrapperFactory.getWrapperClass(WrapperFactory.java:171) at weblogic.jdbc.wrapper.JDBCWrapperFactory.getWrapper(JDBCWrapperFactory.java:146) at weblogic.jdbc.jts.Driver.newConnection(Driver.java:674) at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:196) at weblogic.jdbc.jts.Driver.connect(Driver.java:154) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305) at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247) at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyDatabaseType(RDBMSPersistenceManager.java:2459) at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:198) at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:253) at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:210) at weblogic.ejb20.manager.DBManager.setup(DBManager.java:154) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1057) at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1322) at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610) at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515) at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317) at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2399) at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2311) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2479) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170) .
    Regards,
    Sameer

    This is definitely a problem related to setting up and using the JDBC driver. I'd check with the JDBC newgroup if you have not done so already (then support if that doesn't go anywhere).
    -thorick

  • Error: Specified WebLogic home is not associated with given Middleware home

    Hi All,
    I am getting an error -"INST-07250: Specified WebLogic home is not associated with the given Middleware home" while configuring "bi domain".
    My requirement is to first install a domain in one host and then copy the installation to a different host so that domain can be configured in the new host.
    To make it run on the new host, I have modified the path of fusion home directory and host info in all the required files. But when I run the below script which configures "bi domain" and does silent installation, I get the above INST-07250 error.
    The paths of MW_HOME, WEBLOGIC_HOME, ORACLE_HOME and INSTALLER_DIR etc are as per the new host and correct.
    Script:
    $INSTALLER_DIR/runInstaller ORACLE_HOME="$ORACLE_HOME" -invPtrLoc $ORACLE_HOME/oraInst.loc -oneclick $COMMANDLINE -Doracle.config.mode=true
    The variables are:
    INSTALLER_DIR= /net/adc6260266/scratch/kumasaur/prov/apphome/fusionapps/bi/bin/../oui/bin
    ORACLE_HOME= /net/adc6260266/scratch/kumasaur/prov/apphome/fusionapps/bi
    COMMANDLINE= -weblogicConfigSilent -silent -waitForCompletion -responseFile /tmp/bi-facade-temp-dir505387909/configuration.rsp -jreLoc /scratch/kumasaur/prov/repos64ST3B17A/jdk6
    and the configuration.rsp file contents are:
    [ENGINE]
    #DO NOT CHANGE THIS.
    Response File Version=1.0.0.0.0
    [GENERIC]
    UNIX_GROUP_NAME=dba
    #Set this to true if you want to create a new domain, all other required variables need to be provided. If this is set to true then variables "SCALEOUT_BISYSTEM" must be set to false, since the variables are mutually exclusive.
    CREATE_BISYSTEM=true
    #Set this to true if you want to extend an already existing domain, all other required variables need to be provided. If this is set to true then variables "CREATE_BISYSTEM" must be set to false, since the variables are mutually exclusive.
    SCALEOUT_BISYSTEM=false
    #Write the name of the domain you want to create. Domain name may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters.
    DOMAIN_NAME=BIDomain
    #Write the name of the host to which you want to connect. It should have an already existing domain configured.
    DOMAIN_HOSTNAME=adc6260266.us.oracle.com
    #Give the port number at which the host should be connected.
    DOMAIN_PORT=
    #Give an administrator user name for the domain if you are creating a new one otherwise give the administrator user name for the domain configured at the host.
    ADMIN_USER_NAME=FUSION_APPS_PROV_PATCH_APPID
    #Give an administrator password for the domain if you are creating a new one otherwise give the administrator password for the domain configured at the host.
    ADMIN_PASSWORD=Bcu#favw2goh1m
    #Write the administrator password again to confirm.
    ADMIN_CONFIRM_PASSWORD=Bcu#favw2goh1m
    #Give the complete path to a valid Middleware Home.
    MW_HOME=/net/adc6260266/scratch/kumasaur/prov/apphome/fusionapps
    #Give the complete path to a valid WebLogic Server Home.
    WEBLOGIC_HOME=/net/adc6260266/scratch/kumasaur/prov/apphome/fusionapps/wlserver_10.3
    #Give the complete path for an Oracle Instance directory to be created. This is the location where the software configuration files and runtime processes will reside.
    INSTANCE_HOME=/net/adc6260266/scratch/kumasaur/prov/apphome/instance/BIInstance
    #Give a name for Oracle Instance corresponding to the Instance Home. The Oracle Instance name may only contain alphanumeric and underscore (_) characters, it must begin with an alphabetic (a-z or A-Z) character, and must be from 4 to 30 characters in length.
    INSTANCE_NAME=BIInstance
    #Give the complete path for a domain home to be created.
    DOMAIN_HOME_PATH=/net/adc6260266/scratch/kumasaur/prov/apphome/instance/domains/adc6260266.us.oracle.com/BIDomain
    #Format: hostname:port:servicename. For Application Cluster Database: host1:port1^host2:port2@servicename
    DATABASE_CONNECTION_STRING_BI=ap6055fems.us.oracle.com:1528:fadb04
    #Enter the BIPLATFORM schema username.
    DATABASE_SCHEMA_USER_NAME_BI=BIKUMASAUR_BIPLATFORM
    #Enter the BIPLATFORM schema password.
    DATABASE_SCHEMA_PASSWORD_BI=<SECURE VALUE>
    #Select the database type in which the BIPLATFORM schema exists. Supported database types are Oracle Database, Microsoft SQL Server, IBM DB2.
    DATABASE_TYPE_BI=Oracle Database
    #Format: hostname:port:servicename. For Application Cluster Database: host1:port1^host2:port2@servicename
    DATABASE_CONNECTION_STRING_MDS=ap6055fems.us.oracle.com:1528:fadb04
    #Enter the MDS schema username.
    DATABASE_SCHEMA_USER_NAME_MDS=FUSION_MDS
    #Enter the MDS schema password.
    DATABASE_SCHEMA_PASSWORD_MDS=<SECURE VALUE>
    #Select the database type in which the BIPLATFORM schema exists. Supported database types are Oracle Database, Microsoft SQL Server, IBM DB2.
    DATABASE_TYPE_MDS=Oracle Database
    AUTOMATIC_PORT_DETECT=false
    #Specify the full path to the staticports.ini file that lists the ports to use.
    STATICPORT INI FILE LOCATION=/scratch/kumasaur/prov/apphome/ports/bi_staticports.ini
    #Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
    MYORACLESUPPORT_USERNAME=
    #Provide the My Oracle Support Password
    MYORACLESUPPORT_PASSWORD=<SECURE VALUE>
    #Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle Support username will ignore the Oracle Configuration Manager configuration
    DECLINE_SECURITY_UPDATES=true
    #Set this to true if My Oracle Support Password is specified
    SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
    #Provide the Proxy Host
    PROXY_HOST=
    #Provide the Proxy Port
    PROXY_PORT=
    #Provide the Proxy Username
    PROXY_USER=
    #Provide the Proxy Password
    PROXY_PWD=<SECURE VALUE>
    #Provide the Password to encrypt the RPD
    RPD_ENCRYPTION_PASSWORD=<SECURE VALUE>
    #Confirm the RPD password
    RPD_CONFIRM_PASSWORD=<SECURE VALUE>
    [SYSTEM]
    [APPLICATIONS]
    #Set to true to configure Oracle Business Intelligence. Otherwise set to false.
    CONFIGURE_BI=true
    [RELATIONSHIPS]
    Any help to resolve this would be greatly appreciated.
    Thanks,
    Saurabh

    Hi All,
    I am getting an error -"INST-07250: Specified WebLogic home is not associated with the given Middleware home" while configuring "bi domain".
    My requirement is to first install a domain in one host and then copy the installation to a different host so that domain can be configured in the new host.
    To make it run on the new host, I have modified the path of fusion home directory and host info in all the required files. But when I run the below script which configures "bi domain" and does silent installation, I get the above INST-07250 error.
    The paths of MW_HOME, WEBLOGIC_HOME, ORACLE_HOME and INSTALLER_DIR etc are as per the new host and correct.
    Script:
    $INSTALLER_DIR/runInstaller ORACLE_HOME="$ORACLE_HOME" -invPtrLoc $ORACLE_HOME/oraInst.loc -oneclick $COMMANDLINE -Doracle.config.mode=true
    The variables are:
    INSTALLER_DIR= /net/adc6260266/scratch/kumasaur/prov/apphome/fusionapps/bi/bin/../oui/bin
    ORACLE_HOME= /net/adc6260266/scratch/kumasaur/prov/apphome/fusionapps/bi
    COMMANDLINE= -weblogicConfigSilent -silent -waitForCompletion -responseFile /tmp/bi-facade-temp-dir505387909/configuration.rsp -jreLoc /scratch/kumasaur/prov/repos64ST3B17A/jdk6
    and the configuration.rsp file contents are:
    [ENGINE]
    #DO NOT CHANGE THIS.
    Response File Version=1.0.0.0.0
    [GENERIC]
    UNIX_GROUP_NAME=dba
    #Set this to true if you want to create a new domain, all other required variables need to be provided. If this is set to true then variables "SCALEOUT_BISYSTEM" must be set to false, since the variables are mutually exclusive.
    CREATE_BISYSTEM=true
    #Set this to true if you want to extend an already existing domain, all other required variables need to be provided. If this is set to true then variables "CREATE_BISYSTEM" must be set to false, since the variables are mutually exclusive.
    SCALEOUT_BISYSTEM=false
    #Write the name of the domain you want to create. Domain name may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters.
    DOMAIN_NAME=BIDomain
    #Write the name of the host to which you want to connect. It should have an already existing domain configured.
    DOMAIN_HOSTNAME=adc6260266.us.oracle.com
    #Give the port number at which the host should be connected.
    DOMAIN_PORT=
    #Give an administrator user name for the domain if you are creating a new one otherwise give the administrator user name for the domain configured at the host.
    ADMIN_USER_NAME=FUSION_APPS_PROV_PATCH_APPID
    #Give an administrator password for the domain if you are creating a new one otherwise give the administrator password for the domain configured at the host.
    ADMIN_PASSWORD=Bcu#favw2goh1m
    #Write the administrator password again to confirm.
    ADMIN_CONFIRM_PASSWORD=Bcu#favw2goh1m
    #Give the complete path to a valid Middleware Home.
    MW_HOME=/net/adc6260266/scratch/kumasaur/prov/apphome/fusionapps
    #Give the complete path to a valid WebLogic Server Home.
    WEBLOGIC_HOME=/net/adc6260266/scratch/kumasaur/prov/apphome/fusionapps/wlserver_10.3
    #Give the complete path for an Oracle Instance directory to be created. This is the location where the software configuration files and runtime processes will reside.
    INSTANCE_HOME=/net/adc6260266/scratch/kumasaur/prov/apphome/instance/BIInstance
    #Give a name for Oracle Instance corresponding to the Instance Home. The Oracle Instance name may only contain alphanumeric and underscore (_) characters, it must begin with an alphabetic (a-z or A-Z) character, and must be from 4 to 30 characters in length.
    INSTANCE_NAME=BIInstance
    #Give the complete path for a domain home to be created.
    DOMAIN_HOME_PATH=/net/adc6260266/scratch/kumasaur/prov/apphome/instance/domains/adc6260266.us.oracle.com/BIDomain
    #Format: hostname:port:servicename. For Application Cluster Database: host1:port1^host2:port2@servicename
    DATABASE_CONNECTION_STRING_BI=ap6055fems.us.oracle.com:1528:fadb04
    #Enter the BIPLATFORM schema username.
    DATABASE_SCHEMA_USER_NAME_BI=BIKUMASAUR_BIPLATFORM
    #Enter the BIPLATFORM schema password.
    DATABASE_SCHEMA_PASSWORD_BI=<SECURE VALUE>
    #Select the database type in which the BIPLATFORM schema exists. Supported database types are Oracle Database, Microsoft SQL Server, IBM DB2.
    DATABASE_TYPE_BI=Oracle Database
    #Format: hostname:port:servicename. For Application Cluster Database: host1:port1^host2:port2@servicename
    DATABASE_CONNECTION_STRING_MDS=ap6055fems.us.oracle.com:1528:fadb04
    #Enter the MDS schema username.
    DATABASE_SCHEMA_USER_NAME_MDS=FUSION_MDS
    #Enter the MDS schema password.
    DATABASE_SCHEMA_PASSWORD_MDS=<SECURE VALUE>
    #Select the database type in which the BIPLATFORM schema exists. Supported database types are Oracle Database, Microsoft SQL Server, IBM DB2.
    DATABASE_TYPE_MDS=Oracle Database
    AUTOMATIC_PORT_DETECT=false
    #Specify the full path to the staticports.ini file that lists the ports to use.
    STATICPORT INI FILE LOCATION=/scratch/kumasaur/prov/apphome/ports/bi_staticports.ini
    #Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
    MYORACLESUPPORT_USERNAME=
    #Provide the My Oracle Support Password
    MYORACLESUPPORT_PASSWORD=<SECURE VALUE>
    #Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle Support username will ignore the Oracle Configuration Manager configuration
    DECLINE_SECURITY_UPDATES=true
    #Set this to true if My Oracle Support Password is specified
    SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
    #Provide the Proxy Host
    PROXY_HOST=
    #Provide the Proxy Port
    PROXY_PORT=
    #Provide the Proxy Username
    PROXY_USER=
    #Provide the Proxy Password
    PROXY_PWD=<SECURE VALUE>
    #Provide the Password to encrypt the RPD
    RPD_ENCRYPTION_PASSWORD=<SECURE VALUE>
    #Confirm the RPD password
    RPD_CONFIRM_PASSWORD=<SECURE VALUE>
    [SYSTEM]
    [APPLICATIONS]
    #Set to true to configure Oracle Business Intelligence. Otherwise set to false.
    CONFIGURE_BI=true
    [RELATIONSHIPS]
    Any help to resolve this would be greatly appreciated.
    Thanks,
    Saurabh

  • Getting compilation error: java.util.Set is an interface. This interface is not supported.

    Hi Folks,
    Is there a limitation in BEA's web services implementation? I have a simple web
    service that returns an array of java objects. However I am calling another middle
    tier API that returns a Set. I convert this Set into array of object and return
    it via the web service.
    However the .jws file that implements the webservice does not compile. I get the
    following error message:
    java.util.Set is an interface. This interface is not supported.
    Is there a limitation on using Collections within the .jws file? If that is the
    case it is a severe limitation.
    Note my Web Service API returns an array of java objects with no collections in
    them.
    Sanjay

    Hello,
    Generic java collections can only be handled in a very generic, weakly
    typed manner.
    Take a look at the
    http://workshop.bea.com/xmlbeans/guide/conXMLBeansSupportBuiltInSchemaTypes.html
    and also
    http://workshop.bea.com/xmlbeans/guide/conJavaTypesGeneratedFromUserDerived.html
    You might also ask your question to the XMLBeans newsgroup:
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.xmlbeans
    Regards,
    Bruce
    Sanjay wrote:
    >
    Hi Folks,
    Is there a limitation in BEA's web services implementation? I have a simple web
    service that returns an array of java objects. However I am calling another middle
    tier API that returns a Set. I convert this Set into array of object and return
    it via the web service.
    However the .jws file that implements the webservice does not compile. I get the
    following error message:
    java.util.Set is an interface. This interface is not supported.
    Is there a limitation on using Collections within the .jws file? If that is the
    case it is a severe limitation.
    Note my Web Service API returns an array of java objects with no collections in
    them.
    Sanjay

  • Protocol remote_JDBC not support

    When deploy the project using BPM Admin Center, when starting the weblogic server..
    the error shows:
    protocol remote_JDBC not support for eng-bpmengine.......

    Hi,
    Is this this is the first project you've deployed on an Engine you've just installed? Knowing this will help us understand if you have a problem in one of the external resources in your project or if you had a problem caused by the installation.
    If this is a new Engine, did you use the installation wizard that comes with Oracle BPM 10g? How did you answer the database information for the Directory Service and the Engine? Did you allow the wizard to create a new J2EE domain or did you try to use an existing one (I struggle using the wizard using an existing domain during the installation and get a similar error when I do so)?
    Thanks,
    Dan

Maybe you are looking for