Migration from tomcat to weblogic 10.3.2

Hi,
I am developing a web application, its a servlet which basically acts as a front end for a web service,
and I use CXF for the web service client, tested under a development tomcat instance and worked fine.
I have the spring framework and the rest jars in the lib:
wsdl4j-1.6.1.jar
wss4j-1.5.8.jar
jaxb-api-2.0.jar
cxf-2.2.3.jar
while I try to migrate to weblogic 10.3.2 follow the change as in
http://cxf.apache.org/docs/application-server-specific-configuration-guide.html#ApplicationServerSpecificConfigurationGuide-WebLogic
Then I got the exception:
java.lang.IncompatibleClassChangeError: Class com.ibm.wsdl.DefinitionImpl does not implement the requested interface javax.wsdl.extensions.AttributeExtensible
at org.apache.cxf.wsdl11.WSDLServiceBuilder.copyExtensionAttributes(WSDLServiceBuilder.java:137)
at org.apache.cxf.wsdl11.WSDLServiceBuilder.buildServices(WSDLServiceBuilder.java:277)
I have been research on this problem for a while, found some posts from experts like Dan on Nable...
but I still didn't get it, could anyone help on this.
Joelking

can u let us know how did you resolve this?

Similar Messages

Problem with servlet after migrating from OC4J to WebLogic 10.3

I come across a problem when I was migrating from jDev 11g TP4 to production version in that step also server got changed from OC4J to webLogic.
I am running java http servlet along other jspx pages. When everything was on OC4J there was no problem whit security on this servlet ( servlet was under same authorization automatically, and I was able to create new application module on this servlet by createRootApplicationModule
) but when I changed to WebLogic 10.3 I come across a numerous problems. First one is solved i managed to put the servlet under same authorization as jspx pages by
*<servlet>*
*<servlet-name>report</servlet-name>*
*<servlet-class>path.to.class</servlet-class>*
*<security-role-ref>*
*<role-name>name</role-name>*
*<role-link>valid-users</role-link>*
*</security-role-ref>*
*</servlet>*
but when I trying to create new application module I get JBO-30003 error which is Caused by:
oracle.adf.share.security.ADFSecurityAuthenticationException: JAAS login error.
Invalid null input: name
Has anybody any idea what I am doing wrong?
Thank you for your help, Rok Kogov&scaron;ek

for example:
web.xml
<security-role>
<role-name>yourrole</role-name>
</security-role>
weblogic.xml
<security-role-assignment>
<role-name>yourrole</role-name>
<principal-name>wlsuser</principal-name > 
</security-role-assignment>

Error in deploying entity beans - migration from JBoss to Weblogic 10.3.4

Hi,
I am migrating EJB2.x code from JBoss to Weblogic 10.3.4. As a first step, I am tyring to deploy just Entity beans. I get following error when deploying to server.
'weblogic.application.ModuleException: Exception preparing module: EJBModule(myEJB.jar)
Unable to deploy EJB: CollMetaData from myEJB.jar:
[EJB:011017]Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was:
There are 1 nested errors:
java.lang.NullPointerException
     at weblogic.ejb.container.cmp.rdbms.finders.EjbqlFinder.setMethods(EjbqlFinder.java:288)
     at weblogic.ejb.container.cmp.rdbms.Deployer.processFinders(Deployer.java:744)
     at weblogic.ejb.container.cmp.rdbms.Deployer.readTypeSpecificData(Deployer.java:446)
     at weblogic.ejb.container.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:506)
     at weblogic.ejb.container.persistence.PersistenceType.setupDeployer(PersistenceType.java:455)
     at weblogic.ejb.container.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:118)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1214)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Can someone help me fixing the issue?
I changed schema locations of descriptor files as suggested at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13706/overview.htm#i1074199 (see the third category for '*Enterprise Bean 2.1*' in the listing Table 1-1). Alternatively, you may see the schema locations for EJB2.0 directly at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13719/dd_reference.htm#EJBPG481

JRE version in JBoss is 1.6.0_16. JVM in web logic is pointing to jrockit_160_22_D1.1.1-3 which is come in the package. It doesn't seem to be related to JVM version mismatch.
I think it is an issue with definitions in weblogic-cmp-rdbms-jar.xml file. How should be the definition of entity-descriptor appear for entity bean which has finder methods in ejb-jar.xml?
Please see the snippets from corresponding descriptor files below.
ejb-jar.xml
=========
<entity>
<display-name>EmpBean</display-name>
<ejb-name>EmpBean</ejb-name>
<local-home>LocalEmpBeanHome</local-home>
<local>LocalEmpBean</local>
<ejb-class>EmpBeanBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>EmpBean</abstract-schema-name>
<cmp-field>
<field-name>firstName</field-name>
</cmp-field>
<cmp-field>
<field-name>lastName</field-name>
</cmp-field>
<cmp-field>
<field-name>phone</field-name>
</cmp-field>
<cmp-field>
<field-name>address</field-name>
</cmp-field>
<primkey-field>lastName</primkey-field>
<query>
<query-method>
          <method-name>findByPrimaryKey</method-name>
               <method-params>
               <method-param>java.lang.String</method-param>
               </method-params>
          </query-method>
          <ejb-ql>SELECT Object(o) FROM EmpBean o WHERE o.lastName= ?1</ejb-ql>
     </query>
</entity>
weblogic-jar.xml
============
<weblogic-enterprise-bean>
<ejb-name>EmpBean</ejb-name>
<entity-descriptor>
     <pool>
          <max-beans-in-free-pool>20</max-beans-in-free-pool>
          <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
     </pool>
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>meta-inf/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-use>
<finders-load-bean>true</finders-load-bean>
</persistence>
</entity-descriptor>
<local-jndi-name>ejb/EmpBean</local-jndi-name>
</weblogic-enterprise-bean>
weblogic-cmp-rdbms-jar.xml
====================
<weblogic-rdbms-bean>
<ejb-name>EmpBean</ejb-name>
<data-source-jndi-name>mysqlDS</data-source-jndi-name>
<table-map>
<table-name>emp</table-name>
<field-map>
<cmp-field>firstName</cmp-field>
<dbms-column>first_namel</dbms-column>
</field-map>
<field-map>
<cmp-field>lastName</cmp-field>
<dbms-column>last_name</dbms-column>
</field-map>
<field-map>
<cmp-field>phone</cmp-field>
<dbms-column>phone</dbms-column>
</field-map>
<field-map>
<cmp-field>address</cmp-field>
<dbms-column>address</dbms-column>
</field-map>
</table-map>
<weblogic-rdbms-bean>
Please ignore any typos that you may notice in above sample descriptions (because I just typed it here changing original names).
When I try to deploy the application, I get error message as posted in my first post above in this thread. Please correct me if I am making any erros in descriptor files.
Edited by: 839281 on Feb 25, 2011 10:55 AM
Edited by: venkatp on Mar 1, 2011 9:31 AM

Deploying ear application - migrating from OC4j to Weblogic

I am trying to migrate application from OC4J to weblogic server. Apart from usual differences in descriptors, structure of EAR etc. I came across unusual error:
"both the remote home and remote component interface must be specified. Currently, only one of them is specified"
It is about deploying session bean. Usual EJB3 stateless session bean with local and remote interface, deployed without any problem on OC4J and JBoss. Of course, I know home interfaces are something to do with EJB 2.1, but this is EJB3 application and, I guess, Weblogic has full support for it. Does it? :)
Anyway, is there workaround? Or am I missing something? I don't have to tell you what problems we will be facing if I have to restructure whole application with dozens and hundreds of session beans.
Thanks a lot!

OK. I just want to make sure that there are no problems with the deployment descriptors.
To pin point the problem do the following in JDeveloper:
1. Create a simple EJB 3.0 session bean
2. On that session bean create a Sample Java Client.
3. Run the Session Bean
4. Run the Client
5. If both are running fine, compare the deployment descriptors from the sample and your real application.
--olaf

JSPX Migration from Tomcat to OC4J

We are migrating the web tier of our application from Tomcat 5 to OC4J 10.1.3.0.0. We are having a problem in our jspx files. The code below works in Tomcat but not in oc4j.
<gc3:viewFieldText name="invoice/invoice_xid" valueIndicator="invoice/indicator">
<jsp:attribute name="label">
<x:when select="$mainNode/invoice_type = 'B'">field.invoice/bill_xid</x:when>
<x:otherwise>field.invoice/invoice_xid</x:otherwise>
</x:choose>
</jsp:attribute>
</gc3:viewFieldText>
We are trying to dynamically set the label attribute of one of our custom tags using <jsp:attribute> and the jstl xtags. mainNode is a variable bound in the request and based on the result of the XPath expression, we want to dynamically set the label attribute. The XPath expression is correctly evaluated, however instead of passing the text within the x:when or x:otherwise to our custom tag, it just writes it out to the screen.
If I remove the xtags from the code and hard code the label it works as shown below.
<gc3:viewFieldText name="invoice/invoice_xid" valueIndicator="invoice/indicator">
<jsp:attribute name="label">
field.invoice/bill_xid
</jsp:attribute>
</gc3:viewFieldText>
Let me know if you need any further information.

Chad,
10.1.3.0.0 was buggy.
Try 10.1.3.1.0 or the latest: 10.1.3.2.0
(Just a suggestion.)
Good Luck,
Avi.

JAX-RPC on OC4J (Migrating from TOMCAT to OC4J) Problems

I am attempting to compile and build a simple web service
to using wsdeploy from Sun's JWSDP1.2. It works fine on Tomcat but when I try to deploy it to OC4J. I get the following error:
7/23/03 11:58 AM Internal error in HttpServer
java.lang.ClassCastException: com.evermind.naming.ContextClassLoader
     at com.sun.xml.rpc.server.http.JAXRPCContextListener.contextInitialized(JAXRPCContextListener.java:52)
     at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:583)
     at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:374)
     at com.evermind.server.Application.getHttpApplication(Application.java:657)
     at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:663)
     at com.evermind.server.http.HttpSite.getApplication(HttpSite.java:387)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:378)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:243)
     at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)7/23/03 3:53 PM 9.0.2.0.0
I've come to notice that Oracle's WebServicesAssembler doesn't use com.sun.xml.rpc.server.http.JAXRPCContextListener but instead uses something else. When the JAXRPCContextListener starts to initialize it trys to perform the following operation:
classLoader = (URLClassLoader)Thread.currentThread().getContextClassLoader();
Is there any way to remedy this?? Or is there anything I can do to get this to work??
Thanks
Mike

Have you deployed JAX-RPC onto OC4J? We currently do not have JAX-RPC available on OC4J.
Mike.

Migrating from Tomcat to WebSphere

I have a JSF application which works correctly under tomcat web-server. But when I tried to migrate this application to IBM WebSphere I was suprised to dicover that it didn't work at all. I found a lot of differences between how WS and Tomcat interprete faces-config. Moreover WS parser doesn't understand tags like "<tagname \>".
Maybe somebody has already faced with such a problem and can tell me something how to solve it.

WebSphere version is 6.

[OIM] Migrate from WebSphere to WebLogic

Hi people,
I would like to migrate our OIM implementation from WAS to WLS, is that possible? Is there some documentatition to achieve this goal?

If you only transfer configuration the chances of something breaking are minimal.
On the other hand if you need transactions as well things get a bit more complex.
In either case a full regression test is always a must as there always is the risk that a supporting jar or even dll (if one windows) in the app server is of slightly different version which introduces a change of behavior.
Best regards
/Martin

Migrating from Glassfish to Weblogic

Hello,
We have a java project (EJB 3) that we deploy in glassfish. With new changes to company's infrastructure, glassfish is not available and I need to deploy the EAR files to Weblogic 10.3.0. We build the ear file using maven and get any required dependencies, however as expected, I have started running into issues. I have a stacktrace below here but does anyone have a suggestion for me as to how to get this done?
Unable to access the selected application.
Exception in AppMerge flows' progression
Exception in AppMerge flows' progression
[J2EE:160161]Error while parsing the Application descriptors for mi-connector.ear: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND problem: cvc-attribute.4: The value '6' does not equal the fixed value '5' of attribute 'version':<null> at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234) at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221) at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146) at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306) at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788) at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409) at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759) at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768) at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311) at weblogic.application.compiler.CompilerCtx.setApplicationDescriptor(CompilerCtx.java:138) at weblogic.application.compiler.AppcUtils.setDDs(AppcUtils.java:142) at weblogic.application.compiler.flow.DescriptorParsingFlow.compile(DescriptorParsingFlow.java:57) at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36) at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96) at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:49) at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:94) at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:47) at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36) at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96) at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157) at weblogic.utils.compiler.Tool.run(Tool.java:158) at weblogic.utils.compiler.Tool.run(Tool.java:115) at weblogic.application.compiler.AppMerge.merge(AppMerge.java:169) at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:88) at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:63) at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:181) at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createLazyDeployableObject(WebLogicDeployableObjectFactoryImpl.java:156) at weblogic.deploy.api.tools.SessionHelper.inspect(SessionHelper.java:661) at com.bea.console.actions.app.install.Flow$2.execute(Flow.java:463) at com.bea.console.utils.DeploymentUtils.runDeploymentAction(DeploymentUtils.java:4625) at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:461) 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.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64) at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:255) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106) at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225) at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199) at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:54) at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130) 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:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) .

You are trying to deploy a Java EE 6 application to a Java EE 5 Application Server.
Weblogic is still not a certified Java EE 6 Application Server.
http://en.wikipedia.org/wiki/Java_Platform,_Enterprise_Edition#Java_EE_6_certified
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question.

Application Migration from JBOSS to Weblogic Server

Hi,
I am facing lots of issues while deploying an .ear file on Weblogic server. In the JBOSS server the application is working properly but whenever I am trying to deploy it on Weblogic server its throwing me an error stating :
"ERROR: No j2ee modules detected in EAR archive. Deployment aborted. "
I tried to convert the things to .war file and tried to deploy the application, the application got deployed but its throwing 'exception'.
Please revert me back with some solution.
Thanks
Trishul

Is this forum about Jboss?
Is it about Weblogic?
If so, why do you put a question about a non-Oracle non-database product in a forum on Oracle Database?
Sybrand Bakker
Senior Oracle DBA

Migrating from Tomcat to OC4J

We are currently just using Tomcat for both HTTP and Servlet engine duties on our web server. The HTTP side is quite slow so
we have just purchased the 9iAS with OC4J (v.1.0.2.2). The documentation say OC4J is "100%" Tomcat compatible. That's great but current setup uses HTML to build 3 frames then puts an HTML menu in one which has the javascript commands to run java classes via a servlet. We have our index.html in the top level folder, then the menu files in a sub-folder (menu), graphics in another (misc), javascript in another (lib), then the class files are below that in :
/Web-inf/classes/html...
/Web-inf/classes/database
/Web-inf/classes/objecttypes
/Web-inf/classes/Utils
Anyone set up this style of application? as the examples only show running servlets directly.

Sure. Are you having a specific problem, or just wondering if it will work? YOu class files are fine in those subdirectories so long as they correspond correctly with the package names. As far as referencing a servlet whose class is in a package, you do it in OC4J just like in Tomcat - by defining the servlet name and class and mappings in the web.xml file. If you can build a war using Ant and deploy that war to Tomcat, you will find that that war will deploy very nicely to Orion. The only additional work is to add any custom application setup to the Orion configuration files (server.xml, default-web-site.xml, etc) similar to what you would do in the Tomcat server.xml and worker.xml files.
John H.

Migrate from Tomcat to OC4J

Hi! Everyone,
I developed a Servlet/JSP application on tomcat, now I am going to deploy it to OC4J. In OC4J, directly under default-web-apps, I created a directory called misc, and put my servlets (in default-web-apps/misc/WEB-INF/classes), jsp (in default-web-apps/misc/jsp), beans (in default-web-apps/misc/WEB-INF/classes/beans) there (no EJB). The OC4J server can run jsp correctly, but it can not locate servlets. It can only locate servlets under default-web-apps/WEB-INF/classes directory.
It means it is not scalable if I put my servlets directly in default-web-apps/WEB-INF/classes, because if I deploy another project, which has a servlet, I also need to put it in the same directory.
All in all, OC4J can locate the servlet by "http://127.0.0.1:port/servlet/myservlet", but if I put the servlet in misc/WEB-INF/classes directory, it can not locate the servlet by "http://127.0.0.1:port/misc/servlet/myservlet".
In tomcat, it is good because every time I created a new project, I just create a new directory "misc" parallel to "examples", and I can access that project by "http://127.0.0.1:port/misc/servlet/myservlet". By doing this way, different projects are in different directory. But in OC4J, different projects' servlet has to be in the same directory (I know I can create a directory under WEB-INF/classes called misc, and then call my servlet by "http://127.0.0.1:port/servlet/misc.myservlet, but this is not what I want).
Is there a way to let OC4J to deploy projects like tomcat? The documentation said OC4J is 100% compatible with tomcat, but I think it is not.
Thanks a lot if you can provide help.
Jingzhi

Hi! Everyone,
I developed a Servlet/JSP application on tomcat, now I am going to deploy it to OC4J. In OC4J, directly under default-web-apps, I created a directory called misc, and put my servlets (in default-web-apps/misc/WEB-INF/classes), jsp (in default-web-apps/misc/jsp), beans (in default-web-apps/misc/WEB-INF/classes/beans) there (no EJB). The OC4J server can run jsp correctly, but it can not locate servlets. It can only locate servlets under default-web-apps/WEB-INF/classes directory.
It means it is not scalable if I put my servlets directly in default-web-apps/WEB-INF/classes, because if I deploy another project, which has a servlet, I also need to put it in the same directory.
All in all, OC4J can locate the servlet by "http://127.0.0.1:port/servlet/myservlet", but if I put the servlet in misc/WEB-INF/classes directory, it can not locate the servlet by "http://127.0.0.1:port/misc/servlet/myservlet".
In tomcat, it is good because every time I created a new project, I just create a new directory "misc" parallel to "examples", and I can access that project by "http://127.0.0.1:port/misc/servlet/myservlet". By doing this way, different projects are in different directory. But in OC4J, different projects' servlet has to be in the same directory (I know I can create a directory under WEB-INF/classes called misc, and then call my servlet by "http://127.0.0.1:port/servlet/misc.myservlet, but this is not what I want).
Is there a way to let OC4J to deploy projects like tomcat? The documentation said OC4J is 100% compatible with tomcat, but I think it is not.
Thanks a lot if you can provide help.
Jingzhi

Migration from OAS 10g to Weblogic 10.3

Hello,
I migrate large app from OAS 10g to Weblogic 10.3.
1.
The main part of the job was to prepare descriptors for Weblogic. Unfortunatelly I don't find any tool that could do the job:( There are some problems with descriptors namespaces. This schema and namespaces given in 10.3 docs are not working (not available):
http://edocs.bea.com/wls/docs103/ejb/DD_defs_reference.html
So I use the one from 10 release in weblogic-ejb-jar.xml:
weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
and form 9 release in weblogic-cmp-rdbms-jar.xml:
<weblogic-rdbms-jar xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-rdbms20-persistence.xsd">
There are also some bugs in docs about ejb relations.
After fixing some schema compliance exc this step success.
2. Next the EJBComplianceChecker - its much more restrictive than OAS verification. So updates in ejb interfaces are necessary. It is not a problem with small app but when there ale a lot of code/branches to migrate it's become a problem. I have been looking for some switch that could help with this but with no result/
EJBComplianceChecker - Spec veryfication level
3. Now after EJB compliance checker done its job with success I have an exception that I do not understand:
An error occurred during activation of changes, please see the log for details.
Exception
preparing module: EJBModule(corpo_ejb.jar)
Unable to deploy EJB: corpo_ejb.jar from corpo_ejb.jar:
There are 1 nested errors:
java.io.IOException: JDT compilation error! at
weblogic.ejb.container.ejbc.CompilerForJDT.compile(CompilerForJDT.java:66)
at
weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:357)
at
JDT compilation error!
Could you please give me some point where the problem could be? I don't have any idea where to start looking for..
What are your experiences with migrations from OAS to Weblogic 10?
Thanks in advance!
Edited by: Stoigniew Sztank on Oct 10, 2008 4:00 AM
Edited by: Stoigniew Sztank on Oct 10, 2008 4:01 AM
Edited by: Stoigniew Sztank on Oct 10, 2008 4:02 AM
Edited by: Stoigniew Sztank on Oct 10, 2008 4:04 AM
Edited by: Stoigniew Sztank on Oct 10, 2008 8:05 AM

Hi Stoigniew Sztank,
I am working on migrating Enterpirse application developed using Struts, Ejb2.0, JMS. Its been deployed on OAS 10G and Websphere, but I need to deploy the application on Weblogic 10.3. It seems you have migrated a J2ee application from OAS 10G to Weblogic 10.3. Please can you list me the steps that you followed to migrate the application.
As per my understanding follwing things needsto be taken care of:-
1) Weblogic Descriptor files:
1.1 Weblogic.xml:- we added security roles and ejb-reference-description for the ejbs.
1.2 Weblogic-ejb-jar.xml for all the ejbs used in the application.
1.3 Weblogic-application.xml
1.4 Resource Adapter
2) JMS queue set up
3) JDBC set up
It would be a great help if you can let me know what are the steps to migrate the application.
Thanks and Regards
Deepak Dani

Migrating WebServices app from Tomcat to Glassfish...

Hello!
I've a WebService app. which now runs on Tomcat 5.5.23 and was written using JAX-WS. I've install Sun Java System App. Server 9.0 and I intend to migrate our app. here.
The application is delivered as a war file which I've already deployed in glassfish using admin GUI of asadmin. I can see our app. at WebApplications section but I can't see it under WebServices section, although it seems at a first view that the application works and respond to client's request.
I'd like to ask you if I need to use a special tool for migrating our aplication or what I did is enough and there is no need for other changes.
Thank you very much
With best regards,
Sorin

If I understand correctly, you are trying to load a few properties files on WLS that is specific to an application that you are migrating from tomcat to WLS. If that is the case, then as per my understanding we have the following options:
a. Add all the properties in a jar file and add the same to the classpath or place the same in the lib directory of the server which can be picked at the server start-up.
b. Place the properties file in the domain home which should help.
Refer: loading a new properties file without restarting the managed server
c. Else place the properties files in the web-inf of the application, that should help.

Calling an ejb from glassfish to weblogic server

I'd like to be able to call a stateless session bean from a glassfishV3 server that is residing on weblogic 9.2.3. (Ejb spec 2.1 NOT 3.0 please)
I've done this successfully from Tomcat to weblogic, but there are a few hiccups when trying this on glassfish.
Basically what I've attempted is this:
1.) I add these jvm properties to the glassfish startup:
-Dorg.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
-Djavax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
-Djavax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
2.) Copy weblogic.jar, tools.jar, and webservices.jar from the weblogic/server/lib directory to the glassfish lib/ext directory
...glassfish won't start then because of the weblogic.jar...
3.) Move the weblogic.jar to the WEB-INF/lib directory of my war in glassfish.
Now I try it and get:
(I'm skipping some of the stacktrace at the start)
.....java.lang.IllegalAccessError: tried to access method weblogic.kernel.KernelStatus.initialized()V from class weblogic.kernel.Kernel at weblogic.kernel.Kernel.ensureInitialized......
I'm guessing that this has to do with the "weblogic kernel" not being initialized. So now I'm stuck.
Am I going down the wrong path?
I've also tried these other proposed solutions:
1.) Changing the connection properties of the InitialContext to use these properties:
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://localhost:7001");
env.put(Context.SECURITY_PRINCIPAL, "weblogic");
env.put(Context.SECURITY_CREDENTIALS, "weblogic");
2.) Using RMI over IIOP instead of T3.
None of these with any luck.
If anyone has done this successfully I'd appreciate some insight.
Regards,
Eric

I'd like to be able to call a stateless session bean from a glassfishV3 server that is residing on weblogic 9.2.3. (Ejb spec 2.1 NOT 3.0 please)
I've done this successfully from Tomcat to weblogic, but there are a few hiccups when trying this on glassfish.
Basically what I've attempted is this:
1.) I add these jvm properties to the glassfish startup:
-Dorg.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
-Djavax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
-Djavax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
2.) Copy weblogic.jar, tools.jar, and webservices.jar from the weblogic/server/lib directory to the glassfish lib/ext directory
...glassfish won't start then because of the weblogic.jar...
3.) Move the weblogic.jar to the WEB-INF/lib directory of my war in glassfish.
Now I try it and get:
(I'm skipping some of the stacktrace at the start)
.....java.lang.IllegalAccessError: tried to access method weblogic.kernel.KernelStatus.initialized()V from class weblogic.kernel.Kernel at weblogic.kernel.Kernel.ensureInitialized......
I'm guessing that this has to do with the "weblogic kernel" not being initialized. So now I'm stuck.
Am I going down the wrong path?
I've also tried these other proposed solutions:
1.) Changing the connection properties of the InitialContext to use these properties:
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://localhost:7001");
env.put(Context.SECURITY_PRINCIPAL, "weblogic");
env.put(Context.SECURITY_CREDENTIALS, "weblogic");
2.) Using RMI over IIOP instead of T3.
None of these with any luck.
If anyone has done this successfully I'd appreciate some insight.
Regards,
Eric

Migration from tomcat to weblogic 10.3.2

Similar Messages

Maybe you are looking for