July 2009 - jboss-user - Jboss List Archives

[JBoss jBPM] - Re: Forced installation of JBoss?

by sebastian.s

Hello shekharv, thanks for you reply. I am going to use the GA version. I got a bit confused with the version numbering when browsing the SourceForge download page. Is the problem described here ( http://www.jboss.org/index.html?module=bb&op=viewtopic&t=145459) also existent in 3.2.6.SP1 ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242447#4242447 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242447

17 years

1
0
0 / 0

sticky_session=0 + UseJk=false + HTTP Session Replication

by Nicholas Schuetz

Hello, I have a setup with: Two hardware load balancers -> 2 Apache 2.2 instances running mod_jk 1.2.28 LB w/ sticky_session=0 -> 2 JBossAS 4.2.3 Servers doing HTTP Session Replication via JBoss Clustering. * My hardware load balancers are not configured to do sticky sessions * My Apache 2.2 w/ mod_jk lb workers have sticky_session=0 set (No Sticky Sessions) Since I do not have sticky_session enabled do I still need to have UseJK=true and my jvmRoute value set for mod_jk LB and HTTP Session Replication to work? In deploy/jboss-web.deployer/META-INF/jboss-service.xml it reads: --- SNIP ---  <attribute name="UseJK">false</attribute> --- SNIP --- This suggest to me that unless you are using sticky_session=1 in mod_jk you don't need to set UseJK to true and the jvmRoute. Is this assumption correct? If UseJK is set to false does mod_jk LB still work with JBoss? Will other aspects of jboss clustering still function as they should i.e Session Replication? Thanks, Nick

17 years

1
0
0 / 0

[JBoss jBPM] - Some Questions about Spring JBPM4 Integration

by rmoskal

Greetings all: I've been working with the excellent demo project posted by Andries InzÃ© that shows how to integrate Spring and jBPM4 at http://www.inze.be/andries/. I've managed to get things working against the trunk code but not CR1. I see how we can pass arguments to the java objects in the spring context: <env type=âorg.jbpm.pvm.internal.history.HistorySessionâ/> I'm curious as to what else can be passed to the java object. Like I'd like to get a copy of the actual Execution. HistorySession has only one method. Also will it be possible to declare nodes that pull from the Spring context? I'm super excited about the combination of Spring/jBPM4. Thanks and regards, Robert Moskal Most Media brooklyn, USA View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242439#4242439 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242439

17 years

1
0
0 / 0

[JBossWS] - Re: WebService Client with MTOM - WSDL

by MichaW

attachmentservice_1.wsdl <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions name="AttachmentService" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..." xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:i0="http://ebus.onefox.nl/2009/2/4" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"> <wsdl:import namespace="http://ebus.onefox.nl/2009/2/4" location="AttachmentService.wsdl"/> <wsdl:types/> <wsdl:service name="AttachmentService"> <wsdl:port name="AttachmentServiceEndpoint" binding="i0:AttachmentServiceEndpoint"> <soap:address location="http://wkst02.onefox.nl/ebus/AttachmentService.svc"/> </wsdl:port> </wsdl:service> </wsdl:definitions> AttachmentService.wsdl <?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions targetNamespace="http://ebus.onefox.nl/2009/2/4" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..." xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:tns="http://ebus.onefox.nl/2009/2/4" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"> <wsp:Policy wsu:Id="AttachmentServiceEndpoint_policy"> <wsp:ExactlyOne> <wsp:All> <wsoma:OptimizedMimeSerialization xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"/> </wsp:All> </wsp:ExactlyOne> </wsp:Policy> <wsdl:types> <xsd:schema targetNamespace="http://ebus.onefox.nl/2009/2/4/Imports"> <xsd:import schemaLocation="AttachmentService_1.xsd" namespace="http://ebus.onefox.nl/2009/2/4"/> <xsd:import schemaLocation="AttachmentService_1_2_3.xsd" namespace="http://ebus.onefox.nl/2009/2/4/attachment"/> <xsd:import schemaLocation="AttachmentService_1_2.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/> <xsd:import schemaLocation="AttachmentService.xsd" namespace="http://ebus.onefox.nl/2009/2/4/data"/> <xsd:import schemaLocation="AttachmentService_1_2_3_4.xsd" namespace="http://schemas.microsoft.com/Message"/> </xsd:schema> </wsdl:types> <wsdl:message name="ReadDocumentMsg"/> <wsdl:message name="ReadDocumentMsg_Headers"> <wsdl:part name="AuthInfo" element="tns:AuthInfo"/> <wsdl:part name="Data" element="q1:ReadDocumentMsg" xmlns:q1="http://ebus.onefox.nl/2009/2/4/attachment"/> </wsdl:message> <wsdl:message name="AttachmentServiceReadDocumentResMsg"> <wsdl:part name="ReadDocumentContent" element="q2:ReadDocumentContent" xmlns:q2="http://ebus.onefox.nl/2009/2/4/attachment"/> </wsdl:message> <wsdl:message name="AttachmentServiceReadDocumentResMsg_Headers"> <wsdl:part name="Result" element="q3:ReadDocumentResultMsg" xmlns:q3="http://ebus.onefox.nl/2009/2/4/attachment"/> </wsdl:message> <wsdl:message name="WriteDocumentMsg"> <wsdl:part name="ReadDocumentContent" element="q4:ReadDocumentContent" xmlns:q4="http://ebus.onefox.nl/2009/2/4/attachment"/> </wsdl:message> <wsdl:message name="WriteDocumentMsg_Headers"> <wsdl:part name="AuthInfo" element="tns:AuthInfo"/> <wsdl:part name="Data" element="q5:WriteDocumentMsg" xmlns:q5="http://ebus.onefox.nl/2009/2/4/attachment"/> </wsdl:message> <wsdl:message name="AttachmentServiceWriteDocumentResMsg"/> <wsdl:message name="AttachmentServiceWriteDocumentResMsg_Headers"> <wsdl:part name="Result" element="q6:WriteDocumentResultMsg" xmlns:q6="http://ebus.onefox.nl/2009/2/4/attachment"/> </wsdl:message> <wsdl:portType name="AttachmentService"> <wsdl:operation name="ReadDocument"> <wsdl:input wsaw:Action="http://ebus.onefox.nl/2009/2/4/AttachmentService/ReadDocument" name="ReadDocumentMsg" message="tns:ReadDocumentMsg"/> <wsdl:output wsaw:Action="http://ebus.onefox.nl/2009/2/4/AttachmentService/ReadDocumentResponse" name="AttachmentServiceReadDocumentResMsg" message="tns:AttachmentServiceReadDocumentResMsg"/> </wsdl:operation> <wsdl:operation name="WriteDocument"> <wsdl:input wsaw:Action="http://ebus.onefox.nl/2009/2/4/AttachmentService/WriteDocument" name="WriteDocumentMsg" message="tns:WriteDocumentMsg"/> <wsdl:output wsaw:Action="http://ebus.onefox.nl/2009/2/4/AttachmentService/WriteDocumentResponse" name="AttachmentServiceWriteDocumentResMsg" message="tns:AttachmentServiceWriteDocumentResMsg"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="AttachmentServiceEndpoint" type="tns:AttachmentService"> <wsp:PolicyReference URI="#AttachmentServiceEndpoint_policy"/> <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="ReadDocument"> <soap:operation soapAction="http://ebus.onefox.nl/2009/2/4/AttachmentService/ReadDocument" style="document"/> <wsdl:input name="ReadDocumentMsg"> <soap:header message="tns:ReadDocumentMsg_Headers" part="AuthInfo" use="literal"/> <soap:header message="tns:ReadDocumentMsg_Headers" part="Data" use="literal"/> <soap:body use="literal"/> </wsdl:input> <wsdl:output name="AttachmentServiceReadDocumentResMsg"> <soap:header message="tns:AttachmentServiceReadDocumentResMsg_Headers" part="Result" use="literal"/> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> <wsdl:operation name="WriteDocument"> <soap:operation soapAction="http://ebus.onefox.nl/2009/2/4/AttachmentService/WriteDocument" style="document"/> <wsdl:input name="WriteDocumentMsg"> <soap:header message="tns:WriteDocumentMsg_Headers" part="AuthInfo" use="literal"/> <soap:header message="tns:WriteDocumentMsg_Headers" part="Data" use="literal"/> <soap:body use="literal"/> </wsdl:input> <wsdl:output name="AttachmentServiceWriteDocumentResMsg"> <soap:header message="tns:AttachmentServiceWriteDocumentResMsg_Headers" part="Result" use="literal"/> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> </wsdl:definitions> AttachmentService.xsd <?xml version="1.0" encoding="UTF-8"?> <xs:schema elementFormDefault="qualified" targetNamespace="http://ebus.onefox.nl/2009/2/4/data" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://ebus.onefox.nl/2009/2/4/data"> <xs:complexType name="AuthInfo"> <xs:sequence> <xs:element name="Library" nillable="true" type="xs:string"/> <xs:element name="Username" nillable="true" type="xs:string"/> <xs:element name="Password" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> <xs:element name="AuthInfo" nillable="true" type="tns:AuthInfo"/> <xs:complexType name="ReturnFields"> <xs:sequence> <xs:element minOccurs="0" maxOccurs="unbounded" name="ReturnField" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> <xs:element name="ReturnFields" nillable="true" type="tns:ReturnFields"/> <xs:complexType name="Result"> <xs:sequence> <xs:element minOccurs="0" name="ErrCode" type="xs:int"/> <xs:element minOccurs="0" name="ErrDescription" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> <xs:element name="Result" nillable="true" type="tns:Result"/> <xs:complexType name="Fields"> <xs:sequence> <xs:element minOccurs="0" maxOccurs="unbounded" name="Field" nillable="true" type="tns:Field"/> </xs:sequence> </xs:complexType> <xs:element name="Fields" nillable="true" type="tns:Fields"/> <xs:complexType name="Field"> <xs:sequence> <xs:element name="Name" nillable="true" type="xs:string"/> <xs:element name="Value" nillable="true" type="xs:string"/> </xs:sequence> </xs:complexType> <xs:element name="Field" nillable="true" type="tns:Field"/> </xs:schema> AttachmentService_1.xsd <?xml version="1.0" encoding="UTF-8"?> <xs:schema elementFormDefault="qualified" targetNamespace="http://ebus.onefox.nl/2009/2/4" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://ebus.onefox.nl/2009/2/4"> <xs:import schemaLocation="AttachmentService.xsd" namespace="http://ebus.onefox.nl/2009/2/4/data"/> <xs:element name="AuthInfo" nillable="true" type="q1:AuthInfo" xmlns:q1="http://ebus.onefox.nl/2009/2/4/data"/> </xs:schema> AttachmentService_1_2.xsd <?xml version="1.0" encoding="UTF-8"?> <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://schemas.microsoft.com/2003/10/Serialization/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.microsoft.com/2003/10/Serialization/"> <xs:element name="anyType" nillable="true" type="xs:anyType"/> <xs:element name="anyURI" nillable="true" type="xs:anyURI"/> <xs:element name="base64Binary" nillable="true" type="xs:base64Binary"/> <xs:element name="boolean" nillable="true" type="xs:boolean"/> <xs:element name="byte" nillable="true" type="xs:byte"/> <xs:element name="dateTime" nillable="true" type="xs:dateTime"/> <xs:element name="decimal" nillable="true" type="xs:decimal"/> <xs:element name="double" nillable="true" type="xs:double"/> <xs:element name="float" nillable="true" type="xs:float"/> <xs:element name="int" nillable="true" type="xs:int"/> <xs:element name="long" nillable="true" type="xs:long"/> <xs:element name="QName" nillable="true" type="xs:QName"/> <xs:element name="short" nillable="true" type="xs:short"/> <xs:element name="string" nillable="true" type="xs:string"/> <xs:element name="unsignedByte" nillable="true" type="xs:unsignedByte"/> <xs:element name="unsignedInt" nillable="true" type="xs:unsignedInt"/> <xs:element name="unsignedLong" nillable="true" type="xs:unsignedLong"/> <xs:element name="unsignedShort" nillable="true" type="xs:unsignedShort"/> <xs:element name="char" nillable="true" type="tns:char"/> <xs:simpleType name="char"> <xs:restriction base="xs:int"/> </xs:simpleType> <xs:element name="duration" nillable="true" type="tns:duration"/> <xs:simpleType name="duration"> <xs:restriction base="xs:duration"> <xs:pattern value="\-?P(\d*D)?(T(\d*H)?(\d*M)?(\d*(\.\d*)?S)?)?"/> <xs:minInclusive value="-P10675199DT2H48M5.4775808S"/> <xs:maxInclusive value="P10675199DT2H48M5.4775807S"/> </xs:restriction> </xs:simpleType> <xs:element name="guid" nillable="true" type="tns:guid"/> <xs:simpleType name="guid"> <xs:restriction base="xs:string"> <xs:pattern value="[\da-fA-F]{8}-[\da-fA-F]{4}-[\da-fA-F]{4}-[\da-fA-F]{4}-[\da-fA-F]{12}"/> </xs:restriction> </xs:simpleType> <xs:attribute name="FactoryType" type="xs:QName"/> <xs:attribute name="Id" type="xs:ID"/> <xs:attribute name="Ref" type="xs:IDREF"/> </xs:schema> AttachmentService_1_2_3.xsd <?xml version="1.0" encoding="UTF-8"?> <xs:schema elementFormDefault="qualified" targetNamespace="http://ebus.onefox.nl/2009/2/4/attachment" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://ebus.onefox.nl/2009/2/4/attachment"> <xs:import schemaLocation="AttachmentService.xsd" namespace="http://ebus.onefox.nl/2009/2/4/data"/> <xs:import schemaLocation="AttachmentService_1_2_3_4.xsd" namespace="http://schemas.microsoft.com/Message"/> <xs:complexType name="ReadDocumentMsg"> <xs:sequence> <xs:element name="DocNumber" type="xs:int"/> <xs:element minOccurs="0" name="Version" type="xs:int"/> <xs:element name="Form" nillable="true" type="xs:string"/> <xs:element minOccurs="0" name="Checkout" type="xs:boolean"/> <xs:element minOccurs="0" name="ReturnFields" nillable="true" type="q1:ReturnFields" xmlns:q1="http://ebus.onefox.nl/2009/2/4/data"/> </xs:sequence> </xs:complexType> <xs:element name="ReadDocumentMsg" nillable="true" type="tns:ReadDocumentMsg"/> <xs:element name="ReadDocumentContent" type="q2:StreamBody" xmlns:q2="http://schemas.microsoft.com/Message"/> <xs:complexType name="ReadDocumentResultMsg"> <xs:complexContent mixed="false"> <xs:extension base="q3:Result" xmlns:q3="http://ebus.onefox.nl/2009/2/4/data"> <xs:sequence> <xs:element minOccurs="0" name="DocNumber" type="xs:int"/> <xs:element minOccurs="0" name="Version" type="xs:int"/> <xs:element minOccurs="0" name="Fields" nillable="true" type="q3:Fields"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:element name="ReadDocumentResultMsg" nillable="true" type="tns:ReadDocumentResultMsg"/> <xs:complexType name="WriteDocumentMsg"> <xs:sequence> <xs:element name="DocNumber" type="xs:int"/> <xs:element minOccurs="0" name="Version" type="xs:int"/> <xs:element name="Form" nillable="true" type="xs:string"/> <xs:element minOccurs="0" name="Checkin" type="xs:boolean"/> <xs:element minOccurs="0" name="ReturnFields" nillable="true" type="q4:ReturnFields" xmlns:q4="http://ebus.onefox.nl/2009/2/4/data"/> <xs:element minOccurs="0" name="CreateNewVersion" type="xs:boolean"/> </xs:sequence> </xs:complexType> <xs:element name="WriteDocumentMsg" nillable="true" type="tns:WriteDocumentMsg"/> <xs:complexType name="WriteDocumentResultMsg"> <xs:complexContent mixed="false"> <xs:extension base="q5:Result" xmlns:q5="http://ebus.onefox.nl/2009/2/4/data"> <xs:sequence> <xs:element minOccurs="0" name="DocNumber" type="xs:int"/> <xs:element minOccurs="0" name="Version" type="xs:int"/> <xs:element minOccurs="0" name="Fields" nillable="true" type="q5:Fields"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:element name="WriteDocumentResultMsg" nillable="true" type="tns:WriteDocumentResultMsg"/> </xs:schema> AttachmentService_1_2_3_4.xsd <?xml version="1.0" encoding="UTF-8"?> <xs:schema elementFormDefault="qualified" targetNamespace="http://schemas.microsoft.com/Message" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.microsoft.com/Message"> <xs:simpleType name="StreamBody"> <xs:restriction base="xs:base64Binary"/> </xs:simpleType> </xs:schema> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242438#4242438 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242438

17 years

1
0
0 / 0

[JBoss Cache: Core Edition] - Eviction queue fills up causing threads to block

by Jeremy Stone

We have a problem whereby we have seen the following message logged continuously on a customer's installation of our software that uses JBoss Cache with Hibernate: Warning putNodeEvent(): eviction node event queue size is at 98% threshold value of capacity: 200000 Region: /query/entity/by_name You will need to reduce the wakeUpIntervalSeconds parameter. We have seen this only once so far. It does not appear to recur after a server restart. A stack dump shows many threads waiting to put nodes on to the eviction queue. The following is representative... Thread: pool-21-thread-4 : priority:5, demon:false, threadId:144, threadState:WAITING, lockName:java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@584b2d | | sun.misc.Unsafe.park(Native Method) | java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) | java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925) | java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:254) | org.jboss.cache.RegionImpl.registerEvictionEvent(RegionImpl.java:249) | org.jboss.cache.RegionImpl.registerEvictionEvent(RegionImpl.java:234) | org.jboss.cache.interceptors.EvictionInterceptor.registerEvictionEventToRegionManager(EvictionInterceptor.java:252) | ...etc | org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118) | org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596) | org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306) | org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:328) | ...etc | The EvictionTimer thread appears just to waiting for something to do... Thread: EvictionTimer-0 : priority:5, demon:true, threadId:88, threadState:WAITING, lockName:java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@353fbf | | sun.misc.Unsafe.park(Native Method) | java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) | java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925) | java.util.concurrent.DelayQueue.take(DelayQueue.java:160) | java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:583) | java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:576) | java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947) | java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) | java.lang.Thread.run(Thread.java:619) The only inkling as to what is occurring is that perhaps an eviction algorithm (silently) threw an unchecked exception causing the EvictionTimerTask Task to no longer be scheduled. (see http://java.sun.com/javase/6/docs/api/java/util/concurrent/ScheduledExecu... which states '...If any execution of the task encounters an exception, subsequent executions are suppressed....'). Even if this is not the cause of our problem then EvictionTimerTask seems susceptible to this behaviour. Maybe you should consider using something like the Spring Framework DelegatingExceptionProofRunnable (http://static.springsource.org/spring/docs/2.5.6/api/org/springframework/...). Any thoughts on this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242437#4242437 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242437

17 years

1
0
0 / 0

[JBoss jBPM] - Re: jBPM4: Manually created task can't block the execution

by kukeltje

wow... please... a little patience ;-). This is all free (as in beer) time of others. You ask for progress in less than 9 hours from Shekarv's posting AND a little over 9 hours from your original posting. In between you already had two replies. Most would be jealous. You could also have a look at the foreach forkhandler in jBPM 3 that is in the wiki. Yes it is for jBPM 3, but some concepts are the same. And maybe the implementation of the taskactivity in th source of jBPM 4. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242436#4242436 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242436

17 years

1
0
0 / 0

[JBossWS] - WebService Client with MTOM

by MichaW

Hi, I'm using jbossws-native-2.0.1 (default for the AS 4.2.2.GA). I've used ws-consume on a wsdl from a thirdparty (see attached file). When I try the create the service Service service = Service.create(getWsdlUrl(), getServiceName()); I get an error Caused by: org.jboss.ws.WSException: Cannot deploy null policy! | at org.jboss.ws.extensions.policy.deployer.PolicyDeployer.deployClientSide(PolicyDeployer.java:146) | at org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder.deployPolicyClientSide(PolicyMetaDataBuilder.java:310) | at org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder.deployPolicy(PolicyMetaDataBuilder.java:277) | at org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder.processPolicies(PolicyMetaDataBuilder.java:236) | at org.jboss.ws.extensions.policy.metadata.PolicyMetaDataBuilder.processPolicyExtensions(PolicyMetaDataBuilder.java:193) | at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:93) | at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:131) | at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:61) | at javax.xml.ws.Service.<init>(Service.java:83) | at javax.xml.ws.Service.create(Service.java:721) | at nl.denhaag.gbd.services.ebus.attachmentservice.client.AttachmentServiceClient.initEndpoint(AttachmentServiceClient.java:63) | ... 43 more When I use the same code on a webservice that does not use MTOM everything is working fine. What should I do to provide a policy for MTOM on the clientside? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242434#4242434 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242434

17 years

1
0
0 / 0

[JBoss jBPM] - Re: SQL error executing test process

by kukeltje

Dialect is correct. recreation of View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242432#4242432 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242432

17 years

1
0
0 / 0

[JBossWS] - DOM API on SOAPElementImpl causes NotImplementedException

by gang.yang

I'm working in the area where I need to process SOAP messages as DOM. I've been working with JBossWS as well as other providers. I found that JBossWS's SOAPElement implementation does not support many DOM APIs, such as getTextContent and getIdAttributeNode. Although these seem to be convenience APIs, but are used by our software as well as other 3rd party software. Lacking them limited JBossWS's capatibilties. I'm wondering why JBossWS did not implement them since all other providers seem to support them and if JBossWS has a plan to do so. Thanks, Gang View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242431#4242431 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242431

17 years

1
0
0 / 0

[JBoss jBPM] - Re: Hibernate error while deploying process in a web applica

by kukeltje

8000 lines? Of just jBPM and hibernate debug? If so then look at the stacktrace and put less packages in debug mode. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242430#4242430 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242430

17 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2009