All Downloads are FREE. Search and download functionalities are using the official Maven repository.

META-INF.xsd.smooks.datasource-1.4.xsd Maven / Gradle / Ivy

There is a newer version: 2.0.1
Show newest version



	

	
		Smooks Datasource Configuration
	


	
		
			
				Direct datasource configuration
				The direct datasource resource creates a connection to a datasource and
				makes it available in the ExecutionContext. The datasource can then be used
				by other cartridges to access the datasource.
			
		
	

	
		
			
				Direct Datasource
			
		
		
			
				
					
						
							The element on which the datasource is bound. On the visitAfter
							of the element the connection does a Commit or Rollback depending
							if a exception got thrown.
						
					
				
				
					
						
							The namespace of the bindOnElement element
						
					
				
				
					
						
							The reference name of the datasource. This name must be used
							to retrieve the datasource from the ExecutionContext.
						
					
				
				
					
						
							If the datasource should automaticly commit.
						
					
				
				
					
						
							The JDBC driver name
						
					
				
				
					
						
							The JDBC URL
						
					
				
				
					
						
							The username
						
					
				
				
					
						
							The password
						
					
				
			
		
	

	
		
			
				JNDI datasource configuration
				The JNDI datasource resource retrieves a datasource from the JNDI and
				makes it available in the ExecutionContext. The datasource can then be used
				by other cartridges to access the datasource.
			
		
	

	
		
			
				JNDI Datasource
			
		
		
			

				
					
						
							The element on which the datasource is
							bound. On the visitAfter of the element the
							connection does a commit or rollback
							depending if a exception got thrown.
						
					
				
				
					
						
							The reference name of the datasource. This
							name must be used to retrieve the datasource
							from the ExecutionContext.
						
					
				
				
					
						
							The JNDI path of the datasource.
						
					
				
				
					
						
							The transaction manager used to manage the transaction.
						
					
					
						
							
								
									
										The JDBC transaction manager uses the rollback/commit methods from
										the connection object. The autoCommit flag can be set with the
										autoCommit attribute.
										The setAutoCommitAllowed has no effect when this Transaction Manager
										is set.
									
								
							
							
								
									
										The JTA transaction manager uses JTA UserTransaction to begin/commit/rollback
										the transaction. The UserTransaction jndi address must be set in
										the transactionJndi attribute. The autoCommit is always false, but
										the setAutoCommitAllowed determines if the setAutoCommit method from
										the Connection object is executed to disable the autoCommit.
									
								
							
							
								
									
										The external transaction manager doesn't manage the transaction but
										allowes an external system to manager the transaction.
										The autoCommit flag can still be controlled if the setAutoCommitAllowed
										attribute is set to true.
									
								
							
						
					
				
				
					
						
							If the transactionManager attribute is set to JTA then this attribute must be
							set to the JNDI address of the UserTransaction object.
						
					
				
				
					
						
							If the datasource should automaticly commit.

							If the attribute 'setAutoCommitAllowed' or
							'manageTransaction' is set to false then
							this attribute has no effect.
						
					
				

				
					
						
							If Smooks is allowed to set the autoCommit
							on the connection.

							If the attribute 'manageTransaction' is set
							to false then this attribute has no effect.
						
					
				

			
		
	





© 2015 - 2025 Weber Informatics LLC | Privacy Policy