Roy kachouh

+ Follow
since Jan 10, 2003
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Roy kachouh

Ok guys, I have been pulling my hair out on this one. Just a quick prelude to the configuration of my app:

2 WSAD workspaces open.
Each workspace has it's own server configuration. So there are a total of 2 servers, let's just call them server1 and server2.

Ok now the problem:
I have created a new EJB service that allows for applications to report on the status of a process. Currently, this service is running in server1 of workspace1. There is an application running in workspace2 on server2, that needs to make use of the status service remotely. In other words, the application in server2 is acting as a client for the service provided in server1.

I am having trouble locating the service in the JNDI namespace. When I run the dumpnamespace utility, I can see that the service is bound to the namespace. I am explicitly specifying the ORB port of server1 when I construct my InitialContext. To no avail...

Below is my initial context code:

Properties props = new Properties();

//TODO externalize the URL!!!
String url = "corbaloc:iiop:localhost2:2809";
props.put(Context.PROVIDER_URL, url);

InitialContext ctx = new InitialContext(props);
NamingEnumeration ne = ctx.listBindings("thisNode/node/servers/server1/ejb/xxx/xxx/xx/xxxx");

Object obj =;
return ctx;

It seems that WSAD is ignoring the port, because the only resouces I see when I traverse the namespace are the ones local to the workspace. I am pretty sure that I would be able to see the service bound when I move the app to the WAS environment, because of the federated namepsace. However, I want to be able to test locally. Is this a limitation of WSAD or am I missing some configuration?? Anyhelp, would be greatly appreciated.


If you are talking about a duplicate class within the same EAR, I just verified I do not have duplicate classes within the SAME EAR.

However, I can assure you that I have duplicate classes across EAR files.

This should not give me a problem though right?
Hello, I am in the process of developing a J2EE app for one of my clients and I have been stuck with the same type problems, which I think are related to J2EE classloading. First, I will give an overview of the app.

There are three components that make up my app. 1st I have created an application (EAR 1) specific to the system user interface. This ear includes one web module and one EJB module that contains business logic specific to activites within the user interface. 2nd I have created another application (EAR2) that only contains one ejb module. This EJB module contains generic business logic and i forsee it being utilized by multiple different systems and clients. Finally, I have created a commons jar project, that basically contains all common value objects, exceptions, utilities etc. This commons jar file is being reference as a project utility jar within EAR1 and EAR2.

Well, hopefully you haven't fell asleep yet, because here are my specific questions. Inside my commons jar, I have a user heirarchy; lets just say I have a Parent User and a child user. Now, within my common EJB jar, I have a method that returns the Parent User. A session facade that resides in the UserInterface application makes a call to the method, and the method completes sucessfully and returns the Parent User object. However, when the facade attemps to cast the class to the child user, or even when I try to do it within the WSAD Universal test client, I keep getting a ClassCastException.

1). Is this because my classloader policy is set to Application; therefore, the classes are loaded in different namespaces? I even noticed that when I do an 'instance of' the check returns false, even though the returned object is definitly an instance of.

2). Does this have something to do with my build paths and references? I don't think so, because I do not get compile time errors or NoClassDefFound errors.

3). With any solution, will the app run into problems if the class loading policy is changed on the server?

How do I solve this problem? Any help will be greatly appreciated. I will exchange more info if needed.

How can I ensure that when a user opens up a new browser window, my servlet will create a new corresponding HttpSession.
Thanks in advance.
18 years ago
Hello...I just got back from a heated design review for a new application that my team is creating using Websphere. My team is fairly new using the J2EE architecture. What I was hoping for was that some experienced J2EE developers will be able to provide me with information as to what is a larger performace hit...having a Message Driven bean call individual LOCAL interface (say 3) sequentially, or having the MDB call a new() for each request on 3 helper classes. Any ideas/info/benchmarks would be greatly appeciated.
[ January 10, 2003: Message edited by: roy ]