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

META-INF.sca-policy-1.1-intents-definitions-cd04.xml Maven / Gradle / Ivy

There is a newer version: 2.0.1
Show newest version



                 
	                 
        
                
			Communication through the binding requires that the 
			server is authenticated by the client
                
                
                
        

        
                
			Communication through the binding requires that the 
			client is authenticated by the server
                
                
                
        

        
                
			A convenience intent to help migration
                
        

        
                
			Communication through the binding requires that the
			client and server to authenticate each other
                
        

        
                
			Communication through the binding prevents unauthorized 
			users from reading the messages
                
                
                
        

        
                
			Communication through the binding prevents tampering 
			with the messages sent between the client and the service.
                
                
                
        

        
                
			Ensures clients are authorized to use services. 
                
        

	
	    
        
                
			This intent is used to indicate that a message sent
			by a client is always delivered to the component.
                
        

        
                
			This intent is used to indicate that a message that was 
			successfully sent by a client is not delivered more than 
			once to the component.
                
        

        
                
			This profile intent is used to indicate that a message sent 
			by a client is always delivered to the component. It also 
			indicates that duplicate messages are not delivered to the 
			component.
            
        

        
                
			This intent is used to indicate that all the messages are 
			delivered to the component in the order they were sent by 
			the client.
                
        
	
	
        
                
		A managed transaction environment is necessary in order to 
		run the component. The specific type of managed transaction 
		needed is not constrained.
                
                
                        
			For a component marked with managedTransaction.global 
			a global transaction needs to be present before dispatching 
			any method on the component - using any transaction 
			propagated from the client or else beginning and completing 
			a new transaction. 
                        
                
                
                        
			A component marked with managedTransaction.local needs to 
			run within a local transaction containment (LTC) that 
			is started and ended by the SCA runtime.
                        
                
        

        
                
		A component marked with noManagedTransaction needs to run without 
		a managed transaction, under neither a global transaction nor 
		an LTC. A transaction propagated to the hosting SCA runtime 
		is not joined by the hosting runtime on behalf of a 
		component marked with noManagedtransaction.
                
        

        
                
		For a reference marked as transactedOneWay any OneWay invocation 
		messages are transacted as part of a client global 
		transaction.
		For a service marked as transactedOneWay any OneWay invocation 
		message are received from the transport binding in a 
		transacted fashion, under the service’s global transaction.
                
        

        
                
		For a reference indicates that any OneWay invocation messages 
		are sent immediately regardless of any client transaction.
		For a service indicates that any OneWay invocation is 
		received immediately regardless of any target service 
		transaction.
                
        

        
                
		A service marked with propagatesTransaction is dispatched 
		under any propagated (client) transaction and the service binding 
		needs to be capable	of receiving a transaction context.
		A reference marked with propagatesTransaction propagates any 
		transaction context under which the client runs when the 
		reference is used for a request-response interaction and the 
		binding of a reference marked with propagatesTransaction needs to
		be capable of propagating a transaction context. 
                
        

        
                
		A service marked with suspendsTransaction is not dispatched 
		under any propagated (client) transaction.
		A reference marked with suspendsTransaction does not propagate 
		any transaction context under which the client runs when the 
		reference is used.
                
        
	
        
                
			Used to indicate that the component requires both the 
			managedTransaction.global and the propagatesTransactions 
			intents
                
        
	
		
	
                
			Indicates that request/response operations for the 
			interface of this wire are "long running" and must be
			treated as two separate message transmissions
                
    
	
	
                
			Specifies that the EJB API is needed to communicate with
			the service or reference.
                
    
    
	
		
		Specifies that the SOAP messaging model is used for delivering 
		messages.
                
                
                
    

    
                
		Requires that the messages are delivered and received via the 
		JMS API.
                
    

    
                
		This intent can only be used on a reference. Indicates that the 
		client is not able to handle new inbound connections. The binding 
		and callback binding are configured so that any 
		response or callback comes either through a back channel of the 
		connection from the client to the server or by having the client 
		poll the server for messages. 
                
    
	




© 2015 - 2024 Weber Informatics LLC | Privacy Policy