March 2012 - jboss-user - Jboss List Archives

[JBoss Web Services] - web service payload validation

by Gunnar Bostrom

Gunnar Bostrom [https://community.jboss.org/people/gunnarbos] created the discussion "web service payload validation" To view the discussion, visit: https://community.jboss.org/message/726591#726591 -------------------------------------------------------------- Hi, I use JBoss 7.1 final and would like JBoss to validate the payload. I've created an xsd-schema, a wsdl file and a server implementation. The service is annotaded with @SchemaValidation and executes fine but does not do any validation. Do I have to do anything more than add the annotation to force JBoss to validate the payload? /Gunnar -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/726591#726591] Start a new discussion in JBoss Web Services at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

2
2
0 / 0

[jBPM] - Re: Difficult workflow question

by Maciej Swiderski

Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion "Re: Difficult workflow question" To view the discussion, visit: https://community.jboss.org/message/727194#727194 -------------------------------------------------------------- I believe you got my idea quite good. Please find attached process diagram that I had in mind, note that I did not have time to make it runnable so number of things can go wrong, so to say. https://community.jboss.org/servlet/JiveServlet/showImage/2-727194-18289/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-727194-18... In general, you have a sub process with mutliple instance chanracteristics so you can decide on runtime how many groups you will have, currently two and they are driven by some variables. This is just addition to have it ready for adding more teams without modifying the process. Back to the main topic - yes you need to have a decision point after task is completed to decide if other intances (of a task/subprocess) should be cancelled or not. So if task will complete with Yes, it with throw an error (for now as it is avilable in current engine version and later on, can be changed to signal instead) that will be caught by all other active task/subprocess instances and cancel them and do what ever else is required. Regarding data, isn\t that true that sub process on completion will map its variables to its parent variables? I hope that it makes sense to you :) Cheers -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727194#727194] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

2
1
0 / 0

[JBoss Messaging] - JBoss MQ in Autosys

by Manisha Agrawal

Manisha Agrawal [https://community.jboss.org/people/manisha26] created the discussion "JBoss MQ in Autosys" To view the discussion, visit: https://community.jboss.org/message/727161#727161 -------------------------------------------------------------- Hi All, I am ware that JBoss MQ support is provided in Autosys. (CA Workload Automation version r11.3). Is there any documentation around it? If yes please redirect to it. Also, Is it possible to host Active MQ on JBoss and use it with Autosys. or austosys provides support specifically for JBoss MQ. Regards Manisha -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727161#727161] Start a new discussion in JBoss Messaging at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

1
0
0 / 0

[jBPM] - jBPM integration with webapp

by void void

void void [https://community.jboss.org/people/void_void] created the discussion "jBPM integration with webapp" To view the discussion, visit: https://community.jboss.org/message/727142#727142 -------------------------------------------------------------- Hi , I have a web application, My requirement: I would like my user to design the workflow using web based editor & save it & return them an identifier and use that process on some event of web app Is there any support available to do the same ? Thanks! Jigar -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727142#727142] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

2
4
0 / 0

[JBoss Cache] - Memory Leak through MVCCInvocationContext

by Niklas Schlimm

Niklas Schlimm [https://community.jboss.org/people/Niklas1973] created the discussion "Memory Leak through MVCCInvocationContext" To view the discussion, visit: https://community.jboss.org/message/727141#727141 -------------------------------------------------------------- I have a problem when I redeploying my App on Tomcat several times I am getting an OutOfMemoryError. I hav looked at the Memory and it shows MVCCInvocationContext thread local in the 8080 worker threads. The only way to remove the thread local is through CacheInvocationDelegate.setInvocationContext(null). The issue is that I don't have direct access here. The documentation says that InvocationContextInterceptor does the clean up here. It doesn't obviously. (I checked if its in the chain - it is ...) I have attached the Memory Analyzer screen shot. Any help would be appreciated. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727141#727141] Start a new discussion in JBoss Cache at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

1
0
0 / 0

[JBoss Messaging] - JBoss messaing 1.4.x - Failover in cluster with a vast number of messages in queues

by Antoni .....

Antoni ..... [https://community.jboss.org/people/acure] created the discussion "JBoss messaing 1.4.x - Failover in cluster with a vast number of messages in queues" To view the discussion, visit: https://community.jboss.org/message/727121#727121 -------------------------------------------------------------- Hi We have cluster of 2 nodes, and observe huge delay when jms starts, particularly when we have the great number of messages e.g. 100 000 000 in queues. After crash in table JBM_MSG_REF remain all informations about relations msg to nodes. First what server does when it starts is update this references, but not in a one bulk update, but updating one by one every row. When in JBM_MSG_REF is the vast number of tuples that increase a number of updates need to be done on startup, and it longer significantly time to stand up after crash. Sometimes it takes our servers 20 minutes to start after fail. Is any way to speed up the failover startup? We use JBoss 5.1.GA, JBoss Messaging 1.4.8 and Oracle as a persistence for jms. The same efect we observe using any earlier version 1.4.x. Best Regards - Antoni -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727121#727121] Start a new discussion in JBoss Messaging at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

1
0
0 / 0

[jBPM] - Re: Could not find process with id

by weihua gu

weihua gu [https://community.jboss.org/people/guwh] created the discussion "Re: Could not find process with id" To view the discussion, visit: https://community.jboss.org/message/727091#727091 -------------------------------------------------------------- Because lack jar.Suggestions sart your eclipse by: ant start.demo or ant start.eclipse then import project .it"s work OK -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727091#727091] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

1
0
0 / 0

[JBoss Web Services] - jboss6.0+spring3.0.7 + cxf2.5.2

by zw lin

zw lin [https://community.jboss.org/people/cantalou] created the discussion "jboss6.0+spring3.0.7 + cxf2.5.2" To view the discussion, visit: https://community.jboss.org/message/727074#727074 -------------------------------------------------------------- dear: recently i try to integral jboss6.0 ,spring3.0.7 and cxf2.5.2 ,first i put the spring + cxf into tomcat6.035 , it works. it also works when i put it into jboss(jbossweb-standalone server) with the configuration file <?xml version="1.0" encoding="UTF-8"?> <jboss-app> <loader-repository> apache.cxf:loader=webService.war <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> </jboss-app> from the page http://cxf.apache.org/docs/application-server-specific-configuration-guid... but when i put it into jboss(default server),i encounter the problem : 23:01:50,468 ERROR [[/webService]] Exception starting filter Resteasy: java.lang.RuntimeException: Unable to instantiate MessageBodyReader at org.jboss.resteasy.spi.ResteasyProviderFactory.registerProvider(ResteasyProviderFactory.java:760) [:6.0.0.Final] at org.jboss.resteasy.spi.ResteasyProviderFactory.registerProvider(ResteasyProviderFactory.java:742) [:6.0.0.Final] at org.jboss.resteasy.spi.ResteasyDeployment.registerProvider(ResteasyDeployment.java:467) [:6.0.0.Final] at org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:272) [:6.0.0.Final] at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:197) [:6.0.0.Final] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67) [:6.0.0.Final] at org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.init(FilterDispatcher.java:39) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447) [:6.0.0.Final] at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3246) [:6.0.0.Final] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3843) [:6.0.0.Final] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final] at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final] at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_30] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_30] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_30] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_30] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA] at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA] at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:53) [:2.2.0.GA] at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:41) [:2.2.0.GA] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA] at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:894) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:641) [jboss-dependency.jar:2.2.0.GA] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:182) [:2.2.0.GA] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:58) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.GA] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1571) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2] at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:151) [:0.2.2] at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94) [:0.2.2] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.GA] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA] at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicProfileActivation.start(ProfileActivationWrapper.java:190) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(ProfileActivationWrapper.java:87) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationService.activateProfile(ProfileActivationService.java:215) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationService.activate(ProfileActivationService.java:159) [:0.2.2] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.java:112) [:0.2.2] at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java:87) [:0.2.2] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:91) [:0.2.2] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:132) [:6.0.0.Final] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final] at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at java.lang.Thread.run(Thread.java:662) [:1.6.0_30] Caused by: java.lang.RuntimeException: Illegal to inject a message body into a singleton into public org.apache.cxf.jaxrs.provider.DataBindingProvider(org.apache.cxf.databinding.DataBinding) at org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:157) [:6.0.0.Final] at org.jboss.resteasy.core.ConstructorInjectorImpl.injectableArguments(ConstructorInjectorImpl.java:63) [:6.0.0.Final] at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:129) [:6.0.0.Final] at org.jboss.resteasy.spi.ResteasyProviderFactory.getProviderInstance(ResteasyProviderFactory.java:1038) [:6.0.0.Final] at org.jboss.resteasy.spi.ResteasyProviderFactory.addMessageBodyReader(ResteasyProviderFactory.java:478) [:6.0.0.Final] at org.jboss.resteasy.spi.ResteasyProviderFactory.registerProvider(ResteasyProviderFactory.java:756) [:6.0.0.Final] ... 88 more how could i fix it? or how could i do to deploy cxf app without the jbossws support in my war , the same deploy to server(jbossweb-standalone server)? thanks -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727074#727074] Start a new discussion in JBoss Web Services at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

1
1
0 / 0

[jBPM] - Re: jbpm process REST api for signaling process does not work (is it a bug?)

by Maciej Swiderski

Maciej Swiderski [https://community.jboss.org/people/swiderski.maciej] created the discussion "Re: jbpm process REST api for signaling process does not work (is it a bug?)" To view the discussion, visit: https://community.jboss.org/message/727017#727017 -------------------------------------------------------------- Your observations are generally correct. 5.2 does not support signal functionality and it is targeted for 5.3 so that\s why you see that process instances are not signalable. Why it is not signaled with REST API it is because it hardcodes the name of the signal to 'Signal', so if you use this name as signalRef you should be able to signal your active catch events. HTH -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727017#727017] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

1
0
0 / 0

[jBPM] - Re: Abort Parent Process and child sub process

by lakshmi sampath

lakshmi sampath [https://community.jboss.org/people/lakshmi.sampath] created the discussion "Re: Abort Parent Process and child sub process" To view the discussion, visit: https://community.jboss.org/message/727000#727000 -------------------------------------------------------------- Thanks Joao and Maciej. That made my day. I was troubleshooting that issue, and changing the flag immediately fixed my problem where parent process is now calling abort on child dependent work item handlers which were waiting. thanks lakshmi. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/727000#727000] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]

12 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user March 2012