RE: Does any one has a solution for the "domain was null" message???
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
RE: Does any one has a solution for the "domain was null" message???
Just like I can write a client that can connect to any server (after specifying proper values to new InitialContext), I should be able to do the same thing from any Java Code (with certain limitations). This should be regardless of where the Java code is running. Why should I get a NullPointerException, trying to connect from one Orion Server to another Orion Server. People have been able to connect from Orion Server to Weblogic server, just by creating a new InitialContext with proper parameters for Weblogic. I am developing a Web client application. Along with the Web client application I am providing the interfaces I need to communicate to the outside world. How can I generically connect my Web Client to a Server? If it is possible to create a new InitialContext onto a Weblogic server from Orion, why should this fail from one Orion server to another? On the other hand, I did read the spec. Chapter 18 "Support for Distribution and Interoperability" is devoted to this exact issue. This chapter places RMI-IIOP communication between two servers. While I realize that Orion's RMI-IIOP implementation is not there, I was hoping for a stop gap measure of using InitialContext. I guess, I'll give up at this point. It's clear that an Orion server acting as a client cannot talk to another Orion server acting as a EJB server using InitialContext. -AP_ -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
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
RE: Does any one has a solution for the "domain was null" message???
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
RE: Does any one has a solution for the "domain was null" message???
Earl,
I was only replying to your message where you indicate:
"I suggest you try the
ApplicationInitialContextFactory instead of
theApplicationClientInitialContextFactory in your situation."
I was
only saying that using ApplicationInitialcontextFactory will not work in my
case. There is no aspect that you do not understand. It's
quite simple. Just try to create a new InitialContext(p) where p contains
ApplicationClientInitialContextFactory. During the creation of
InitialContext you will get a NullPointerException with the message of "domain
was null".
Jason
Smith did a good job of documenting of how to connect two Orion servers together
using RMI.XML file, however, this does not seem to be J2EE compliant. I
still want to use the solution where InitialContext can be used to connect to a
different server.
For
now, we are deploying our application in the same server using the
parent="application-name" tag.
-AP_
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Earl
MarwilSent: Tuesday, April 03, 2001 8:00 AMTo:
Orion-InterestCc:
[EMAIL PROTECTED]Subject: RE: Does any one has a
solution for the "domain was null" message???If you use
the ApplicationClientContextFactory it will read
META-INF/application-client.xml which is where you can specify the
and elements... There still must be some other
aspect of your situation that I don't understand.In answer to my
own question, I finally discovered how the rmi authentication works in
conjunction with an EJBUserManager. It was not clear from the error messages.
After reading the article at orionsupport on the DataSourceUserManager,
studying the orion examples and docs and an intuitive guess, I added the
permissions to a group in the application's principals.xml,
e.g.:rmi
users(Can someone explain the permissions in
relation to the groups or point me to a reference? I'm still not sure which of
the two or whether both are required and why. It works for now...)This
group name is added in the orion-application.xml which also directs the
application to use the custom EJB user manager:...
...Now
my application client is successful in connecting to the rmi server,
authenticating a user account via the EJBUserManager and accessing my
application.At 18:37 3/30/2001 -0800, you wrote:
The problem, is that I AM connecting to ANOTHER
server from a client. It'sjust happends that the client is an
Orion. UsingApplicationInitialContextFactory attempts to read
META-INF/application.xml,but I need to specify ,
and other such entries which youcannot be put into
application.xml.-AP_-Original Message-From:
[EMAIL PROTECTED][mailto:[EMAIL PROTECTED]]On Behalf
Of Earl MarwilSent: Friday, March 30, 2001 10:21 AMTo:
Orion-InterestSubject: Re: Does any one has a solution for the "domain
was null"message???There may be a clue to this question in
the following error message that isgenerated when trying
thecom.evermind.server.ApplicationInitialContextFactory from an
applicationclient:"javax.naming.NamingException:com.evermind.server.ApplicationInitialContextFactory
should only be usedinside Orion server environments. For
clientcom.evermind.server.ApplicationClientInitialContextFactory
orcom.evermind.server.rmi.RMIInitialContextFactory should be
used"I suggest you try the ApplicationInitialContextFactory instead
of theApplicationClientInitialContextFactory in your
situation.Somewhat related, I have been trying to get an
application client working.I have succeeded in connecting to the orion
rmi server, looking up an ejb,and retrieving data. I would like to
authenticate against theEJBUserManager that is configured for our web
applications. However, itappears that the rmi authentication defaults to
XMLUserManager - i.e., Ican only authenticate for users defined in the
principals.xml file. Thiscould be related to the orion Bugzilla #374.
Can anyone provide someinsight into the RMI authentication?
Thanks.Regards,EarlAt 18:04 3/29/2001 -0800, you
wrote:>Could someone help me with this problem. When trying to
create a new>InitialContext with
factory>com.evermind.server.ApplicationClientInitialContextFactory
from inside of>OrionServer always throws a NullPointerException, with
message "domain was>null". The same code works fine from
external client.>>Has anyone fixed this problem? Has
anyone seen this problem? Is anyone>trying to deploy JSP and
RE: Does any one has a solution for the "domain was null" message???
If you use the ApplicationClientContextFactory it will read META-INF/application-client.xml which is where you can specify the and elements... There still must be some other aspect of your situation that I don't understand. In answer to my own question, I finally discovered how the rmi authentication works in conjunction with an EJBUserManager. It was not clear from the error messages. After reading the article at orionsupport on the DataSourceUserManager, studying the orion examples and docs and an intuitive guess, I added the permissions to a group in the application's principals.xml, e.g.: rmi users (Can someone explain the permissions in relation to the groups or point me to a reference? I'm still not sure which of the two or whether both are required and why. It works for now...) This group name is added in the orion-application.xml which also directs the application to use the custom EJB user manager: ... ... Now my application client is successful in connecting to the rmi server, authenticating a user account via the EJBUserManager and accessing my application. At 18:37 3/30/2001 -0800, you wrote: The problem, is that I AM connecting to ANOTHER server from a client. It's just happends that the client is an Orion. Using ApplicationInitialContextFactory attempts to read META-INF/application.xml, but I need to specify , and other such entries which you cannot be put into application.xml. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Earl Marwil Sent: Friday, March 30, 2001 10:21 AM To: Orion-Interest Subject: Re: Does any one has a solution for the "domain was null" message??? There may be a clue to this question in the following error message that is generated when trying the com.evermind.server.ApplicationInitialContextFactory from an application client: "javax.naming.NamingException: com.evermind.server.ApplicationInitialContextFactory should only be used inside Orion server environments. For client com.evermind.server.ApplicationClientInitialContextFactory or com.evermind.server.rmi.RMIInitialContextFactory should be used" I suggest you try the ApplicationInitialContextFactory instead of the ApplicationClientInitialContextFactory in your situation. Somewhat related, I have been trying to get an application client working. I have succeeded in connecting to the orion rmi server, looking up an ejb, and retrieving data. I would like to authenticate against the EJBUserManager that is configured for our web applications. However, it appears that the rmi authentication defaults to XMLUserManager - i.e., I can only authenticate for users defined in the principals.xml file. This could be related to the orion Bugzilla #374. Can anyone provide some insight into the RMI authentication? Thanks. Regards, Earl At 18:04 3/29/2001 -0800, you wrote: >Could someone help me with this problem. When trying to create a new >InitialContext with factory >com.evermind.server.ApplicationClientInitialContextFactory from inside of >OrionServer always throws a NullPointerException, with message "domain was >null". The same code works fine from external client. > >Has anyone fixed this problem? Has anyone seen this problem? Is anyone >trying to deploy JSP and EJB parts on different Orion servers, or are all >people comfortable running their models in front of the firewalls? > >Any help would be appreciated > >Thanks for your help. >-AP_ Earl Marwil SCIENTECH, Inc. 1690 International Way Idaho Falls, ID 83402 208.525.3717 Earl Marwil SCIENTECH, Inc. 1690 International Way Idaho Falls, ID 83402 208.525.3717
RE: Does any one has a solution for the "domain was null" message???
The problem, is that I AM connecting to ANOTHER server from a client. It's just happends that the client is an Orion. Using ApplicationInitialContextFactory attempts to read META-INF/application.xml, but I need to specify , and other such entries which you cannot be put into application.xml. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Earl Marwil Sent: Friday, March 30, 2001 10:21 AM To: Orion-Interest Subject: Re: Does any one has a solution for the "domain was null" message??? There may be a clue to this question in the following error message that is generated when trying the com.evermind.server.ApplicationInitialContextFactory from an application client: "javax.naming.NamingException: com.evermind.server.ApplicationInitialContextFactory should only be used inside Orion server environments. For client com.evermind.server.ApplicationClientInitialContextFactory or com.evermind.server.rmi.RMIInitialContextFactory should be used" I suggest you try the ApplicationInitialContextFactory instead of the ApplicationClientInitialContextFactory in your situation. Somewhat related, I have been trying to get an application client working. I have succeeded in connecting to the orion rmi server, looking up an ejb, and retrieving data. I would like to authenticate against the EJBUserManager that is configured for our web applications. However, it appears that the rmi authentication defaults to XMLUserManager - i.e., I can only authenticate for users defined in the principals.xml file. This could be related to the orion Bugzilla #374. Can anyone provide some insight into the RMI authentication? Thanks. Regards, Earl At 18:04 3/29/2001 -0800, you wrote: >Could someone help me with this problem. When trying to create a new >InitialContext with factory >com.evermind.server.ApplicationClientInitialContextFactory from inside of >OrionServer always throws a NullPointerException, with message "domain was >null". The same code works fine from external client. > >Has anyone fixed this problem? Has anyone seen this problem? Is anyone >trying to deploy JSP and EJB parts on different Orion servers, or are all >people comfortable running their models in front of the firewalls? > >Any help would be appreciated > >Thanks for your help. >-AP_ Earl Marwil SCIENTECH, Inc. 1690 International Way Idaho Falls, ID 83402 208.525.3717
Re: Does any one has a solution for the "domain was null" message???
There may be a clue to this question in the following error message that is generated when trying the com.evermind.server.ApplicationInitialContextFactory from an application client: "javax.naming.NamingException: com.evermind.server.ApplicationInitialContextFactory should only be used inside Orion server environments. For client com.evermind.server.ApplicationClientInitialContextFactory or com.evermind.server.rmi.RMIInitialContextFactory should be used" I suggest you try the ApplicationInitialContextFactory instead of the ApplicationClientInitialContextFactory in your situation. Somewhat related, I have been trying to get an application client working. I have succeeded in connecting to the orion rmi server, looking up an ejb, and retrieving data. I would like to authenticate against the EJBUserManager that is configured for our web applications. However, it appears that the rmi authentication defaults to XMLUserManager - i.e., I can only authenticate for users defined in the principals.xml file. This could be related to the orion Bugzilla #374. Can anyone provide some insight into the RMI authentication? Thanks. Regards, Earl At 18:04 3/29/2001 -0800, you wrote: >Could someone help me with this problem. When trying to create a new >InitialContext with factory >com.evermind.server.ApplicationClientInitialContextFactory from inside of >OrionServer always throws a NullPointerException, with message "domain was >null". The same code works fine from external client. > >Has anyone fixed this problem? Has anyone seen this problem? Is anyone >trying to deploy JSP and EJB parts on different Orion servers, or are all >people comfortable running their models in front of the firewalls? > >Any help would be appreciated > >Thanks for your help. >-AP_ Earl Marwil SCIENTECH, Inc. 1690 International Way Idaho Falls, ID 83402 208.525.3717
RE: Does any one has a solution for the "domain was null" message???
Hmmm, but in this case, my server is acting as a client to another server. The ApplicationInitialContextFactory will look for the application.xml instead of client-application.xml. I need to specify the bindings to the other services, not the packages in the application. My server is acting as a client to another server, so I think the ApplicationClientInitialContextFactory should be the one to use. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Endres Sent: Thursday, March 29, 2001 9:25 PM To: Orion-Interest Cc: Alex Paransky Subject: Re: Does any one has a solution for the "domain was null" message??? Inside the container, you are supposed to use ApplicationInitialContextFactory instead of ApplicationClientInitialContextFactory. Have you tried that? > Could someone help me with this problem. When trying to create a new > InitialContext with factory > com.evermind.server.ApplicationClientInitialContextFactory from inside of > OrionServer always throws a NullPointerException, with message "domain was > null". The same code works fine from external client. > > Has anyone fixed this problem? Has anyone seen this problem? Is anyone > trying to deploy JSP and EJB parts on different Orion servers, or are all > people comfortable running their models in front of the firewalls? > > Any help would be appreciated > > Thanks for your help. > -AP_ > >
Re: Does any one has a solution for the "domain was null" message???
Inside the container, you are supposed to use ApplicationInitialContextFactory instead of ApplicationClientInitialContextFactory. Have you tried that? > Could someone help me with this problem. When trying to create a new > InitialContext with factory > com.evermind.server.ApplicationClientInitialContextFactory from inside of > OrionServer always throws a NullPointerException, with message "domain was > null". The same code works fine from external client. > > Has anyone fixed this problem? Has anyone seen this problem? Is anyone > trying to deploy JSP and EJB parts on different Orion servers, or are all > people comfortable running their models in front of the firewalls? > > Any help would be appreciated > > Thanks for your help. > -AP_ > >
