PageFlow Bea 9 and BIRT

hello!
I'm trying to integrate in one project my old bea8 sp5 project updated with the workshop to bea 9.2 AND reports in eclipse BIRT.
i have build a war app with reports in this new bea 9.2, and it works fine, but it needs the
<wls:container-descriptor>
<wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
</wls:container-descriptor>
OR
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
modification into weblogic.xml, to work properly.
in the other hand, i have my old app made in workshop 8 sp5, imported in the new enviroment. It works just fine too.
but, when i try to join both, i need to add the
container-descriptor tag in the updated application (where i am making the mixture) to get access to reports pages, then i have an error:
Module named 'prototipo' failed to deploy.
weblogic.application.ModuleException:
where prototipo is the name of the old app, updated to w9.
the complete stack trace in log file is
####<19-jul-2006 16H27' GMT-03:00> <Error> <Deployer> <pc_vates91> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1153337254341> <BEA-149265> <Failure occured in the execution of deployment request with ID '1153337225730' for task '0'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
 at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:295)
 at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
 at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
 at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl
 at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:531)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
 at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:308)
 at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
 at org.apache.beehive.netui.util.logging.Logger.getInstance(Logger.java:44)
 at org.apache.beehive.netui.pageflow.PageFlowContextListener.<clinit>(PageFlowContextListener.java:36)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at java.lang.Class.newInstance0(Class.java:350)
 at java.lang.Class.newInstance(Class.java:303)
 at weblogic.servlet.internal.EventsManager.registerEventListener(EventsManager.java:275)
 at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:257)
 at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1573)
 at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1037)
 at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:433)
 at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:408)
 at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:552)
 at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:287)
 at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
 at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
 at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<19-jul-2006 16H27' GMT-03:00> <Warning> <Deployer> <pc_vates91> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1153337254856> <BEA-149004> <Failures were detected while initiating distribute task for application 'prototipo'.>
####<19-jul-2006 16H27' GMT-03:00> <Warning> <Deployer> <pc_vates91> <AdminServer> <[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1153337254872> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
 at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:295)
 at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
 at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
 at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl
 at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:531)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
 at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:308)
 at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:370)
 at org.apache.beehive.netui.util.logging.Logger.getInstance(Logger.java:44)
 at org.apache.beehive.netui.pageflow.PageFlowContextListener.<clinit>(PageFlowContextListener.java:36)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
 at java.lang.Class.newInstance0(Class.java:350)
 at java.lang.Class.newInstance(Class.java:303)
 at weblogic.servlet.internal.EventsManager.registerEventListener(EventsManager.java:275)
 at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:257)
 at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1573)
 at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1037)
 at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:433)
 at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:408)
 at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:552)
 at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:287)
 at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
 at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
 at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
data that could help
i tried change weblogic.xml with "wls:" form, and without it. i don't understand the difference... but in both cases nothing changed.
i search for LogFactoryImpl class in jar files and i had find one, so i delete it from webcontent/web-inf/lib, but the problem stills goes on.
if all the code and jar files are together but prefer-web-inf-classes tag is not used, i have no deployment error, but i can't view reports, of course.
the application has pageflows, ejb's and controls, from bea products. and when i imported it, i choose use beehive in the options.
BIRT version is 2.1.0
JDK version jdk150_04
weblogic.xml:
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app xmlns:wls="http://www.bea.com/ns/weblogic/90">
 <wls:container-descriptor>
 <wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
 </wls:container-descriptor>
 <context-root>procesoIngreso</context-root>
 <wls:library-ref>
 <wls:library-name>jstl</wls:library-name>
 <wls:specification-version>1.1</wls:specification-version>
 <wls:implementation-version>1.1.2</wls:implementation-version>
 </wls:library-ref>
 <wls:library-ref>
 <wls:library-name>beehive-controls-1.0-war</wls:library-name>
 <wls:specification-version>1.0</wls:specification-version>
 <wls:implementation-version>1.0</wls:implementation-version>
 </wls:library-ref>
 <wls:library-ref>
 <wls:library-name>weblogic-controls-1.0-war</wls:library-name>
 <wls:specification-version>1.0</wls:specification-version>
 <wls:implementation-version>1.0</wls:implementation-version>
 </wls:library-ref>
 <wls:library-ref>
 <wls:library-name>struts-1.1</wls:library-name>
 <wls:specification-version>1.1</wls:specification-version>
 <wls:implementation-version>1.0</wls:implementation-version>
 </wls:library-ref>
 <wls:library-ref>
 <wls:library-name>struts-1.2</wls:library-name>
 <wls:specification-version>1.2</wls:specification-version>
 <wls:implementation-version>1.0</wls:implementation-version>
 </wls:library-ref>
 <wls:library-ref>
 <wls:library-name>beehive-netui-resources-1.0</wls:library-name>
 <wls:specification-version>1.0</wls:specification-version>
 <wls:implementation-version>1.0</wls:implementation-version>
 </wls:library-ref>
 <wls:library-ref>
 <wls:library-name>beehive-netui-1.0</wls:library-name>
 <wls:specification-version>1.0</wls:specification-version>
 <wls:implementation-version>1.0</wls:implementation-version>
 </wls:library-ref>
</wls:weblogic-web-app>
The original weblogic.xml (when workshop imports the old project) was
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns="http://www.bea.com/ns/weblogic/90"
 xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
 <jsp-descriptor>
 <debug>true</debug>
 </jsp-descriptor>
 <url-match-map>
 weblogic.servlet.utils.SimpleApacheURLMatchMap
 </url-match-map>
 <context-root>procesoIngreso</context-root>
 
 <library-ref>
 <library-name>struts-1.1</library-name>
 <specification-version>1.1</specification-version>
 <implementation-version>1.0</implementation-version>
 </library-ref>
 <library-ref>
 <library-name>beehive-netui-resources-1.0</library-name>
 <specification-version>1.0</specification-version>
 <implementation-version>1.0</implementation-version>
 </library-ref>
 <library-ref>
 <library-name>beehive-netui-1.0</library-name>
 <specification-version>1.0</specification-version>
 <implementation-version>1.0</implementation-version>
 </library-ref>
 <library-ref>
 <library-name>jstl</library-name>
 <specification-version>1.1</specification-version>
 <implementation-version>1.1.2</implementation-version>
 </library-ref>
</weblogic-web-app>
procesoIngreso is the name of war module of the j2ee app.
web.xml file is:
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>Workshop Application</display-name>
<description/>
<servlet>
<description/>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.beehive.netui.pageflow.PageFlowActionServlet</servlet-class>
<init-param>
<description/>
<param-name>config</param-name>
<param-value>/_pageflow/struts-config.xml</param-value>
</init-param>
<init-param>
<description/>
<param-name>config/-global</param-name>
<param-value>/_pageflow/struts-config--global.xml</param-value>
</init-param>
<init-param>
<description/>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<description/>
<param-name>detail</param-name>
<param-value>2</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>default.html</welcome-file>
<welcome-file>default.htm</welcome-file>
<welcome-file>default.jsp</welcome-file>
</welcome-file-list>
<error-page>
<error-code>500</error-code>
<location>/error.jsp</location>
</error-page>
<jsp-config>
<taglib>
<taglib-uri>netui-tags-html.tld</taglib-uri>
<taglib-location>/WEB-INF/netui-tags-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>netui-tags-databinding.tld</taglib-uri>
<taglib-location>/WEB-INF/netui-tags-databinding.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>netui-tags-template.tld</taglib-uri>
<taglib-location>/WEB-INF/netui-tags-template.tld</taglib-location>
</taglib>
</jsp-config>
<filter>
<filter-name>PageFlowJspFilter</filter-name>
<filter-class>org.apache.beehive.netui.pageflow.PageFlowJspFilter</filter-class>
</filter>
<filter>
<filter-name>PageFlowForbiddenFilter</filter-name>
<filter-class>org.apache.beehive.netui.pageflow.PageFlowForbiddenFilter</filter-class>
<init-param>
<param-name>response-code</param-name>
<param-value>404</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>PageFlowJspFilter</filter-name>
<url-pattern>*.jsp</url-pattern>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowJspFilter</filter-name>
<url-pattern>*.jspx</url-pattern>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowForbiddenFilter</filter-name>
<url-pattern>*.java</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowForbiddenFilter</filter-name>
<url-pattern>*.jsfb</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowForbiddenFilter</filter-name>
<url-pattern>*.jpfs</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>PageFlowForbiddenFilter</filter-name>
<url-pattern>/_pageflow/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
<listener>
<listener-class>org.apache.beehive.netui.pageflow.PageFlowContextListener</listener-class>
</listener>
<listener>
<listener-class>org.apache.beehive.netui.pageflow.HttpSessionMutexListener</listener-class>
</listener>
<servlet>
<servlet-name>XmlHttpRequestServlet</servlet-name>
<servlet-class>org.apache.beehive.netui.pageflow.xmlhttprequest.XmlHttpRequestServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.jpf</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>XmlHttpRequestServlet</servlet-name>
<url-pattern>*.xhr</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>XmlHttpRequestServlet</servlet-name>
<url-pattern>*.render</url-pattern>
</servlet-mapping>
<-- MENU CONFIGURATION -->
<context-param>
 <param-name>menuConfigLocation</param-name>
 <param-value>/WEB-INF/menu-config.xml</param-value>
 </context-param>
 <listener>
 <listener-class>net.sf.navigator.menu.MenuContextListener</listener-class>
 </listener>
<-- END MENU CONFIGURATION -->
<-- BIRT CONFIGURATION -->
<context-param>
 <param-name>BIRT_VIEWER_LOCALE</param-name>
 <param-value>en-US</param-value>
 </context-param>
 <context-param>
 <param-name>BIRT_VIEWER_REPORT_ROOT</param-name>
 <param-value></param-value>
 </context-param>
 
 <context-param>
 <param-name>BIRT_VIEWER_IMAGE_DIR</param-name>
 <param-value></param-value>
 </context-param>
 
 <context-param>
 <param-name>BIRT_VIEWER_LOG_DIR</param-name>
 <param-value></param-value>
 </context-param>
 <servlet>
 <servlet-name>ViewerServlet</servlet-name>
 <servlet-class>org.eclipse.birt.report.viewer.servlets.ViewerServlet</servlet-class>
 </servlet>
 <servlet-mapping>
 <servlet-name>ViewerServlet</servlet-name>
 <url-pattern>/frameset</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
 <servlet-name>ViewerServlet</servlet-name>
 <url-pattern>/run</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
 <servlet-name>ViewerServlet</servlet-name>
 <url-pattern>/navigation</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
 <servlet-name>ViewerServlet</servlet-name>
 <url-pattern>/toolbar</url-pattern>
 </servlet-mapping>
<-- END BIRT CONFIGURATION -->
</web-app>
that's all i think that i cant give you, i guess...
(all xml comments have not the "!" because in preview, those lines are not shown, for example <-- END BIRT CONFIGURATION -->)
can you help me please with this issue?
thank in advance.
best regards
julio

julio,
Hey I'm having the exact same problem when I add
<wls:container-descriptor>
<wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
</wls:container-descriptor>
to my weblogic.xml??? Did you ever get a resolution for this problem if so can you help me out.
Thanks,
Greg

Similar Messages

Integration Vitria BusinessWare with BEA and JReport

Mi nombre es Sabino Mariano, estoy en Accenture M?xico, en un proyecto para Pemex, el cual consiste en la integraci?n de Vitria BusinessWare con BEA WebLogic.
Requiero informaci?n con respecto a la forma de conjuntar estas dos aplicaciones para publicar informaci?n en BEA, asi como la forma de utilizar JReport para los Reportes.
Muchas Gracias

I have worked some with BEA's WebLogic Server and Workshop and have been able to deploy UML modeled services designed with Telelogic Tau successfully through Workshop (using Telelogic Tau's Eclipse integration). As far as I know, Telelogic has a BPM workflow from a high level through System Architect to Tau where you can further refine busines models into UML models and then deploy your SOA through Workshop.

BEA and Web Services problem

Hi
I'm new to java and trying to educate myself in this field and therefor I have this question.
I'm trying to develope a web service to bea. I successfully managed to deploy bea's web service example called Trader(EJB version). Available at webservices.zip that I downloaded from this site(src\examples\webservices\complex\statelessSession).
But now I'm facing a problem that I can't figure out how to read data from HttpRequest- is this possible at all with EJB? For example I would like to get username from header? Or usually X509 certificate is added to request and how can i deal with it?
Currently I'm able to read only data specified in the procedure defined in the interface. For example:
public String doIt(String val,String val2)
Any help would be appreciated :)
Thanks in advance :)
Edited by justcraizy at 04/03/2007 7:34 AM

You should be able to get the username from the context?
private SessionContext sessionCtx = null;
public void setSessionContext(SessionContext sctx) {
this.sessionCtx = sctx;
public void someMethod() {
String username = sessionCtx.getCallerPrincipal().getName();
-Jesus

JNLP and BIRT

Hello
I have got SWT application which uses BIRT. I am using JNLP to distribute it. It works fine when I set engine confing BIRT home as existing ReportEngine folder on harddrive, but I want to download ReportEngine as jars using JNLP. I can't find what should my BirtHome point to. Could anyone tell me how to do that?

Hi marv_
I don't know BIRD but maybe this helps:
your Application is downloaded and started by javaws.
Since you don't know which path is has I'd suggest to use relative paths (what I'd recommend also in any in any other case)
If you really need the absolute path in a configuration you could determine the path* your program is working on and then write this path to the configuration.
* You can do that in this way
File file = new File(".");
System.out.println(file.getAbsolutePath());
May be there is a better way but I don't know another.

PageFlow scope and session scoped form beans

Howdy,
Is there any more documentation on how the scope of form beans is supposed
to work in SP2? The only bit I find is a small section within the
jpf:forward and jpf:action annotation doc files. This doesn't really help
very much. If you could point to examples or more information explaining
how this can be done, I would really appreciate it!
Thanks,
Wendy

Are you sending the user back and forth between HTTP and HTTPS requests? If a session is established via HTTPS the cookie will be secure and will not be accessible to HTTP requests to the same server.

Bea and nvarchar2 data type in oracle

Does weblogic server supports nvarchar2 data type in Oracle?..
I use CMP with java data type String mapped to nvarchar2 data type to oracle.when
i try to create a bean it throws "java.sql.SQLException: ORA-12704: character set
mismatch". Is there any configuration in the server to set the character set?..
can anyone help me on this?...

Does weblogic server supports nvarchar2 data type in Oracle?..
I use CMP with java data type String mapped to nvarchar2 data type to oracle.when
i try to create a bean it throws "java.sql.SQLException: ORA-12704: character set
mismatch". Is there any configuration in the server to set the character set?..
can anyone help me on this?...

BEA and Borland to Offer Borland JBuilder, BEA Weblogic Edition

It's coming lads, the N.1 IDE targeted for N.1 App Server. See all details
at :
http://www.theserverside.com/home/thread.jsp?thread_id=14979
[Guillaume Lasnier.vcf]

Hi,
Instead of Ping,Try telnet command to specific DB port from Weblogic Server to DB server
You should get
$ telnet ipaddress port
Trying ipaddress...
Connected to ipaddress.
Escape character is '^]'.
Regards
Fabian

Porting a netui pageflow project from BEA Workshop into JDeveloper 11g

Hi.
Now that BEA and Oracle has merged and JDeveloper ships with Weblogic server instead of ye olde oc4j, I thought that netui pageflow projects developed in BEA Workshop/Workspace studio would be a breeze to port to JDev. This does not seem to be the case. I've googled til my eyes got sore, without any luck. Correct me if I'm wrong, but the Beehive Netui package was once developed by BEA, then given to Apache, then taken back into BEA's control. When I read that JDeveloper should be the IDE for BEA/Oracle from now on, I thought that this would mean that it would also be compatible with BEA projects.
If it is at all possible, how do I go about porting my Hibernate/Spring/Beehive NetUi PageFlow workshop project to run under JDeveloper/Weblogic?
I've found this article: http://www.oracle.com/technology/products/jdev/howtos/1013/w4wljdev/workshopandjdev.html?rssid=rss_otn_news
But still no luck enabling Beehive Netui support for my pageflows in JDeveloper.
Edited by: Øystein_Amundsen on Oct 31, 2008 12:57 PM

There is no current plan to enable Beehive (e.g. NetUI) specific features in JDeveloper.
The beehive development environment is still inside WebLogic Workshop and you can get the latest version here:
http://www.oracle.com/technology/products/workshop/index.html
It might be possible to do development with Beehive in JDeveloper by adding the beehive jar files into your project properties->libraries node.
That said - I would recommend that you look into Oracle ADF as an alternative framework for your development - it has a lot of similar concepts to Beehive but it is more up-to-date and has better features in many areas.
Read more about it here:
http://www.oracle.com/technology/products/jdev/11/collateral/beehivetoadf.pdf

BEA / Wily: Financial Webinar - Achieving Availability, Performance and Control of Java Applications in Financial Services

Event Date: October 1, 2002 at 11:00 AM Pacific (US), 02:00 PM Eastern (US)
To register: http://regsvc.placeware.com/?wily-bea1001
Title: Achieving Availability, Performance and Control of Java Applications
in Financial Services
Abstract:
In today's competitive environment, financial institutions must focus on
three key business goals:
a.. Creating a customer-centric enterprise to maximize value to customers
and increase share of wallet
b.. Improving transactional efficiency for rapid delivery of the right
products, services and information to customers and to employees
c.. Accelerating the decision making process to mitigate risk and improve
returns.
BEA and Wily Technology have helped a number of financial services firms
meet these objectives by delivering high-performance business solutions that
meet rigorous demands for performance, reliability and scalability.
On October 1, 2002, Wily Technology and BEA will present a joint Web seminar
titled "Achieving Availability, Performance and Control of Java Applications
in Financial Services" with Eric Gudgion, Principal System Architect,
Technical Solutions Group at BEA and Chris Farrell, Director of Technical
Marketing at Wily. This Webinar will showcase the many advantages that the
WebLogic® Enterprise PlatformT and Wily's Introscope® offer financial
services firms.
Attendees will learn how WebLogic Server, BEA's unified, simplified and
extensible solution, provides a robust platform for the development and
deployment of enterprise Java applications. Some examples of what financial
institutions can achieve with BEA include Multi-channel Services Delivery,
Straight-Through Processing, Wealth Management and Cash Management.
Wily Technology will highlight Introscope's ability to manage financial
services Java applications by pinpointing component-level performance issues
in real-time, whether in the application, application server or
Java-connected back-end systems. Wily's suite of Java application management
solutions offers a comprehensive platform for achieving 24x7 application
availability, enhanced performance and better control of IT resources.

First of all you should check out which products are supported on 64bit :- http://www.oracle.com/technology/products/bi/hyperion-supported-platforms.html
If you are planning on using windows 64bit EAS then you will have to manually deploy the web application, it cannot be automatically deployed.
Cheers
John
http://john-goodwin.blogspot.com/

ADF Taskflows with EJB and pageflow scope

Hi,
I am trying to create a simple registration page which is very simillar to FOD customer registration using EJBs instead of ADF BC.
I can achieve the registration in one page but I wanted to try this using a wizard based process using ADF taskflows.
I created a bounded taskflow with 3 pages. page1 is employee details, page2 is job details, page 3 is the summary page. I have JPA entities for Employee and Jobs and an EJB3 session Facade. I have used the Employees default constructor to create the UI bindings from the constructor section of the data controls. This creates an EmployeesIterator which I use it for bindings on all the three pages.
My question is can I use this Iterator binding in pageflow scope? If yes How do I do this?
The other way is to use a managed bean in pageflow scope and have UI bindings to the variables in managed bean. This option will work but I will not be utilising any of the features of ADF bindings.
Can anyone please suggest which is the better option.
Thanks
Venkatesh

Hi,
pageDef files can be shared, but their instances aren't. The caching is on the data control side, which means that instead of using a constructor you would break up the input form into method calls like
createPerson(String, fn, String ln, String address)
createInterest(String hobby1, String hobby2);
dagging and dropping the method calls should the reate an input form. Submitting the forms allows you to build a new person object on the session facade which at the end is committed. This way the ADF binding works across pages, operating on a single new object
Frank
Ps.: Note that I did not run this example for a test

LDAP Users and Groups

Hi,

I have configured an LDAP Authenticator for an external LDAP directory in the security realm of the samples portal. User Management is working, but when I try to access the Group Management for the LDAP Authenticator I get the following error:

com.bea.p13n.usermgmt.hierarchy.TreeNotBuiltException: State: UNINITIALIZED. Tree is uninitialized. Add provider GAAD to list of providers to build. Tree is uninitialized. Add provider GAAD to list of providers to build.


It seems that this needs to be setup. How do I do this?


Some general notes on LDAP:

I think that in a production environment it is of great value to manage users and groups in a LDAP directory. For instance we have a company directory which contains all users. It seems that users from LDAP can not been added to groups which are in the DB. LDAP also has the advantage of supporting dynamic groups.
As in previous weblogic releases the LDAP authenticator is read only. It would be great if the write functionality could be added as well. Actually managing LDAP users and groups in one place would be a tremendous improvement for us.

Another thing on my wishlist are examples for delegated administration and visitor entitlements. For the sample portal these are empty. But I think it would be nice to have some out of the box examples that show what is possible and help developers and business analysts to understand the concepts and create their own roles.

It would be interesting to read what Bea and other developer think about this.

Kind regards,

Kai


Marcus,
Yes, I am using 9.2 TP.
We are already using LDAP for user management with 8.1.
Now, I try to configure 9.2 as well. I am running 9.2 installations on different machines. When I click on Service Administration in the Admin Portal, I get the following error message for each installation:
java.lang.NullPointerException at com.bea.jsptools.serviceadmin.ads.ToolAdServiceBean.cloneFromAdServiceBean(ToolAdServiceBean.java:190) at com.bea.jsptools.serviceadmin.ServiceAdminTreeBuilder.buildAdContentProviderNodes(ServiceAdminTreeBuilder.java:769) at com.bea.jsptools.serviceadmin.ServiceAdminTreeBuilder.buildAdServiceBranch(ServiceAdminTreeBuilder.java:746) at com.bea.jsptools.serviceadmin.ServiceAdminTreeBuilder.createTreeElement(ServiceAdminTreeBuilder.java:184) at com.bea.jsptools.patterns.tree.TreeService$DefaultTreeServiceImpl.buildWholeTree(TreeService.java:234) at com.bea.jsptools.patterns.tree.TreeService$DefaultTreeServiceImpl.buildWholeTree(TreeService.java:235) at com.bea.jsptools.patterns.tree.TreeService$DefaultTreeServiceImpl.buildTree(TreeService.java:122) at util.tree.TreeController.constructTree(TreeController.java:142) at util.tree.TreeController.buildTree(TreeController.java:422) at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:852) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:782) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:456) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:285) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:48) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:1984) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:90) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2055) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:535) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:821) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:625) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:156) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1178)
java.lang.NullPointerException
java.lang.NullPointerException
at com.bea.jsptools.serviceadmin.ads.ToolAdServiceBean.cloneFromAdServiceBean(ToolAdServiceBean.java:190)
at com.bea.jsptools.serviceadmin.ServiceAdminTreeBuilder.buildAdContentProviderNodes(ServiceAdminTreeBuilder.java:769)
at com.bea.jsptools.serviceadmin.ServiceAdminTreeBuilder.buildAdServiceBranch(ServiceAdminTreeBuilder.java:746)
at com.bea.jsptools.serviceadmin.ServiceAdminTreeBuilder.createTreeElement(ServiceAdminTreeBuilder.java:184)
at com.bea.jsptools.patterns.tree.TreeService$DefaultTreeServiceImpl.buildWholeTree(TreeService.java:234)
at com.bea.jsptools.patterns.tree.TreeService$DefaultTreeServiceImpl.buildWholeTree(TreeService.java:235)
at com.bea.jsptools.patterns.tree.TreeService$DefaultTreeServiceImpl.buildTree(TreeService.java:122)
at util.tree.TreeController.constructTree(TreeController.java:142)
at util.tree.TreeController.buildTree(TreeController.java:422)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:852)
at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:782)
at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:456)
at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:285)
at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:48)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:1984)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:90)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2055)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:535)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:821)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:625)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:156)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1178)

How to open new window without loosing pageFlow context?

I am using 8.1 SP 3.
Here is what I need to do. I have a an anchor link in a jsp that needs to open a new window after executing an action in a page flow. That action forwards to a jsp that needs to be able to access pageFlow variables.
So, I have the following:
<netui:anchor target="_blank" action="timesheetSubmitView">
Everything works fine, that is it opens a new window and keeps the pageFlow content, BUT the new window contains all of the portlets that were on the original page. What I need is a new window that just contains the jsp that my action forwards to.
I looked through the various topics on this forum, but the recomended approach posted by someone to enable redirect does not work because weblogic is loosing the pageFlow context, so jsp errors out due to the fact that variable on a pageFlow is null.

I had the same issue. A couple different things to try -
1. There is a property called redirect in the action. Set it to true.
That did not work for me, so I just used pageFlow variables and put things into the session. Bad way of doing it, but works :)
In the action that loads the first JSP, put things into the session. Then in the timesheetSubmitView action get the stuff from the session.
Write an onDestroy method that deletes the session stuff, when u are done with it.

Error using IO taglib in BEA 8.1

 Hello,
 I am integrating a web application into BEA 8.1 and everything seems to be getting
 worked out except for 1 thing. In one of my JSP pages I use the Jakarta io taglib
 to send a SOAP message. When I try to run this JSP page I get the following error:
 WARNING: ERROR: Caughtjava.io.FileNotFoundException: Response: '500: Internal
 Se
 rver Error' for url: 'http://[the ip]:8080/axis/services/vkb-resourcemgmt'
 java.io.FileNotFoundException: Response: '500: Internal Server Error' for url:
 http://[the ip]:8080/axis/services/vkb-resourcemgmt'
 at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.
 java:394)
 at org.apache.taglibs.io.URLTag.getURLInputStream(URLTag.java:274)
 at org.apache.taglibs.io.URLTag.getURLReader(URLTag.java:259)
 at org.apache.taglibs.io.URLTag.readURL(URLTag.java:327)
 at org.apache.taglibs.io.URLTag.doEndTag(URLTag.java:181)
 at jsp_servlet._jsp.__registerproduct._jspService(registerProduct.jsp:31
 The problem is not with the URL being a bad one but there is some internal conflict
 between BEA and the taglib itself. I don't have problems when my web application
 runs outside of BEA (just in Tomcat).
 Thoughts??
 Thanks - Peter
 6)


 "Peter Len" <[email protected]> wrote in message
 news:[email protected]...
 >
 > Hello,
 >
 > I am integrating a web application into BEA 8.1 and everything seems to be
 getting
 > worked out except for 1 thing. In one of my JSP pages I use the Jakarta
 io taglib
 > to send a SOAP message. When I try to run this JSP page I get the
 following error:
 >
 > WARNING: ERROR: Caughtjava.io.FileNotFoundException: Response: '500:
 Internal
 > Se
 > rver Error' for url: 'http://[the ip]:8080/axis/services/vkb-resourcemgmt'
 > java.io.FileNotFoundException: Response: '500: Internal Server Error' for
 url:
 > '
 > http://[the ip]:8080/axis/services/vkb-resourcemgmt'
 > at
 weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.
 > java:394)
 > at org.apache.taglibs.io.URLTag.getURLInputStream(URLTag.java:274)
 > at org.apache.taglibs.io.URLTag.getURLReader(URLTag.java:259)
 > at org.apache.taglibs.io.URLTag.readURL(URLTag.java:327)
 > at org.apache.taglibs.io.URLTag.doEndTag(URLTag.java:181)
 > at
 jsp_servlet._jsp.__registerproduct._jspService(registerProduct.jsp:31
 > ...................................................
 >
 > The problem is not with the URL being a bad one but there is some internal
 conflict
 > between BEA and the taglib itself. I don't have problems when my web
 application
 > runs outside of BEA (just in Tomcat).
 >
 > Thoughts??
 >
 > Thanks - Peter
 > 6)
 Looks like the URL is returning a 500 Internal Server Error which implies an
 exception on the server side. Does the other URL also reside on WebLogic? If
 so you might want to look at the server log and see if there is something
 going on

Migration from WLI2.0 to WLI2.1 - problems and solutions

We have experienced a number of issues when migrating from WLI2.0 (no service packs)
to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
these issues in case they can be of help to others.
Problems:
1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
What about WLI2.0 with no service packs - I don't see why BEA should have left
out migration from that platform. We decided to follow the process and see what
happened.
2. There is no indication in the documentation of how to run the GUI based migration
tools on Unix, only for Windows so we had to follow the manual route.
3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
to the DB variable setting scripts. It then says to run "migratedb.sh". None of
these files have extensions ".sh" - the files that were installed have no extension.
Obviously that did not stop us running them but the documentation needs correcting.
4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
is a second copy of this file in the bin folder called "setenv". Why are there
2 copies. Also I note that the one in bin is executable and the other is not.
All very confusing!!
5. The migratedb script fails to run because we have not previously run setDomain.
This is not documented.
6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
does not contain the expected folders. That basically means you cannot migrate
such a domain. We carried on with the process using the bpmdomain so that we could
at least migrate our database automatically.
7. Having run setDomain, we tried migratedb again but it failed because we had
not run switchdb. Again, this is not documented. We ran switchdb successfully.
8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
script migratedb then attempts to run a file called "migrate". This is evidence
that no-one has ever tested this script at BEA and we are very disconcerted by
this fact!! We renamed the script and ran migratedb again - this time it ran the
migrate script.
9. This still fails with the following errors (when calling migrateCommonRep)
     -v (No such file or directory)
     null
     java.lang.NullPointerException
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:120)
     at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
     at com.bea.eci.migration.Migrate.main(Migrate.java:73)
     java.lang.NullPointerException
     at com.bea.eci.migration.Migrate.main(Migrate.java:192)
10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
have sqlplus installed on the same machine as WLI and yet again this requirement
is not documented. At this point we gave up trying to run the migrate script as
there seemed to be no route forward.
The process we took to move from WLI2.0 (WLPI only) was as follows:
a. Since we had done no changes to filerealm.properties we simply copied the one
fron bpmdomain into our own domain.
b. We have been unable to run the step to migrate the common repository (see note
9). If this is referring to the XML repository then that should not be a problem
to us as we have not used it.
c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
script on our database. This seems to have successfully updated the database.
Lastly, having completed the migration process we tried to run the server but
it fails. This is because the startWeblogic script fails to call checkdomain properly.
We modified the line to become:
     ". $WLI_HOME/bin/checkdomain"     # the '.' was missing
Does anyone else have any experiences with this that would help us all?
Pete

Pete,
Please post this to the weblogic.integration.interest and weblogic.integration.developer newsgroups?
Pete Edwards wrote:
We have experienced a number of issues when migrating from WLI2.0 (no service packs)
to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
these issues in case they can be of help to others.
Problems:
1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
What about WLI2.0 with no service packs - I don't see why BEA should have left
out migration from that platform. We decided to follow the process and see what
happened.
2. There is no indication in the documentation of how to run the GUI based migration
tools on Unix, only for Windows so we had to follow the manual route.
3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
to the DB variable setting scripts. It then says to run "migratedb.sh". None of
these files have extensions ".sh" - the files that were installed have no extension.
Obviously that did not stop us running them but the documentation needs correcting.
4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
is a second copy of this file in the bin folder called "setenv". Why are there
2 copies. Also I note that the one in bin is executable and the other is not.
All very confusing!!
5. The migratedb script fails to run because we have not previously run setDomain.
This is not documented.
6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
does not contain the expected folders. That basically means you cannot migrate
such a domain. We carried on with the process using the bpmdomain so that we could
at least migrate our database automatically.
7. Having run setDomain, we tried migratedb again but it failed because we had
not run switchdb. Again, this is not documented. We ran switchdb successfully.
8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
script migratedb then attempts to run a file called "migrate". This is evidence
that no-one has ever tested this script at BEA and we are very disconcerted by
this fact!! We renamed the script and ran migratedb again - this time it ran the
migrate script.
9. This still fails with the following errors (when calling migrateCommonRep)
-v (No such file or directory)
null
java.lang.NullPointerException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
at com.bea.eci.migration.Migrate.main(Migrate.java:73)
java.lang.NullPointerException
at com.bea.eci.migration.Migrate.main(Migrate.java:192)
10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
have sqlplus installed on the same machine as WLI and yet again this requirement
is not documented. At this point we gave up trying to run the migrate script as
there seemed to be no route forward.
The process we took to move from WLI2.0 (WLPI only) was as follows:
a. Since we had done no changes to filerealm.properties we simply copied the one
fron bpmdomain into our own domain.
b. We have been unable to run the step to migrate the common repository (see note
9). If this is referring to the XML repository then that should not be a problem
to us as we have not used it.
c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
script on our database. This seems to have successfully updated the database.
Lastly, having completed the migration process we tried to run the server but
it fails. This is because the startWeblogic script fails to call checkdomain properly.
We modified the line to become:
". $WLI_HOME/bin/checkdomain" # the '.' was missing
Does anyone else have any experiences with this that would help us all?
Pete--
Developer Relations Engineer
BEA Support

Factory Finder failure and _tmmsgrcv() SEGV

Hello,
we have a rather strange problem with WLE 5.1. One type of process, QD,
occasionally experiences a SEGV inside _tmmsgrcv(). The SEGV is usually
preceeded by a failure from the factory finder.
QD is a process that converts /Q messages into Croba requests. TMQFORWARD is
used to get the messages out of the /Q, and to invoke the Tuxedo service in
QD. QD then finds a Corba object that can handle the operation and invokes
the operation. There are multiple instances of TMQFORWARD, QD and CorbaApp
for the same service/object.
The functionality of QD is roughly this:
try {
f = find_on_factory_by_id( name);
if (CORBA::is_nil( f)) {
log( "no factory found");
return RETRY;
else {
h = Obj::_narrow( f);
if (CORBA::is_nil( h)) {
log( "narrow failed");
return RETRY;
catch( ...) {
log( "find factory failed");
if (tooManyFactoryFailures)
assert();
return( RETRY);
try {
h->ping(); // no-op to check that object is available
catch( INVALID_TRANSACTION) {
log( "object is busy");
CORBA::release( h);
return( RETRY);
catch ( ...) {
log( "ping failed");
CORBA::release( h);
return( RETRY);
try {
h->doOp( msg);
catch( ...) {
log( "operation failed");
CORBA::release( h);
return( RETRY);
CORBA::release( h);
return SUCCESS;
The outer function will call tpreturn indicating success, retry or abort.
Now, most of the time all is ok and this works for days. But once in a while
there is a problem.
The outcome is either an assert, because most attempts to find the factory
fail (there still are a few successes in between), or a SEGV on getting the
next message to be handled by the QD (it's a different message, not a
retry).
#0 0xfbaa4274 in _tmmsgrcv () from /opt/wle/lib/libtux.so.65
#1 0xfbad4c1c in _tmrcvrq () from /opt/wle/lib/libtux.so.65
#2 0xfbad6b58 in _tmrunserver () from /opt/wle/lib/libtux.so.65
#3 0xfbaba140 in _tmstartserver () from /opt/wle/lib/libtux.so.65
#4 0x4346c in main (argc=19, argv=<incomplete type>, N=<error type>) at
BS-6950.c:74
The failure scenario starts with a factory failure (log "find factory
failed", exception TRANSACTION_ROLLEDBACK). QD returns retry, and the
message remains on the /Q (with a delayed retry).
After that the behaviour is not consistent.
Sometimes QD crashes (SEGV) on receiving the next message.
Sometimes QD seems to succeed processing the next message (no errors logged,
no exceptions thrown), but the Corba Object never gets the message.
Sometimes QD fails again to get the factory, but the exception is either
INTERNAL or BAD_PARAM.
The above may be repeated in any combination until the final outcome (assert
or SEGV).
In one case (but only one) there was a LIBTUX_CAT:518: ERROR.
In some cases there is a LIBTUX_CAT:489: ERROR.
My suspicion is that there is a memory corruption somewhere. I have reviewed
our code many times and have not been able to find anything. I have also
searched BEA and the web, but have not found anything relevant.
Any suggestions?
Roger

Hi Todd,
thanks for your reply.
I started to answer your individual questions, but then we had a different
crash (in tmfmsgfree). I submitted that to BEA, and they found a known fix
in 8.1. Hopefully they will port it to WLE 5.1.
Have you tried running Purify or a similar tool to see if that helps?Yes, some time ago to fix a memory leak. At that time I didn't look
specifically for this problem, but anything unusual I would have noticed.
Also, have you been able to create a consistent reproducer?We can not reproduce it. On our performance test bed it happens about once
every other day (with 132 QD processes handling 3.5M messages). At the
customer site it happens two or 3 times a day, even though they have only
about 2M messages per day.
BEA Support can help youWe created a case and submitted a stack trace and core dump. They did not
find anything unusual.
but no releases were evident for your factories.That was my mistake in presenting the simplified code.
I'm also puzzled by your tooManyFactoryFailures assertion.Before I started working on the project, it was noticed that once in a blue
moon a QD process would enter a state where it would experience many factory
finder failures. No cause was found and the Assert was added to recover from
this. It was an early indication of the current problem. Since then the
factory failures have become more frequent and more severe (SEGV). That is
why I am looking at it again.
is there a reason you are hitting the factory finder each time?Again it is historical. I believe it was done to better do load-sharing.
Roger

PageFlow Bea 9 and BIRT

Similar Messages

Maybe you are looking for