OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: regrep by sun

Leanne Luger wrote:
> Hi
> Has anyone else on this list got the ebxml regrep installed and working?

Leanne et al:

We tried the Sun package on *nix
however we we abandoned installation after initial problems.  IT
seems to be a Registry only implementation, however, as you may be
aware,  XMLG previously developed such tools.

XML Global has a Beta Registry called GoXML Central which uses the ebXML
and also contains a library for CPP creation. The registry is not
dependant on any third party DB. It uses our own GOXML Native XML DB for
storage and metadata.

It is also written in Java and the libraries can be deployed in three

The first method of deployment is a standard JAR file in the classpath
of a static classloader for use as a standalone library. A developer
would use this option if he or she were interested in sending
synchronous messages to an ebXML messaging server and nothing else. The
obvious case for this method of deployment is within a client
application that does not need a listening port. The only incoming
messages that are processed are the response messages that are generated
immediately on the open HTTP connection (as in SOAP RPC). An application
of the library in this configuration is known as the "Client Scenario".

The second method of deployment is within a J2EE-compliant web
application server. The package contains a servlet and web application
that can listen for incoming messages. The servlet delegates the
messages to a Central home-object that is configured to route the
messages to the appropriate application connector or service. Details on
how to connect applications are out of scope for this chapter but are
included within the accompanying API docs. Application in this
configuration is known as the server scenario.

The last method of deployment is as a standalone server using the
Jakarta Tomcat application server running in an embedded mode. This is a
least-effort deployment mode and is suitable if are interested in
deploying a server application and do not normally run a web application
server at all. There is minimal support for this method of deployment as
it was used primarily by the development team for testing built-in
services. These include the Registry sub-system. This scenario is called
the standalone scenario.

Duane Nickull, CTO - Founder
XML Global Technologies, Inc.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC