Weblogic 10MP1 - is it version 10.0.1?

I am a bit confused with WebLogic's versioning and I need to clarify:
We have this in registry.xml:
<component name="WebLogic Server" version="10.0.1.0">
Does it mean we have Weblogic 10MP1?
Thank you,
Adam

Hi,
Your correct it means WLS 10.0 MP1
Regards,
Kal

Similar Messages

  • I've extended java.lang.Thread.  How do I get WebLogic to use my version?

    I want to add a String attribute to the thread class to save some extra info I need. I extended the Thread class with a private String with getter/setter methods.
    Since WebLogic instantiates the threads and not my own code, how do I get WebLogic to use my version of Thread instead of the one from java.lang?
    -Bill

    I don't think it's possible to have WLS use your own thread implementation for WLS internals. However, for your own custom work, it's pretty straight-forward to use the CommonJ Work Manager API and add your own implementation details for a thread pool.
    See documentation: http://download.oracle.com/docs/cd/E12839_01/web.1111/e13701/self_tuned.htm#i1069944
    WorkManager Javadocs: http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13941/index.html?commonj/work/WorkManager.html
    Specifically providing your own Work interface implementation should hopefully allow you to meet your need.
    Edited by: james.bayer on Feb 15, 2010 6:40 AM

  • Is able to run two webservices in Weblogic 7.0 trial version ?

    Hi all:
    I caught a webservice problem in weblogic7.0 (trial version).
    I have built an Session Bean example (examples\webservices\complex\statelessSession)
    in Weblogic 7.0 Examples Service, it works as expected.
    However, when I create another session bean following the above example with different
    Service Name and JNDI Name, the new session bean cannot work as expected(No WSDL
    URL is found).
    Is able to run two webservices in Weblogic 7.0 trial version?
    How can I run two and more webservices in Weblogic 7.0 trial version?
    If anyone know how to solve it, please reply me as soon as possible.

    Hi Kelvin,
    Could you check your server log file for any errors. If there are errors, would you post them here. It sounds like the second webservice is simply not being
    deployed for some reason.
    In the application.xml, make sure you have given each webservice a different <context-root>
    As a suggestion, make the <display-name> and the <context-root> the same, for example using: "TreeClock" then you should be able to find the webservice:
    http://<host>:<port>/TreeClock/TreeClock
    Bruce
    Kelvin wrote:
    Bruce:
    Thanks your help !!! Sorry to confuse you as we are actually using the GA version
    (download form BWA for evaluation).
    The problem is like this, when we developed two web service and deploy both.
    Only one of them can show up by quene the ?wsdl.
    Any additional info that we can provide ???
    Many thanks !!!
    Regards
    Kelvin
    Bruce Stephens <[email protected]> wrote:
    Hi Kelvin,
    By "trial version" if you mean the WLS 7.0 Beta program, thanks for giving
    this a spin
    however the final version of WLS 7.0 was Generally Available as of 4/30/02
    and the Beta
    program closed.
    We have an example that illustrates how to build a client that invokes two
    webservices.
    You can get a copy from the dev2dev center:
    http://dev2dev.bea.com/managed_content/direct/webservice/simple2.zip
    Hope this helps,
    Bruce
    Kelvin wrote:
    Hi all:
    I caught a webservice problem in weblogic7.0 (trial version).
    I have built an Session Bean example (examples\webservices\complex\statelessSession)
    in Weblogic 7.0 Examples Service, it works as expected.
    However, when I create another session bean following the above examplewith different
    Service Name and JNDI Name, the new session bean cannot work as expected(NoWSDL
    URL is found).
    Is able to run two webservices in Weblogic 7.0 trial version?
    How can I run two and more webservices in Weblogic 7.0 trial version?
    If anyone know how to solve it, please reply me as soon as possible.<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
    <html>
    Hi Kelvin,
    <p>By "trial version" if you mean the WLS 7.0 Beta program, thanks for
    giving this a spin however the final version of WLS 7.0 was Generally Available
    as of 4/30/02 and the Beta program closed.
    <p>We have an example that illustrates how to build a client that invokes
    two webservices. You can get a copy from the dev2dev
    center:
    <p>http://dev2dev.bea.com/managed_content/direct/webservice/simple2.zip
    <br>
    <p>Hope this helps,
    <br>Bruce
    <br>
    <p>Kelvin wrote:
    <blockquote TYPE=CITE>Hi all:
    <p>I caught a webservice problem in weblogic7.0 (trial version).
    <p>I have built an Session Bean example (examples\webservices\complex\statelessSession)
    <br>in Weblogic 7.0 Examples Service, it works as expected.
    <br>However, when I create another session bean following the above example
    with different
    <br>Service Name and JNDI Name, the new session bean cannot work as expected(No
    WSDL
    <br>URL is found).
    <p>Is able to run two webservices in Weblogic 7.0 trial version?
    <br>How can I run two and more webservices in Weblogic 7.0 trial
    version?
    <p>If anyone know how to solve it, please reply me as soon as possible.</blockquote>
    </html>

  • No output at all from weblogic.Admin HELP | GETSTATE | VERSION on linux

    Hi, somehow I am getting zero output from weblogic.Admin command, is it redirected somewhere?
    #>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD VERSION
    #>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD GETSTATE
    #>
    #>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -username weblogic -password $WPWD HELP
    #>
    Thanks.

    Hi,
    You need to Run the SetDomainEnv.sh/cmd from the Domain_Home/bin and then you can execute the below Commands and they will execute succesfully
    Eg:From Windows Environment Same applies in Linux Environmet as well
    C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl  t3://localhost:7001  -username weblogic -password weblogic1 VERSION
    WebLogic Server 10.3.5.0  Fri Apr 1 20:20:06 PDT 2011 1398638
    C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl  t3://localhost:7001  -username weblogic -password weblogic1 GETSTATE
    Current state of "AdminServer" : RUNNING
    C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl  t3://localhost:7001  -username weblogic -password weblogic1 HELP
    Usage: java [<SSL trust options>] weblogic.Admin
            [ [-url | -adminurl] [<protocol>://]<listen-address>:<port>]
            -username <username> [-password <password>]
            <COMMAND> <ARGUMENTS>
    Hope it helps

  • Where Is weblogic.WLST Installed? (Version 10.3)

    I've installed Weblogic Server 10.3 (Oracle WebLogic Server 11gR1 (10.3.1) - Package Installer). I want to use weblogic.WLST but it does not seem like it got installed? What am I missing.
    Thank you

    This was helpful, thank you.
    I read through the cited example however I was unable to find a 'weblogic.WLST' anywhere under $WL_HOME. Then I stumbled across a $WL_HOME/wlserver_10.3/common/bin/*wlst.sh*. I found that I can invoke that script and be placed at a WLST prompt. I was then able to start the node manager and Admin Server using WLST.
    I wonder what happened to 'weblogic.WLST', maybe this wlst.sh is it's replacement in version 10.3?
    In the end, I had problems starting a Managed Server, and I've been reading through the doc a good part of the day so I think I'm going to start a new thread on that problem.
    Thank you!

  • Can weblogic server 5.1 version work with Oracle 9.2.0 thin JDBC driver?

    we have an applicaiton using weblogic 5.1 and Oracle database 8.1.6. Is that possible
    to upgrade databse version to Oracle 9i without weblogic upgrade? If yes, what
    JDBC driver should be used? Oracle 9.2.0 thin JDBC driver or weblogic jDriver?
    Is there any known issue with the JDBC driver under that architecture?
    Please help.

    Lei Zeng wrote:
    we have an applicaiton using weblogic 5.1 and Oracle database 8.1.6. Is that possible
    to upgrade databse version to Oracle 9i without weblogic upgrade? If yes, what
    JDBC driver should be used? Oracle 9.2.0 thin JDBC driver or weblogic jDriver?
    Is there any known issue with the JDBC driver under that architecture?
    Please help.Hi. Any weblogic server can be used with any JDBC driver. Just upgrade the
    JDBC driver to the latest/best one for Oracle9i, and make sure it's the first
    thing in the server's weblogic.classpath (not the java.classpath). I recommend the
    thin driver. Because it's all java, it is much more reliable. There is no known
    issue with standard JDBC with that or any other driver. Some non-standard Oracle
    calls which arer available from Oracle's driver classes are available through
    weblogic, and some are not.
    Joe Weinstein

  • Weblogic 10.3 - Ant version conflict - help with filtering

    I'm trying to deploy Hudson on WebLogic 10.3
    I first got an error saying Hudson needs Ant 1.7 and WebLogic loaded Ant 1.6.5 so I set prefer-web-inf-classes to true in weblogic.xml
    After this I got another error:
    java.lang.LinkageError: Class org/xml/sax/XMLReader violates loader constraints
         at org.apache.commons.jelly.parser.XMLParser.getXMLReader(XMLParser.java:496)
         at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:312)
         at org.apache.commons.jelly.JellyContext.compileScript(JellyContext.java:521)
    Apparently some of the Hudson jar files contain org.xml.sax.XMLReader which is a different version than what weblogic has loaded.
    I'm now trying to do go back and instead of prefer-web-inf-classes use prefer-application-packages in weblogic-application.xml
    <prefer-application-packages>
              <package-name>org.apache.tools.ant.*</package-name>
              <package-name>antlr.*</package-name>
         </prefer-application-packages>
    but Hudson webapp still complains "Ant classes are loaded from M:\bea\modules\org.apache.ant_1.6.5\lib\ant.jar"
    do I have to specify every package in the prefer-application-packages or is the wildcard enough ?
    I'm now stuck as to what to do next

    Not that this would solve your problem, but googling for that error message ("XMLReader violates loader constraints") finds someone who has the exact same problem with Hudson (I hope it's not you), and that OC4J demonstrates the same symptom.
    [http://www.nabble.com/Can%27t-deploy-Hudson-to-weblogic-td18116993.html|http://www.nabble.com/Can%27t-deploy-Hudson-to-weblogic-td18116993.html]

  • Weblogic SAAJ implementation and version problem

    I have a problem with Weblogic 9.0 using its own implementation over the one i provide.
              I have tried putting the saaj-api.jar and saaj-impl.jar in my domains lib/ catalog as well as the domains config/lib/ catalog.
              I also tried PRE_CLASSPATH in setDomainEnv.cmd but it seems the weblogic implementation is being used anyway!
              Any ideas how to solve this?
              Here are a couple of exceptions i get after a context lookup and getConnection of the resource adapter:
              Caused by: javax.xml.soap.SOAPException: Unable to create SOAP connection factory: com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory
                   at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
                                  I also tried adding a property value:
                        System.setProperty("javax.xml.soap.SOAPConnectionFactory", "com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory");
                        in the web app before doing the context lookup, and then i get this exception:
                        java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1
              at weblogic.webservice.core.soap.SOAPElementImpl.getElementsByTagNameNS(SOAPElementImpl.java:527)
              

    Was this problem solved in the latest version of Bea Weblogic 9.2?
              I have an issue on soap 1.2 support activation (through Binding.Type.SOAP12):
              java.lang.RuntimeException: weblogic.testclient.WsdlParseFailedException: SOAP 1.2 is not supported by the Test Client
              at weblogic.testclient.ConnectionState.createWsdl(ConnectionState.java:63)
              at Controller.refreshWsdl(Controller.java:437)
              at Controller.begin(Controller.java:285)
              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:585)
              at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:878)
              at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:808)
              at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:477)
              at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:305)
              at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:335)
              at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:51)
              at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:95)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2042)
              at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:90)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2114)
              at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:554)
              at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851)
              at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630)
              at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157)
              at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
              at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
              at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
              at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
              at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
              at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3241)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
              at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
              at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
              at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
              at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
              at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
              Caused by: weblogic.testclient.WsdlParseFailedException: SOAP 1.2 is not supported by the Test Client
              at weblogic.testclient.WsdlOperationParser.createOperation(WsdlOperationParser.java:38)
              at weblogic.testclient.WebService.createOperation(WebService.java:251)
              at weblogic.testclient.WebService.<init>(WebService.java:88)
              at weblogic.testclient.Wsdl.parseWsdl(Wsdl.java:135)
              at weblogic.testclient.Wsdl.<init>(Wsdl.java:60)
              at weblogic.testclient.ConnectionState.createWsdlFromHttpUrl(ConnectionState.java:120)
              at weblogic.testclient.ConnectionState.createWsdl(ConnectionState.java:54)
              ... 37 more

  • Weblogic 9.1 and Weblogic 6.1 "Incompatible versions " error

    Hi,
    When i tried to create InitalContext object on Weblogic 9.1 It gives me following error.
    <i>"javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login f
    ailed: 'Incompatible version: Incompatible versions - this server:6.1.7.0 client:9.1.0]]"</i>
    The EJB is deployed on Weblogic 6.1 and client deployed on Weblogic 9.1 trying to access that EJB.
    Please let me know how to resolve this issue.
    Regards
    Jagat Kansara

    Hi,
    When i tried to create InitalContext object on Weblogic 9.1 It gives me following error.
    <i>"javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login f
    ailed: 'Incompatible version: Incompatible versions - this server:6.1.7.0 client:9.1.0]]"</i>
    The EJB is deployed on Weblogic 6.1 and client deployed on Weblogic 9.1 trying to access that EJB.
    Please let me know how to resolve this issue.
    Regards
    Jagat Kansara

  • Weblogic.appc compiler for Weblogic 9 and higher version

    We had problem precompiling the jsp's using weblogic.jspc compiler after migrating the project from 8.1 to 9.2. From the edocs weblogic documentation we see that jspc compiler is deprecated from weblogic 9 onwards and they recommend using weblogic.appc for precompiling the jsp's.
    Please note if you are passing runtime expression values in the name attribute of the jsp param tag, you will have to explicitly enabke "<rtexprvalue-jsp-param-name>" to true in weblogic.xml deployment descriptor (format shown below).
    <weblogic-web-app>
    <jsp-descriptor>
    <rtexprvalue-jsp-param-name>true</rtexprvalue-jsp-param-name>
    </jsp-descriptor>
    </weblogic-web-app>
    Below is the edocs link which has JSP descriptors information for Weblogic 9,2
    http://e-docs.bea.com/wls/docs92/webapp/weblogic_xml.html#wp1038491
    - - Tarun

    The solution given in the below link worked for me .
    http://a-developer-life.blogspot.com/2010/11/injecting-into-ejb3-with-google-guice.html?showComment=1328674836129#c7251888680841418914

  • Does weblogic server 6.1 version allows installation in target destination having spaces?

    All BEA users,
    I am facing some BEA related problem.
    I am writing a installer that silently installs BEA 6.1.
    The installer then calls a cmd file that will create a windows service and later
    will start this service.
    What I have noticed is that if I give the destination path as say
    "C:\Program Files\CompanyName\ProductName" then it creates the windows service
    but it doesnot start the service.
    Whereas if I give the path as say "C:\CompanyName\ProductName" then it creates
    and starts the service.
    I wanted to know whether this is a limitation with BEA? I haven't read any where
    about this limitation in the BEA site.
    Thanks in advance,
    A

    All BEA users,
    I am facing some BEA related problem.
    I am writing a installer that silently installs BEA 6.1.
    The installer then calls a cmd file that will create a windows service and later
    will start this service.
    What I have noticed is that if I give the destination path as say
    "C:\Program Files\CompanyName\ProductName" then it creates the windows service
    but it doesnot start the service.
    Whereas if I give the path as say "C:\CompanyName\ProductName" then it creates
    and starts the service.
    I wanted to know whether this is a limitation with BEA? I haven't read any where
    about this limitation in the BEA site.
    Thanks in advance,
    A

  • WebLogic 11g: Weblogic-Application-Version not taken into account

    Hello,
    I'm trying to set up Production Redeployment on my EAR, under WebLogic 10.3.6.
    However, I can't figure out how to make Weblogic-Application-Version work in MANIFEST.MF
    Here is my EAR structure:
    MyApplication
    --- APP-INF
    --- --- lib
    --- --- classes
    --- META-INF
    --- --- application.xml
    --- --- weblogic-application.xml
    --- --- MANIFEST.MF <- file I update
    --- WebApp1
    --- --- META-INF
    --- --- --- MANIFEST.MF
    --- --- WEB-INF
    --- --- --- classes
    --- --- --- lib
    --- --- --- web.xml
    --- --- --- weblogic.xml
    --- WebApp2
    --- --- same as WebApp1
    MANIFEST.MF content is the following:
    Manifest-Version: 1.0
    Weblogic-Application-Version: VERSION_1
    The problem is that it's not taken into account when I deploy the application in the WebLogic console.
    When I use staged mode, the line Weblogic-Application-Version: VERSION_1 is removed from the staged MANIFEST.MF file.
    The only way to manage to version my application is to add the flag -appversion to weblogic.Deployer, but I don't want to use that on a Production environment (and it's not recommended in the documentation!).
    Any idea why Weblogic-Application-Version not taken into account? I tried to add debug mode to node weblogic/debug but with no success.
    Thanks by advance,
    Julien

    I tested it at my end and was able to redeploy it successfully with the application versions.
    Are you saying that by deploying through weblogic console,the archive version is not honoring/getting picked up .is that correct?
    if yes, what does your weblogic console shows for archive version,when you first try to deploy your application with the VERSION_1.
    I mean,when you are on the "Optional Settings" Page.Do you see the Archive Version as VERSION_1?
    Deployments >> Click on the Install >> select your application ( MyAPP)>> Install this deployment as an application >> Select deployment targets >> Optional Settngs
    Example from the Optional settings Page for My application
    What do you want to name this deployment?
    Name: MyAPP     
    Archive Version:     
    VERSION_1
    This can confirm that the application being deployed is versioned one and if it doesn't shows up,then you need to check why its not getting picked up.?
    Moreover,You can enable the "deploy" debug flag to see whats going wrong in your case during the deployment process
    Server > Debug > Weblogic > Deploy
    Do refer the below viewlet on the Production Redeployment
    http://download.oracle.com/otn_hosted_doc/wls/redeployment/wls-side-by-side-non-annotation_viewlet_swf.html

  • Weblogic Server Advantage version

    Hi All,
    I am planning to upgrade weblogic server (Base) Advantage version 6.1 SP4 to Weblogic Server Advantage 8.1 non production.
    I tried logging the upgrade through the support site.
    The site provided us upgrade option as
    Lic, WLS Base v8.1
    I would like to know if there is a difference between
    WLS Base v8.1
    and
    Weblogic Server Advantage 8.1 non production.
    Thanks for your support.

    Hi Deena
    1. Always go with the latest version of Weblogic Portal which is currently 10.3.2.
    2. There may be many internal bug fixes from older versions that got fixed in 10.3.2. If you download or user older versions, you may need to apply all Patches for exsiting bugs. So go with latest.
    3. One major difference is, latest WLP 10.3.2 uses full fledged 100% Eclipse IDE. So you are now using more standard/universal IDE. Earlier versions had BEA Customized eclipse kind of IDE we usually call Workshop. But latest uses full Eclipse IDE. Since it is Eclipse, you can add any 3rd party reusable plugins for this IDE like db explorer etc.
    4. One other thing is older version of WLP used default Embedded LDAP for all security roles, policies stuff. But latest WLP 10.3.2, used RDBMS database to store all this stuff.
    Bottom line, go with the latest version of WLP and you can avoid any upgrades also for some time.
    Thanks
    Ravi Jegga

  • [weblogic 8.1-sp4] standard taglib versions

    today i got "java.lang.ClassCastException: javax.servlet.jsp.jstl.fmt.LocalizationContext". in my application i include jstl-1.0.6.jar, so i guess weblogic uses some other version of jstl-related classes, but i couldn't even find these in server classpath.
    so my question is which exact version of jstl weblogic does use and where it keeps corresponding jars (or classes)?

    i mean the location of "default" jstl classes that comes with weblogic distribution. my 1.0.6 conflicts with these, otherwise i don't see any logical explanation for CCE not even in my code:
    java.lang.ClassCastException: javax.servlet.jsp.jstl.fmt.LocalizationContext
         at org.apache.taglibs.standard.tag.common.fmt.BundleSupport.getLocalizationContext(Ljavax.servlet.jsp.PageContext;)Ljavax.servlet.jsp.jstl.fmt.LocalizationContext;(BundleSupport.java:127)
         at org.apache.taglibs.standard.tag.common.fmt.MessageSupport.doEndTag()I(MessageSupport.java:152)
         at jsp_servlet._web_45_inf._jsp._templates.__template._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(__template.java:235)

  • Weblogic server 10.0 MP2 version compatibility with EJB3.0

    Is it ok to use EJB3.0 in 10.0 MP2 ?
    Are there any pitfalls or problems with EJB3.0 implementation with webloigc 10.0 MP2 version?
    Currently we are using weblogic 10.0 MP2 version and planning to use EJB3.0 for one of our projects.
    Do we still need to go to weblogic 10.3 for using EJB 3.0 or can we stick with webloigc 10.0 MP2 version
    As per weblogic 10.0 documentation EJB3.0 is supported and JDK version used is 1.5. - http://docs.oracle.com/cd/E13222_01/wls/docs100/pdf/notes.pdf
    Thanks
    Deena

    Hi Anup,
    Maybe you should be a bit more specific about what you want to do. Coherence is just Java and has been supported WebLogic for years in the same way most other third-party Java libraries and APIs are. I first started using Coherence about four or five years ago with WebLogic 8.
    JK

Maybe you are looking for