org.pentaho.platform.repository2.unified.webservices

Overview

Package

Class

Use

Tree

Deprecated

Index

Help

PREV PACKAGE NEXT PACKAGE

FRAMES NO FRAMES

Package org.pentaho.platform.repository2.unified.webservices

This package contains a variation of the IUnifiedRepository interface that has been modified to work within the restrictions imposed by various Java RPC technologies like JAX-WS and GWT.

See:
Description

Interface Summary
IUnifiedRepositoryWebService	JAX-WS-safe version of `IUnifiedRepositoryService`.
IUnifiedRepositoryWebServiceAsync

Class Summary
DataNodeDto
DataPropertyDto
DefaultUnifiedRepositoryWebService	Implementation of `IUnifiedRepositoryWebService` that delegates to an `IUnifiedRepository` instance.
IUnifiedRepositoryWebServiceCache
NodeRepositoryFileDataAdapter
NodeRepositoryFileDataDto
RepositoryFileAclAceAdapter
RepositoryFileAclAceDto
RepositoryFileAclAdapter
RepositoryFileAclDto
RepositoryFileAdapter	Converts `RepositoryFile` into JAXB-safe object and vice-versa.
RepositoryFileDto	JAXB-safe version of `RepositoryFile`.
RepositoryFileTreeAdapter	Converts `RepositoryFileTree` into JAXB-safe object and vice-versa.
RepositoryFileTreeDto
StringKeyStringValueDto
VersionSummaryAdapter
VersionSummaryDto

Package org.pentaho.platform.repository2.unified.webservices Description

This package contains a variation of the IUnifiedRepository interface that has been modified to work within the restrictions imposed by various Java RPC technologies like JAX-WS and GWT. The restrictions are:

Must supply no-arg constructors.
No interfaces--only concrete types.
No uses of the type Object or Serializable (possibly other types as well).
No method overloading.
No static inner classes.
No InputStreams or other types that are not emulated by GWT.
No arrays. (Technically they are allowed but use typed Lists instead.) https://jax-ws.dev.java.net/issues/show_bug.cgi?id=813

Java clients should never use the "safe" version of the IUnifiedRepository interface. Instead, clients should code to the IUnifiedRepository interface and use the adapter layer to convert the calls into calls on the web service client. In this way, the client code is location unaware--it can be calling code in the same JVM or a remote JVM.