[JCA/JBoss] - Re: Destroying connection that could not be successfully mat
by bortx
Hello,
I have reached this post because I am facing the same problem. I see that in the FAQ it says:
anonymous wrote : Q: I have strange pooling? Connections that are not matched in my
|
| matchManagedConnections
|
| are destroyed.
|
| A: Yes this is the default/expected behaviour.
I have had a look at the jca 1.5 specification and according to this issue it says the following
anonymous wrote : If the resource adapter cannot find an acceptable ManagedConnection instance, it
| returns a null value. In this case, the application server requests the resource
| adapter to create a new connection instance.
So, it does not say anything in particular about this behaviour.
Now I'm gonna explain my use case, on which I consider this is not the expected behaviour:
My resource adapter holds connections, each one have an associated window, so that on a request, and identifier is stored on the window to be removed later when an ACK is received. When a request is made, it may need one or more slots on the window, so I specify a ConnectionRequestInfo with the number of slots needed.
Suppose a request is made which needs 2 slots, and all connections in the pool have 1 free slot. The matchManagedConnections method returns null and application server creates a new Connection that is returned. At this moment, if existing connections are destroyed, their associated window information and actions on ACKs are lost. Other reason for not destroy them is that as they all have 1 slot free, they should be available for other 1 slot requests. Also, they will become available as ACKs come.
I have seen that using <application-managed-security/> not only changes this behaviour, as application must implement all connection pooling task. In my case a new connection is created on each request, so I suppose that no connection management is performed by jboss. In my opinion, I consider that this behaviour should be configurable on a policy property, so you can use all jboss services in your resource adapter as matchManagedConnections method and choose what to do with no matching connections.
I only want to explain my point of view in order to contribute on improving this amazing project. Thanks a lot!
Borja
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165307#4165307
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165307
17 years, 10 months
[EJB 3.0] - Problem with EJB3 MDB, & Entity Objects
by smeverts
I am having a problem with a project that I am currently working on. I have a process that imports a datafile which goes like:
1. a SAR detects the file is present
2. the SAR will then send a JMS message to the MDB
3. the MDB receives the message and then parses / imports the data creating Entity objects etc.
4. when the MDB has imported all of the records it then sends a list of IDs to the next MDB which would need to process it and so on.
Here's the problem. I import all of the records in basically the OnMessage function of the MDB using a couple of helper classes. When I go to send the message to the next MDB, the "NEXT" MDB receives the message looks up the entity by the ID provided in the message and it's not in the database even though we persisted it in the "FIRST" MDB... Even if in the "FIRST" MDB I call entityManager.Flush () and then EntityManager.Clear() it still has the same problem
Am I not using EJB correctly, should the MDB be using some other EJB object to process / import the records?
Any thoughts?
Thanks in advance,
Scott
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165305#4165305
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165305
17 years, 10 months
[JBoss jBPM] - Re: How to deploy a BPEL process using the APIs?
by dhanushgopinath
Hi Alex,
Where are the client properties configured? is it in jbpm.hibernate.cfg.xml ? I tried configuring the hsqldb-ds.xml to use it over tcp. I also made jbpm.hibernate.cfg.xml to use the JDBC Conenction Properties as you mentioned earlier.
But it was failing to load the BPEL. The Database Connection page in the JBPM BPEL was showing Database Connection Failure.
Please see my hsqldb-ds.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!-- The Hypersonic embedded database JCA connection factory config -->
|
| <!-- $Id: hsqldb-ds.xml 39791 2006-01-10 18:14:42Z dimitris $ -->
|
| <datasources>
| <local-tx-datasource>
|
| <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
| <!-- Datasources are not available outside the virtual machine -->
| <jndi-name>DefaultDS</jndi-name>
|
| <!-- For server mode db, allowing other processes to use hsqldb over tcp.
| This requires the org.jboss.jdbc.HypersonicDatabase mbean.
| <connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url> -->
|
| <!-- For totally in-memory db, not saved when jboss stops.
| The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
| <connection-url>jdbc:hsqldb:.</connection-url>
| -->
| <!-- For in-process persistent db, saved when jboss stops.
| The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
| -->
| <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url>
|
| <!-- The driver class -->
| <driver-class>org.hsqldb.jdbcDriver</driver-class>
|
| <!-- The login and password -->
| <user-name>sa</user-name>
| <password></password>
|
| <!--example of how to specify class that determines if exception means connection should be destroyed-->
| <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-->
|
| <!-- this will be run before a managed connection is removed from the pool for use by a client-->
| <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->
|
| <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
| <min-pool-size>5</min-pool-size>
|
| <!-- The maximum connections in a pool/sub-pool -->
| <max-pool-size>20</max-pool-size>
|
| <!-- The time before an unused connection is destroyed -->
| <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
| <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connections -->
| <idle-timeout-minutes>0</idle-timeout-minutes>
|
| <!-- sql to call when connection is created
| <new-connection-sql>some arbitrary sql</new-connection-sql>
| -->
|
| <!-- sql to call on an existing pooled connection when it is obtained from pool
| <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
| -->
|
| <!-- example of how to specify a class that determines a connection is valid before it is handed out from the pool
| <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionChecker</valid-connection-checker-class-name>
| -->
|
| <!-- Whether to check all statements are closed when the connection is returned to the pool,
| this is a debugging feature that should be turned off in production -->
| <track-statements/>
|
| <!-- Use the getConnection(user, pw) for logins
| <application-managed-security/>
| -->
|
| <!-- Use the security domain defined in conf/login-config.xml -->
| <security-domain>HsqlDbRealm</security-domain>
|
| <!-- Use the security domain defined in conf/login-config.xml or the
| getConnection(user, pw) for logins. The security domain takes precedence.
| <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
| -->
|
| <!-- HSQL DB benefits from prepared statement caching -->
| <prepared-statement-cache-size>32</prepared-statement-cache-size>
|
| <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
| <metadata>
| <type-mapping>Hypersonic SQL</type-mapping>
| </metadata>
|
| <!-- When using in-process (standalone) mode -->
| <depends>jboss:service=Hypersonic,database=localDB</depends>
| <!-- Uncomment when using hsqldb in server mode
| <depends>jboss:service=Hypersonic</depends>
| -->
| </local-tx-datasource>
|
| <!-- Uncomment if you want hsqldb accessed over tcp (server mode)
|
| <mbean code="org.jboss.jdbc.HypersonicDatabase"
| name="jboss:service=Hypersonic">
| <attribute name="Port">1701</attribute>
| <attribute name="BindAddress">localhost</attribute>
| <attribute name="Silent">true</attribute>
| <attribute name="Database">default</attribute>
| <attribute name="Trace">false</attribute>
| <attribute name="No_system_exit">true</attribute>
| </mbean>
| -->
|
| <!-- For hsqldb accessed from jboss only, in-process (standalone) mode -->
| <mbean code="org.jboss.jdbc.HypersonicDatabase"
| name="jboss:service=Hypersonic,database=localDB">
| <attribute name="Database">localDB</attribute>
| <attribute name="InProcessMode">true</attribute>
| </mbean>
|
| </datasources>
|
and jbpm.hibernate.cfg.xml
<?xml version='1.0' encoding='utf-8'?>
| <!DOCTYPE hibernate-configuration PUBLIC
| "-//Hibernate/Hibernate Configuration DTD 3.0//EN"
| "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
|
| <hibernate-configuration>
|
| <session-factory>
|
| <!-- SQL dialect -->
| <property name="hibernate.dialect">org.hibernate.dialect.HSQLDialect</property>
| <property name="hibernate.cache.provider_class">org.hibernate.cache.HashtableCacheProvider</property>
|
| <!-- JDBC connection properties (begin) === -->
| <!--
| <property name="hibernate.connection.driver_class">org.hsqldb.jdbcDriver</property>
| <property name="hibernate.connection.url">jdbc:hsqldb:mem:jbpm;sql.enforce_strict_size=true</property>
| <property name="hibernate.connection.username">sa</property>
| <property name="hibernate.connection.password"/>
| <property name="hibernate.hbm2ddl.auto">create</property> -->
| <!-- ==== JDBC connection properties (end) -->
|
| <!-- DataSource properties (begin) -->
| <property name="hibernate.connection.datasource">java:/DefaultDS</property>
| <!-- DataSource properties (end) -->
|
| <!-- JTA transaction properties (begin) ===
| <property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
| <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property>
| <property name="jta.UserTransaction">UserTransaction</property>
| ==== JTA transaction properties (end) -->
|
| <!-- logging properties (begin) -->
| <property name="hibernate.format_sql">true</property>
| <property name="hibernate.use_sql_comments">true</property>
| <!-- logging properties (end) -->
|
| <!-- ############################################ -->
| <!-- # mapping files with external dependencies # -->
| <!-- ############################################ -->
|
| <!-- following mapping file has a dependendy on -->
| <!-- 'bsh-{version}.jar'. -->
| <!-- uncomment this if you don't have bsh on your -->
| <!-- classpath. you won't be able to use the -->
| <!-- script element in process definition files -->
| <mapping resource="org/jbpm/graph/action/Script.hbm.xml"/>
|
| <!-- following mapping files have a dependendy on -->
| <!-- 'jbpm-identity.jar', mapping files -->
| <!-- of the pluggable jbpm identity component. -->
| <!-- Uncomment the following 3 lines if you -->
| <!-- want to use the jBPM identity mgmgt -->
| <!-- component. -->
| <!-- identity mappings (begin) -->
| <mapping resource="org/jbpm/identity/User.hbm.xml"/>
| <mapping resource="org/jbpm/identity/Group.hbm.xml"/>
| <mapping resource="org/jbpm/identity/Membership.hbm.xml"/>
| <!-- identity mappings (end) -->
|
| <!-- following mapping files have a dependendy on -->
| <!-- the JCR API -->
| <!-- jcr mappings (begin) ===
| <mapping resource="org/jbpm/context/exe/variableinstance/JcrNodeInstance.hbm.xml"/>
| ==== jcr mappings (end) -->
|
| <!-- ###################### -->
| <!-- # jbpm mapping files # -->
| <!-- ###################### -->
|
| <!-- hql queries and type defs -->
| <mapping resource="org/jbpm/db/hibernate.queries.hbm.xml" />
|
| <!-- graph.def mapping files -->
| <mapping resource="org/jbpm/graph/def/ProcessDefinition.hbm.xml"/>
| <mapping resource="org/jbpm/graph/def/Node.hbm.xml"/>
| <mapping resource="org/jbpm/graph/def/Transition.hbm.xml"/>
| <mapping resource="org/jbpm/graph/def/Event.hbm.xml"/>
| <mapping resource="org/jbpm/graph/def/Action.hbm.xml"/>
| <mapping resource="org/jbpm/graph/def/SuperState.hbm.xml"/>
| <mapping resource="org/jbpm/graph/def/ExceptionHandler.hbm.xml"/>
| <mapping resource="org/jbpm/instantiation/Delegation.hbm.xml"/>
|
| <!-- graph.node mapping files -->
| <mapping resource="org/jbpm/graph/node/StartState.hbm.xml"/>
| <mapping resource="org/jbpm/graph/node/EndState.hbm.xml"/>
| <mapping resource="org/jbpm/graph/node/ProcessState.hbm.xml"/>
| <mapping resource="org/jbpm/graph/node/Decision.hbm.xml"/>
| <mapping resource="org/jbpm/graph/node/Fork.hbm.xml"/>
| <mapping resource="org/jbpm/graph/node/Join.hbm.xml"/>
| <mapping resource="org/jbpm/graph/node/State.hbm.xml"/>
| <mapping resource="org/jbpm/graph/node/TaskNode.hbm.xml"/>
|
| <!-- context.def mapping files -->
| <mapping resource="org/jbpm/context/def/ContextDefinition.hbm.xml"/>
| <mapping resource="org/jbpm/context/def/VariableAccess.hbm.xml"/>
|
| <!-- taskmgmt.def mapping files -->
| <mapping resource="org/jbpm/taskmgmt/def/TaskMgmtDefinition.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/def/Swimlane.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/def/Task.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/def/TaskController.hbm.xml"/>
|
| <!-- module.def mapping files -->
| <mapping resource="org/jbpm/module/def/ModuleDefinition.hbm.xml"/>
|
| <!-- bytes mapping files -->
| <mapping resource="org/jbpm/bytes/ByteArray.hbm.xml"/>
|
| <!-- file.def mapping files -->
| <mapping resource="org/jbpm/file/def/FileDefinition.hbm.xml"/>
|
| <!-- scheduler.def mapping files -->
| <mapping resource="org/jbpm/scheduler/def/CreateTimerAction.hbm.xml"/>
| <mapping resource="org/jbpm/scheduler/def/CancelTimerAction.hbm.xml"/>
|
| <!-- graph.exe mapping files -->
| <mapping resource="org/jbpm/graph/exe/Comment.hbm.xml"/>
| <mapping resource="org/jbpm/graph/exe/ProcessInstance.hbm.xml"/>
| <mapping resource="org/jbpm/graph/exe/Token.hbm.xml"/>
| <mapping resource="org/jbpm/graph/exe/RuntimeAction.hbm.xml"/>
|
| <!-- module.exe mapping files -->
| <mapping resource="org/jbpm/module/exe/ModuleInstance.hbm.xml"/>
|
| <!-- context.exe mapping files -->
| <mapping resource="org/jbpm/context/exe/ContextInstance.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/TokenVariableMap.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/VariableInstance.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/variableinstance/ByteArrayInstance.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/variableinstance/DateInstance.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/variableinstance/DoubleInstance.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/variableinstance/HibernateLongInstance.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/variableinstance/HibernateStringInstance.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/variableinstance/LongInstance.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/variableinstance/NullInstance.hbm.xml"/>
| <mapping resource="org/jbpm/context/exe/variableinstance/StringInstance.hbm.xml"/>
|
| <!-- job mapping files -->
| <mapping resource="org/jbpm/job/Job.hbm.xml"/>
| <mapping resource="org/jbpm/job/Timer.hbm.xml"/>
| <mapping resource="org/jbpm/job/ExecuteNodeJob.hbm.xml"/>
| <mapping resource="org/jbpm/job/ExecuteActionJob.hbm.xml"/>
|
| <!-- taskmgmt.exe mapping files -->
| <mapping resource="org/jbpm/taskmgmt/exe/TaskMgmtInstance.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/exe/TaskInstance.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/exe/PooledActor.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/exe/SwimlaneInstance.hbm.xml"/>
|
| <!-- logging mapping files -->
| <mapping resource="org/jbpm/logging/log/ProcessLog.hbm.xml"/>
| <mapping resource="org/jbpm/logging/log/MessageLog.hbm.xml"/>
| <mapping resource="org/jbpm/logging/log/CompositeLog.hbm.xml"/>
| <mapping resource="org/jbpm/graph/log/ActionLog.hbm.xml"/>
| <mapping resource="org/jbpm/graph/log/NodeLog.hbm.xml"/>
| <mapping resource="org/jbpm/graph/log/ProcessInstanceCreateLog.hbm.xml"/>
| <mapping resource="org/jbpm/graph/log/ProcessInstanceEndLog.hbm.xml"/>
| <mapping resource="org/jbpm/graph/log/ProcessStateLog.hbm.xml"/>
| <mapping resource="org/jbpm/graph/log/SignalLog.hbm.xml"/>
| <mapping resource="org/jbpm/graph/log/TokenCreateLog.hbm.xml"/>
| <mapping resource="org/jbpm/graph/log/TokenEndLog.hbm.xml"/>
| <mapping resource="org/jbpm/graph/log/TransitionLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/VariableLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/VariableCreateLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/VariableDeleteLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/VariableUpdateLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/variableinstance/ByteArrayUpdateLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/variableinstance/DateUpdateLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/variableinstance/DoubleUpdateLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/variableinstance/HibernateLongUpdateLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/variableinstance/HibernateStringUpdateLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/variableinstance/LongUpdateLog.hbm.xml"/>
| <mapping resource="org/jbpm/context/log/variableinstance/StringUpdateLog.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/log/TaskLog.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/log/TaskCreateLog.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/log/TaskAssignLog.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/log/TaskEndLog.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/log/SwimlaneLog.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/log/SwimlaneCreateLog.hbm.xml"/>
| <mapping resource="org/jbpm/taskmgmt/log/SwimlaneAssignLog.hbm.xml"/>
|
| <!-- ###################### -->
| <!-- # bpel mapping files # -->
| <!-- ###################### -->
|
| <!-- hql queries and type defs -->
| <mapping resource="org/jbpm/bpel/persistence/db/hibernate.queries.hbm.xml" />
|
| <!-- graph.def mapping files -->
| <mapping resource="org/jbpm/bpel/graph/def/BpelProcessDefinition.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/def/ImportDefinition.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/def/Import.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/def/LinkDefinition.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/def/Activity.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/def/Namespace.hbm.xml" />
|
| <!-- graph.basic mapping files -->
| <mapping resource="org/jbpm/bpel/graph/basic/BasicActivity.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/basic/AssignOperation.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/basic/assign/Copy.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/basic/assign/From.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/basic/assign/To.hbm.xml" />
|
| <!-- graph.struct mapping files -->
| <mapping resource="org/jbpm/bpel/graph/struct/StructuredActivity.hbm.xml" />
|
| <!-- graph.scope mapping files -->
| <mapping resource="org/jbpm/bpel/graph/scope/Scope.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/scope/Handler.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/scope/Compensate.hbm.xml" />
|
| <!-- graph.exe mapping files -->
| <mapping resource="org/jbpm/bpel/graph/exe/LinkInstance.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/exe/ScopeInstance.hbm.xml" />
| <mapping resource="org/jbpm/bpel/graph/exe/FaultInstance.hbm.xml" />
|
| <!-- variable.def mapping files -->
| <mapping resource="org/jbpm/bpel/variable/def/VariableDefinition.hbm.xml" />
| <mapping resource="org/jbpm/bpel/variable/def/VariableType.hbm.xml" />
|
| <!-- variable.exe mapping files -->
| <mapping resource="org/jbpm/bpel/variable/exe/ElementInstance.hbm.xml" />
| <mapping resource="org/jbpm/bpel/variable/exe/MessageValue.hbm.xml" />
|
| <!-- sublang.def mapping files -->
| <mapping resource="org/jbpm/bpel/sublang/def/Snippet.hbm.xml" />
|
| <!-- alarm mapping files -->
| <mapping resource="org/jbpm/bpel/alarm/AlarmAction.hbm.xml" />
|
| <!-- integration.catalog mapping files -->
| <mapping resource="org/jbpm/bpel/integration/catalog/CatalogEntry.hbm.xml" />
|
| <!-- integration.def mapping files -->
| <mapping resource="org/jbpm/bpel/integration/def/CorrelationSetDefinition.hbm.xml" />
| <mapping resource="org/jbpm/bpel/integration/def/PartnerLinkDefinition.hbm.xml" />
| <mapping resource="org/jbpm/bpel/integration/def/Correlations.hbm.xml" />
| <mapping resource="org/jbpm/bpel/integration/def/Correlation.hbm.xml" />
| <mapping resource="org/jbpm/bpel/integration/def/MessageAction.hbm.xml" />
| <mapping resource="org/jbpm/bpel/integration/def/ReceiveAction.hbm.xml" />
| <mapping resource="org/jbpm/bpel/integration/def/ReplyAction.hbm.xml" />
| <mapping resource="org/jbpm/bpel/integration/def/InvokeAction.hbm.xml" />
|
| <!-- integration.exe mapping files -->
| <mapping resource="org/jbpm/bpel/integration/exe/CorrelationSetInstance.hbm.xml" />
| <mapping resource="org/jbpm/bpel/integration/exe/PartnerLinkInstance.hbm.xml" />
|
| <!-- endpointref mapping files -->
| <mapping resource="org/jbpm/bpel/endpointref/EndpointReference.hbm.xml" />
| <mapping resource="org/jbpm/bpel/endpointref/SoapEndpointReference.hbm.xml" />
|
| <!-- wsdl mapping files -->
| <mapping resource="org/jbpm/bpel/wsdl/impl/PropertyImpl.hbm.xml" />
| <mapping resource="org/jbpm/bpel/wsdl/impl/PartnerLinkTypeImpl.hbm.xml" />
| <mapping resource="org/jbpm/bpel/wsdl/impl/PropertyAliasImpl.hbm.xml" />
| <mapping resource="org/jbpm/bpel/wsdl/impl/OperationImpl.hbm.xml" />
| <mapping resource="org/jbpm/bpel/wsdl/impl/PortTypeImpl.hbm.xml" />
| <mapping resource="org/jbpm/bpel/wsdl/impl/OperationMember.hbm.xml" />
| <mapping resource="org/jbpm/bpel/wsdl/impl/MessageImpl.hbm.xml" />
| <mapping resource="org/jbpm/bpel/wsdl/impl/PartImpl.hbm.xml" />
|
| </session-factory>
|
| </hibernate-configuration>
Please let me know how will these two behave in this case over TCP.
When we configure it over TCP should other properties becommented? Like the Default Datasource and all?
Thanks
Dhanush
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165304#4165304
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165304
17 years, 10 months