[JBossWS] - JBossWS Exception
by landoo
Hi,
I am using JBossWS generated web services with EJB3 endpoint, but i get following exception:
| 10:01:43,122 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
| org.jboss.ws.WSException: Cannot find child element: arg0
| at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:891)
| at org.jboss.ws.core.CommonSOAPBinding.unbindRequestMessage(CommonSOAPBinding.java:343)
| at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:195)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:408)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
| at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
| at java.lang.Thread.run(Thread.java:595)
|
Any idea how to resolve it?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152593#4152593
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152593
18 years, 1 month
[Microcontainer] - Re: SchemaResolverDeployer is parsing but not deploying
by alesj
"david.lloyd(a)jboss.com" wrote : I think what I really want to do is to just provide a way to specify the various I/O beans, because that's all my (incorrectly-named) "deployments" really are for the most part. So I guess what I need to do is to figure out a way to "merge" in my metadata with the regular BeanMetaData - should just be a question of some JAXB research I hope...
You already done that. ;-)
e.g. you now have
| <dml:deployment>
| <dml:io someattrib="foobar" />
| <dml:remote otherattrib="barfoo" />
| </dml:deployment>
|
And you can simply do this
| <mc:deployment>
| <dml:deployment>
| <dml:io someattrib="foobar" />
| <dml:remote otherattrib="barfoo" />
| </dml:deployment>
| </mc:deployment>
|
But I would still leave your deployer.
And I would now add some generic deployer that takes custom metadata which implements BeanMetaDataFactory and turns it into component beans
| public class CustomMD2BMD<T extends BeanMetaDataFactory> extends SomeHandyHelperDeployer
| {
| public CustomMD2BMD(Class<T> metadata)
| {
| super(metadata);
| }
|
| public void deploy(DeploymentUnit unit, T deployment)
| {
| List<BMD> beans = deployment.getBeans();
| for(BMD bean : beans)
| putBMDtoComponent(bean);
| }
|
| ...
| }
|
And then adding such deployer would be 1line of xml/code:
| <bean name="DML2BMD" class="CustomMD2BMD">
| <constructor><parameter>io.DeploymentMetaData</parameter></constructor>
| </bean>
|
Or/and I might even do similar shortcut xml element (as I did with SRD).
Simple enough now? ;-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152589#4152589
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152589
18 years, 1 month
[JBoss AOP] - Re: problem with jboss loadtime weaving
by Moslem
10:14:36,468 INFO [Server] Starting JBoss (MX MicroKernel)...
10:14:36,468 INFO [Server] Release ID: JBoss [Trinity] 4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)
10:14:36,468 INFO [Server] Home Dir: D:\Pfe\jboss-4.2.0.GA\jboss-4.2.0.GA
10:14:36,468 INFO [Server] Home URL: file:/D:/Pfe/jboss-4.2.0.GA/jboss-4.2.0.GA/
10:14:36,468 INFO [Server] Patch URL: null
10:14:36,468 INFO [Server] Server Name: default
10:14:36,468 INFO [Server] Server Home Dir: D:\Pfe\jboss-4.2.0.GA\jboss-4.2.0.GA\server\default
10:14:36,468 INFO [Server] Server Home URL: file:/D:/Pfe/jboss-4.2.0.GA/jboss-4.2.0.GA/server/default/
10:14:36,469 INFO [Server] Server Log Dir: D:\Pfe\jboss-4.2.0.GA\jboss-4.2.0.GA\server\default\log
10:14:36,469 INFO [Server] Server Temp Dir: D:\Pfe\jboss-4.2.0.GA\jboss-4.2.0.GA\server\default\tmp
10:14:36,469 INFO [Server] Root Deployment Filename: jboss-service.xml
10:14:37,452 INFO [ServerInfo] Java version: 1.6.0_06,Sun Microsystems Inc.
10:14:37,452 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 10.0-b22,Sun Microsystems Inc.
10:14:37,452 INFO [ServerInfo] OS-System: Windows Vista 6.0,x86
10:14:38,263 INFO [Server] Core system initialized
10:14:41,587 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
10:14:41,587 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
10:14:42,633 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
10:14:42,633 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
10:14:43,117 INFO [TransactionManagerService] Starting recovery manager
10:14:43,320 INFO [TransactionManagerService] Recovery manager started
10:14:43,320 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
10:14:45,005 WARN [ServiceController] Problem creating service jboss.aop:service=AspectManager
java.lang.NullPointerException
at org.jboss.aop.deployment.AspectManagerServiceJDK5.attachTranslator(AspectManagerServiceJDK5.java:42)
at org.jboss.aop.deployment.AspectManagerService.createService(AspectManagerService.java:138)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:330)
at org.jboss.system.ServiceController.create(ServiceController.java:273)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.create(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Unknown Source)
10:14:47,471 INFO [EJB3Deployer] Starting java:comp multiplexer
10:14:50,046 INFO [ServiceEndpointManager] jbossws-1.2.1.GA (build=200704151756)
10:14:52,293 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre1.6.0_06\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jdk1.6.0_06\bin\..\jre\bin\client;C:\Program Files\Java\jdk1.6.0_06\bin\..\jre\bin;C:\Program Files\Java\jdk1.6.0_06\bin;C:\Program Files\Java\jre1.6.0_06\bin
10:14:52,419 INFO [Http11Protocol] Initialisation de Coyote HTTP/1.1 sur http-127.0.0.1-8080
10:14:52,435 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
10:14:52,435 INFO [Catalina] Initialization processed in 449 ms
10:14:52,435 INFO [StandardService] Démarrage du service jboss.web
10:14:52,450 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.GA
10:14:52,513 INFO [Catalina] Server startup in 73 ms
10:14:52,700 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
10:14:53,823 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
10:14:54,354 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp3446jbossws-context-exp.war/
10:14:54,542 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
10:14:55,509 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
10:14:56,321 INFO [MailService] Mail Service bound to java:/Mail
10:14:56,555 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
10:14:56,618 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
10:14:56,665 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
10:14:56,743 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
10:14:56,837 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
10:14:56,899 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
10:14:56,930 INFO [QuartzResourceAdapter] start quartz!!!
10:14:57,055 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
10:14:57,086 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
10:14:57,102 INFO [RAMJobStore] RAMJobStore initialized.
10:14:57,102 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
10:14:57,102 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
10:14:57,102 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
10:14:58,771 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
10:14:59,209 INFO [A] Bound to JNDI name: queue/A
10:14:59,209 INFO [B] Bound to JNDI name: queue/B
10:14:59,209 INFO [C] Bound to JNDI name: queue/C
10:14:59,209 INFO [D] Bound to JNDI name: queue/D
10:14:59,209 INFO [ex] Bound to JNDI name: queue/ex
10:14:59,240 INFO [testTopic] Bound to JNDI name: topic/testTopic
10:14:59,240 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
10:14:59,240 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
10:14:59,256 INFO [testQueue] Bound to JNDI name: queue/testQueue
10:14:59,349 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
10:14:59,412 INFO [DLQ] Bound to JNDI name: queue/DLQ
10:14:59,568 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
10:14:59,833 INFO [TomcatDeployer] deploy, ctxPath=/BpelAdminHelp, warUrl=.../tmp/deploy/tmp3476BpelAdminHelp-exp.war/
10:15:00,271 INFO [TomcatDeployer] deploy, ctxPath=/active-bpel, warUrl=.../deploy/active-bpel.war/
10:15:00,739 INFO [WebappClassLoader] validateJarFile(D:\Pfe\jboss-4.2.0.GA\jboss-4.2.0.GA\server\default\.\deploy\active-bpel.war\WEB-INF\lib\servlet-api.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
10:15:00,739 INFO [WebappClassLoader] validateJarFile(D:\Pfe\jboss-4.2.0.GA\jboss-4.2.0.GA\server\default\.\deploy\active-bpel.war\WEB-INF\lib\servlet.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
10:15:01,160 ERROR [STDERR] 22 mai 2008 10:15:01 org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet init
INFO: ActiveBPEL startup
10:15:02,253 ERROR [STDERR] 22 mai 2008 10:15:02 org.activebpel.rt.axis.bpel.AeAxisServerFactory initAxisServer
INFO: Initialized Axis Server
10:15:02,254 ERROR [STDERR] 22 mai 2008 10:15:02 org.activebpel.rt.axis.bpel.AeAxisServerFactory initAxisServer
INFO: Initialized Axis Client Config
10:15:02,348 ERROR [STDERR] 22 mai 2008 10:15:02 org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger logInfo
INFO: Loaded config file from D:\Pfe\jboss-4.2.0.GA\jboss-4.2.0.GA\server\default\bpr\aeEngineConfig.xml
10:15:03,783 ERROR [STDERR] 22 mai 2008 10:15:03 org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger logInfo
INFO: ********** ActiveBPEL In-Memory Configuration Initialized
10:15:04,080 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
10:15:04,377 INFO [TomcatDeployer] deploy, ctxPath=/testbj, warUrl=.../tmp/deploy/tmp3477testbj-exp.war/
10:15:04,611 INFO [TomcatDeployer] deploy, ctxPath=/testjbaop, warUrl=.../tmp/deploy/tmp3478testjbaop-exp.war/
10:15:04,782 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.aop:service=AspectManager
State: FAILED
Reason: java.lang.NullPointerException
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.aop:service=AspectManager
State: FAILED
Reason: java.lang.NullPointerException
10:15:04,954 INFO [Http11Protocol] Démarrage de Coyote HTTP/1.1 sur http-127.0.0.1-8080
10:15:05,002 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
10:15:05,017 INFO [Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)] Started in 28s:548ms
10:15:18,995 ERROR [STDERR] 22 mai 2008 10:15:18 org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger logInfo
INFO: [AeEngineAdmin.wsr] Starting WebServices deployment.
10:15:18,996 ERROR [STDERR] 22 mai 2008 10:15:18 org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger logInfo
INFO: [AeEngineAdmin.wsr] Deploying META-INF\service.wsdd
10:15:19,745 ERROR [STDERR] 22 mai 2008 10:15:19 org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger logInfo
INFO: [AeEngineAdmin.wsr] Finished WebServices deployment.
10:15:19,791 ERROR [STDERR] 22 mai 2008 10:15:19 org.activebpel.rt.axis.bpel.web.AeProcessEngineServlet$AeTomcatLogger logInfo
INFO: ********** ActiveBPEL In-Memory Configuration Started
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152588#4152588
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152588
18 years, 1 month
[JBoss Portal] - Re: Problem regarding renderURL param
by je.a.le
with plain jsp i don't know, but using a little trick inside the portlet do view you could.
the problem is from the processAction / doView method. doView keep renderParam (set in processAction), therefore, render 'old' data when switching back using the tab button. Unfortunately ActionRequest doesn't allow us to remove a renderParam - That would solve the problem - I tried using Attributes, properties but none seem to work.
The 'trick' I'm using in a similar problems is to pass param from processAction to doView using... session ! yes, it's quite dirty. Sample :
| public void processAction(ActionRequest request, ActionResponse response) throws PortletException, IOException {
|
| PortletSession session = request.getPortletSession(true);
| if (session != null) {
| String todo = request.getParameter("articleedit_todo");
| session.setAttribute("todo", todo);
| }
| //......
| }
|
| public void doView(RenderRequest request, RenderResponse response) throws PortletException, IOException {
| //.......
| PortletSession session = request.getPortletSession(true);
| Object todo = session.getAttribute("todo");
| session.setAttribute("todo", null);
| if ((todo == null ? "" : todo.toString()).compareTo("goedit") == 0) {
| getPortletContext().getRequestDispatcher("/WEB-INF/jsp/articles/ACAdminArticleEditPortlet_view.jsp").include(request, response);
| } else {
| getPortletContext().getRequestDispatcher("/WEB-INF/jsp/articles/ACAdminArticlePortlet_view.jsp").include(request, response);
| }
| }
| }
A+
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152587#4152587
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152587
18 years, 1 month