Public

Creates a new session using credentials of the sessionparameter. The new session
is not yet attached

createSession

 Sets the timeout for all sockets opened to (not fro) the COM server for this
session. Default value

setGlobalSocketTimeout

Used to destroy the session, this release all references of the COM server and
it's interfaces. It s

destroySession

 Sets the use of NTLM2 Session Security. Framework will use NTLM Packet Level
Privacy and Sign\Seal 

useSessionSecurity

<init>

addToSession

debug_addIpids

debug_delIpids

equals

Gets the domain of the user associated with this session.

getDomain

Returns the global timeout applied to all sockets opened from this session to
COM Server.

getGlobalSocketTimeout

getLocalHost

getLocalhostAddressAsIPString

getLocalhostAddressAsIPbytes

getLocalhostCanonicalAddressAsString

getPassword

Returns a unique identifier for this session.

getSessionIdentifier

getStub

getTargetServer

getUnreferencedHandler

JISession

Updating database using SQL prepared statement

A border layout lays out a container, arranging and resizing its components to
fit in five regions: 

java.awt.BorderLayout

Wraps an existing Writer and buffers the output. Expensive interaction with the
underlying reader is

java.io.BufferedWriter

A controller for the selection of SelectableChannel objects. Selectable channels
can be registered w

java.nio.channels.Selector

A parser that parses a text string of primitive types and strings with the help
of regular expressio

java.util.Scanner

Defines the contract between a returned instance and the runtime when an
application needs to provid

javax.ws.rs.core.Response

Provides Base64 encoding and decoding as defined by RFC 2045.This class
implements section 6.8. Base

org.apache.commons.codec.binary.Base64

runOnUiThread

getExternalFilesDir

scheduleAtFixedRate

//now read the session and prepare information for the stub.

"Got the class not registered exception , will attempt setting entries based on status flags..."

//		if (session.isSessionSecurityEnabled())

//			super.getProperties().setProperty("rpc.ntlm.seal", "true");

//			super.getProperties().setProperty("rpc.ntlm.sign", "true");

//			super.getProperties().setProperty("rpc.ntlm.keyExchange", "true");

//			super.getProperties().setProperty("rpc.ntlm.keyLength", "128");

//			super.getProperties().setProperty("rpc.ntlm.ntlm2", "true");

/** Instantiates a JIComServer represented by the interfacePointer param. There are cases where a COM server may hand down a 
	 * reference to a different COM server(which may or may not be on the same machine) and we would like to hook in between. 
	 * The <code>IJIComObject</code> interface is usable only in the context of the current JIComServer, but when the interfacePointer 
	 * is of a completely different COM server, the JIObjectFactory APIs will not work. The reason is the interface pointer passed to those 
	 * APIs expects to belong only to a single and same COM server (say 'A'). If by any chance, that COM server passes a reference to you 
	 * of another COM server (say 'B') on a different machine, the <code>IJIComObject</code> so returned from <code>JIObjectFactory</code> APIs 
	 * will result in "Method not found" Exceptions (or others) since the pointer returned via that will always place calls to 'A' instead of 'B'. 
	 * Under such scenarios you must use this API. This is not a usual case and for reasons related to nature of DCOM, will be very well documented 
	 * in the Developers guide of your COM server. 
	 * 
	 * The DCOM specs refer to this as the "middleman" case. (Section 3.3.1) 
	 * 
	 * @param session Please use a new session and not an already bounded one. The <code>JISession.createSession(JISession)</code> can be used to create a new session.
	 * @param interfacePointer reference to a different COM server pointer.
	 * @param ipAddress		 Can be <code>null</code>. Sometimes there are many adapters (virtual as well) on the Target machine to which this interface pointer belongs,
	 * 						 which may get sent as part of the interface pointer and consequently this call will fail since it is a possibility that IP is not reachable via this machine.
	 * 						 The developer can send in the valid IP and if found in the interface pointer list will be used to talk to the target machine, overriding the other IP addresses present in the interface pointer. 
	 * 						 If this IP is not found then the "machine name" binding will be used. If this param is <code>null</code> then the first binding obtained from the interface pointer is used. 
	 */

//now we choose, otherwise the first one we get.

//this means, even though I asked for TCPIP something else was supplied, noticed this in win2k.				    

//can only come for the name, saving it incase nothing matches the target address

//to use the binding supplied by the user.

"99fcfec4-5260-101b-bbcb-00aa0021347a:0.0"

//first send an AlterContext to the IID of the IOxidResolver

// Now will setup syntax for IRemUnknown and the address.

//syntax = "00000143-0000-0000-c000-000000000046:0.0";

/** Instantiates a JIComServer represented by the interfacePointer param. There are cases where a COM server may hand down a
	 * reference to a different COM server(which may or may not be on the same machine) and we would like to hook in between.
	 * The <code>IJIComObject</code> interface is usable only in the context of the current JIComServer, but when the interfacePointer
	 * is of a completely different COM server, the JIObjectFactory APIs will not work. The reason is the interface pointer passed to those
	 * APIs expects to belong only to a single and same COM server (say 'A'). If by any chance, that COM server passes a reference to you
	 * of another COM server (say 'B') on a different machine, the <code>IJIComObject</code> so returned from <code>JIObjectFactory</code> APIs
	 * will result in "Method not found" Exceptions (or others) since the pointer returned via that will always place calls to 'A' instead of 'B'.
	 * Under such scenarios you must use this API. This is not a usual case and for reasons related to nature of DCOM, will be very well documented
	 * in the Developers guide of your COM server.
	 *
	 * The DCOM specs refer to this as the "middleman" case. (Section 3.3.1) 
	 * 
	 * @param session Please use a new session and not an already bounded one. The <code>JISession.createSession(JISession)</code> can be used to create a new session.
	 * @param interfacePointer reference to a different COM server pointer.
	 * @param ipAddress		 Can be <code>null</code>. Sometimes there are many adapters (virtual as well) on the Target machine to which this interface pointer belongs,
	 * 						 which may get sent as part of the interface pointer and consequently this call will fail since it is a possibility that IP is not reachable via this machine.
	 * 						 The developer can send in the valid IP and if found in the interface pointer list will be used to talk to the target machine, overriding the other IP addresses present in the interface pointer.
	 * 						 If this IP is not found then the "machine name" binding will be used. If this param is <code>null</code> then the first binding obtained from the interface pointer is used.
	 */

//this means, even though I asked for TCPIP something else was supplied, noticed this in win2k.

/**
 * 
 * Instantiates a JIComServer represented by the interfacePointer param.
 * There are cases where a COM server may hand down a reference to a
 * different COM server(which may or may not be on the same machine) and we
 * would like to hook in between. The <code>IJIComObject</code> interface is
 * usable only in the context of the current JIComServer, but when the
 * interfacePointer is of a completely different COM server, the
 * JIObjectFactory APIs will not work. The reason is the interface pointer
 * passed to those APIs expects to belong only to a single and same COM
 * server (say 'A'). If by any chance, that COM server passes a reference to
 * you of another COM server (say 'B') on a different machine, the
 * <code>IJIComObject</code> so returned from <code>JIObjectFactory</code>
 * APIs will result in "Method not found" Exceptions (or others) since the
 * pointer returned via that will always place calls to 'A' instead of 'B'.
 * Under such scenarios you must use this API. This is not a usual case and
 * for reasons related to nature of DCOM, will be very well documented in
 * the Developers guide of your COM server.
 * 
 * The DCOM specs refer to this as the "middleman" case. (Section 3.3.1)
 * 
 * 
 * 
 * @param session
 * Please use a new session and not an already bounded one. The
 * <code>JISession.createSession(JISession)</code> can be used to
 * create a new session.
 * @param interfacePointer
 * reference to a different COM server pointer.
 * @param ipAddress
 * Can be <code>null</code>. Sometimes there are many adapters
 * (virtual as well) on the Target machine to which this
 * interface pointer belongs,
 * which may get sent as part of the interface pointer and
 * consequently this call will fail since it is a possibility
 * that IP is not reachable via this machine.
 * The developer can send in the valid IP and if found in the
 * interface pointer list will be used to talk to the target
 * machine, overriding the other IP addresses present in the
 * interface pointer.
 * If this IP is not found then the "machine name" binding will
 * be used. If this param is <code>null</code> then the first
 * binding obtained from the interface pointer is used.
 */

How to use setStubmethodin org.jinterop.dcom.core.JISession

Best Java code snippets using org.jinterop.dcom.core.JISession.setStub (Showing top 6 results out of 315)

How to use
setStub
method
in
org.jinterop.dcom.core.JISession