The inter - application communication is not the only issue that the j2ee
spec defines as vendor specific...there is also the security spec. With user
security, we usually isolate the code which is vendor specific so that we
can quickly change security methods if we need to use another application
vendor.
I believe that inter - application communication is another area where the
best architectural solution is to isolate the vendor specific code. It
wouldn't be a good idea to force all of the vendors to use the same over the
wire protocol for application communication...then they would all be equally
slow! ormi (the orion over the wire protocol) is one place orion can be
faster than other vendors.
Regards,
elephantwalker
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ray Harrison
Sent: Wednesday, April 04, 2001 5:31 AM
To: Orion-Interest
Subject: RE: Does any one has a solution for the "domain was null"
message???
>From what I have seen, each app server is free to define its own specific
method for partitioning
functionality and is not hard wired into the spec. Orion, Weblogic, EA
Server, for instance, each
have their own protocol for intra/inter server communication. Jason has done
an excellent job in
describing how Orion operates (and Jason, you also cleared up an issue I was
having yesterday too
- thanks!). I am not always as careful as I should be when I read specs -
Alex, is there a section
of the specs that says that you should be able to accomplish what you want
to do from the approach
that you tried? Architecturally, it seems you have an orion server that is
acting as a web
container and an orion server that is acting as an EJB container and that
you want to use Orion's
protocols to have those two servers communicate appropriately.
Cheers
Ray
--- Jason Smith <[EMAIL PROTECTED]> wrote:
> Well, I agree that it would be nice if you could get access to servers
> outside of Orion using the "client" approach, I don't think it necessarily
> defined in the J2EE platform specs. I took a look around the J2EE 1.3
> specification, and the section J2EE.2.8 "Flexibility of Product
> Requirements" states:
> "This specification doesn't require that J2EE product be implemented by a
> single program, a single server, or even a single machine. In general,
this
> specification doesn't describe the partionining of services or functions
> between machines, servers, or processes. As long as the requirements in
> this specification are met, J2EE Product Providers can partition the
> functionality however they see fit. A J2EE product must be able to deploy
> application components that execute with the semantics described by this
> specification."
>
> In section J2EE.2.11.3 "Network Protocols" it says that "This
specification
> defines the mapping of application components to industry-standard network
> protocols. The mapping allows client access to the application components
> that have not installed J2EE product technology".
>
> Finally, in J2EE.8.2.1 "Application Assembly" subpart 3ii says
"Dependencies
> that are not linked to internal components must be handled by the Deployer
> as external dependencies that must be met by resources previously
installed
> on the platform. External resources must be linked to the resources on
the
> platform during deployment."
>
> From everything I have read, it seems that Orion isn't violating any
> specification rules, since they are allowed to partition functionality as
> they see fit. Orion does allows multiple servers to intercommunicate, but
> it is the responsibility of the application deployer to specify those
links
> (and it is specific to Orion). Since the web container is bundled as part
> of the J2EE Server, I don't think the specification requires that it has
> access to anything outside that specific server environment.
>
> I would like to hear the thoughts of others about this, and any
experiences
> they might have had with access with remote containers/servers.
>
> -jason
>
>
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/?.refer=text
