Traction Problem In Session Facade Disign

Hi
I am using session facade design pattern.
I have Action class calling session facade method "getData" . This method calls "findByPrimaryKey" method in BMP.
Method "getData" has transaction attribute as "RequiresNew" and "findByPrimaryKey" has "Required".
This combination does not assign identity to BMP hence I can not use setter getter method for retriving data(throws nullpointer exception when getter method accessed) I have made sure that I am accessing table and getting data in to BMP but as BMP is not ablle to hoild any identity its not allowing me to use BMP's getter method in session facade.
I have Used Same transaction attribute for create method called by "addNew" method of session facade bean.
Transaction method for "addNew" is "RequiresNew" and for "create" is "Required".
It works fine and gives identity toBMP hense I can use Setter getter method defined in BMP bean.
How can I avoid this and get BMP an identity?
Thanking in Advance,
Chintan.

Similar Messages

Transaction Problem in Session Facade Design Pattern

Hi
Well Sorry for giving wrang title to the topic, coz of which I have not received and reply.
I am using session facade design pattern.
I have Action class calling session facade method "getData" . This method calls "findByPrimaryKey" method in BMP.
Method "getData" has transaction attribute as "RequiresNew" and "findByPrimaryKey" has "Required".
This combination does not assign identity to BMP hence I can not use setter getter method for retriving data(throws nullpointer exception when getter method accessed) I have made sure that I am accessing table and getting data in to BMP but as BMP is not ablle to hoild any identity its not allowing me to use BMP's getter method in session facade.
I have Used Same transaction attribute for create method called by "addNew" method of session facade bean.
Transaction method for "addNew" is "RequiresNew" and for "create" is "Required".
It works fine and gives identity toBMP hense I can use Setter getter method defined in BMP bean.
How can I avoid this and get BMP an identity?
Thanking in Advance,
Chintan.

Sorry, how is this related to JSF?
There's an OO/patterns forum out. Consider reposting the question over there with formatted code.

JNDI Naming Problem accessing Session Bean from Message Driven Bean

Hi,
     I am facing a very strange problem in JNDI look up accessing a Session Bean from a Message Driven Bean. I have a session fa�ade bean(Remote Bean) which is being called from Struts Action class getting the home reference from the ServiceLocator (I have implemented ServiceLocator pattern to obtain JNDI reference for all EJBs). When I am calling the session fa�ade EJB from the Struts Action class everything is working fine.
     But when I am trying to call the same EJB from my Message Driven Bean, I am getting a JNDI exception (NameNotFoundException - No Object bound to name �java:comp/env/ejb/EJBJNDIName�). I am trying to get the remote reference from the same ServiceLocator which is successfully providing me a reference while calling from the struts action class. But the same ServiceLocator is not able to provide me a reference while calling from the Message Driven Bean. If I use the JNDI name directly like �EJBJNDIName� in the lookup it is working fine. The lookup for the name is working fine and I am able to call the Session Fa�ade bean with that reference.
     I am really not sure what exactly the problem is. If I have any problem in the ServiceLocator, it should have given me the same error while calling from Struts Action class. But it is working fine with the full name �java:comp/env/ejb/EJBJNDIName� calling from the struts action class. I am not sure whether Message Driven Bean has something to do with it. Why I am not able to get a reference of the EJB with the full name? Please Help.
Thanks
Amit

Hi Bhagya,
Thanks for your response. I think from EJB container we can call Local EJBs with the full JNDI name. The session facade bean which is being called is a remote bean. From the session facade bean I am calling a local stateless session bean for database access. I am getting the reference of the local EJB from my session facade bean with full JNDI name "java:comp/env/ejb/EJBJNDIName". It is working fine with out any problem. My servicelocator is able to provide me the reference of the local EJB from the session facade remote bean with Full JNDI name. I am only having this problem calling from the MDB. I am really not sure whether what is causing it?
Thanks
Amit

Calling session facade methods from my code

My application consists of two projects: Interface and Model. Model, of course, is used for access to a database using TopLink with POJOs and session facade bean...Pretty much like thing done int tutorial. While, naturally, Interface project are the web pages etc. Standard web application.
Now, there is no problem with using data controls from session facade bean (drag and drop to the form for making tables, lists, forms etc.), that works fine.
What I need is to use methods from my session facade bean in my code. For example, I have made a TopLink query findAllLabels. It is exposed in session facade bean UtilBean so in the bean the code is
List<Labels> findAllLabels(){
So In some part of my code (for instance, in some backing bean) I would like to call this query. I have done this:
UtilBean util=new UtilBean();
List<Labels> labels=util.findAllLabels();
And this works fine, for now. But, I'm wondering, is this the correct solution, and is there some more ellegant and correct way to do this? Is it correct to instantiate a session facade bean in this way?

The more appropriate and correct solution is as follows:
Drag the toplink named query(without expanding it) from the data control pallete into your h:form.
You will get an option to create a ADF Command Button or ADF Command Link.
Select ADF Command Button.
Double click the generated button.
It enables you to create a default action listener for the button. Ensure that the Check box labelled
"Generate ADF Binding Code" is checked.
Click OK.
This should create a method in your backing bean
as
public String commandButton1_action(....)
/*Generated Code.
Insert your code here
This should solve your problem
Bye.

Business Delegate and Session Facade Pattern

Hi!
The only way to use the Session Facade Pattern, is if I use EJB for Persistence.
Is valid to do this?:
I use Ejb for simple update, insert querys. From my business delegate I call the Session Facade Layer, and from this I invoque Entyties for persistence.
But if I have complex querys, is correct to make PL SQL Procedures and do the following:
From my business delegate I call to the Dao layer, and from this via JDBC I call the Procedure.
Please explain me the best form to do this, having complex querys for reporting and simple querys for inserts/update.
Is valid to combine the use of CMP (for simple persistence cases), BMP (for complex persistence cases), and JDBC for complex select querys with multiple result rows.
Thanks!!

It depends on your design goals. One of the forces driving the use of patterns is the desire to tier an application and abstract the internals of each tier away from the other tiers. One (normal) benefit of this methodology is that the application should become more portable. Now, if you are using PL/SQL, BMP and CMP, you are mixing and matching portable versus proprietary. This is okay. But you should abstract away whether you are using PL/SQL, BMP or CMP from the business layer (or domain model). Ideally, you could completely swap database technologies (say from relational to object) and only have to re-write your integration tier (your DAO's).
Session facade is simply a glorified Facade pattern. It abstracts the lower-level details of what you are persisting and instead forces you to think in terms of objects. You can use a facade without even remotely touching EJB's. It just so happens that, historically, EJB containers made a mess out of scalability when it came to entity beans. The "session" facade refers to a facade pattern implemented in session beans (that have fewer scalability problems) communicating with the entity beans which do have scalability problems.
So... to make a long story short, use whatever persistence mechanism you desire. Remember that you should be able to completely switch your persistent store from one type or another and simply re-write your DAO's (or CMP deployment descriptors). Using a facade pattern can help towards this end, but don't make it a straightjacket.
- Saish
"My karma ran over your dogma." - Anon

Business Delegate, Session Facade or both?

Hi,
I'm having some problems with figuring out the point of using both Business Delegate (BD) and Session Facade (SF). As far as I can see, you often have a 1-1 mapping between the BD and SF, so why not use the SF directly?
Here's my scenario. I have a web application that uses WebWork for presentation and pageflow, a session facade implemented using an ejb, which aggregates calls to the businness objects into "business rule"-methods and business objects implemented using plain java objects. Is there really any need to have a business delegate here? I might as well use the session facade directly from the webwork actions? Or..?
Any suggestions? Am I far off? ;-)

As far as I can see, you often have a 1-1 mapping between the BD and SF, so why not use the SFYou can have one Business Delegate encapsulate all of the business methods that are exposed by one or more Session Facades. The benefit here is that you protect the web component from any details of the business tier. e.g. your business tier has five session facades and the web tier has a single Business Delegate. The BD can be extended to call web services as well.
Here's my scenario. I have a web application that uses
WebWork for presentation and pageflow, a session
facade implemented using an ejb, which aggregates
calls to the businness objects into "business
rule"-methods and business objects implemented using
plain java objects. Say you eliminate the EJB implementation. What effect will this have on the web tier objects? The Business Delegate will enable you to easily replace the business implementation with little impact on the web components.

Session facade lookup fails occasionally

Hey all,
Since a few weeks we're having some problems with our weblogic server. We're running a number of ears and wars which communicate with each other using a BusinessDelegate and Session Facade. The InitialContext lookup which is done, suddenly seems to fail at random occasions (today I counted around 20 failed lookups of the facade of one application and > 800 succesful transactions.
is there anyone who has seen this behaviour before? I'm kindof running out of ideas. Maybe something with the garbage collector?
Caused by: javax.naming.NameNotFoundException: Unable
to resolve 'XXXFacadeBean' Resolved ; remaining
name 'XXXFacadeBean'Regards,
Rein

Hey all,
Since a few weeks we're having some problems with our weblogic server. We're running a number of ears and wars which communicate with each other using a BusinessDelegate and Session Facade. The InitialContext lookup which is done, suddenly seems to fail at random occasions (today I counted around 20 failed lookups of the facade of one application and > 800 succesful transactions.
is there anyone who has seen this behaviour before? I'm kindof running out of ideas. Maybe something with the garbage collector?
Caused by: javax.naming.NameNotFoundException: Unable
to resolve 'XXXFacadeBean' Resolved ; remaining
name 'XXXFacadeBean'Regards,
Rein

Value-list handler, value-list iterator and session-facade strategy

Hello all,
Further to an earlier post, I rewrote my post trying to me more accurate in my question.
Here is my problem:
I am trying to implement the value-list handler design pattern using the session facade strategy. In the pattern as it is described here
(http://java.sun.com/blueprints/corej2eepatterns/Patterns/ValueListHandler.html) the client accesses the value-list handler AND the iterator directly.
As I chose the session-facade strategy having my value-list handler as a stateful session ejb, I don't know how the client is going to access the iterator. I see only one option: Having the client access the iterator through the ejb value-list handler. This requires adding new methods to the ejb.
Is this the correct way of doing it? Is there another way of doing this?
Thanks in advance,
Julien Martin.

u can use project list handler as ur session facade.
regarding ur second question ..session facade and value list handler session bean which is also a session facade( but there is difference between first and second) so u can use session facade and value listhandler

How to combine Session Facade and Transfer object?

Hello All!
I'm working on an enterprise application. Presentation layer is a stand alone client, business logic is build on the Glassfish v2.1 and MySQL is used as a database. The client is connection to the GlassFishj server remotely using EJBs.
I have problems with business logic architecture.
Here is the brief description of backend application architecture design:
1. Session Facade pattern is used to simplify the client and application server interface and to provide application layers between backend (http://java.sun.com/blueprints/corej2eepatterns/Patterns/SessionFacade.html).
2.Transfer Object pattern to define update transfer objects strategy in order to decrease network overhead during client and application server interactions and to provide version control for objects. Transfer objects are designed as simple java business serializable objects. (http://java.sun.com/blueprints/corej2eepatterns/Patterns/TransferObject.html)
3. Originally the backend application consisted of three modules: users, storage and orders, but at the end I have decided to divide my application into the following parts - assortments, map, menu, orders, transactions, users.
4. All MySQL database transactions are via JDBC using procedures. No use of entity beans.
Questions:
1. I have some doubts about using Session Facade and Transfer object patterns at the same time. At first I'd mike to cite the definitions of the patters from the SUN official web site.
* Use a session bean as a facade to encapsulate the complexity of interactions between the business objects participating in a workflow. The Session Facade manages the business objects, and provides a uniform coarse-grained service access layer to clients.
* Use a Transfer Object to encapsulate the business data. A single method call is used to send and retrieve the Transfer Object. When the client requests the enterprise bean for the business data, the enterprise bean can construct the Transfer Object, populate it with its attribute values, and pass it by value to the client.
* So, if I use Transfer Object along with Session Facade, it makes some difficulties with object version control, because I 2 or
3 transfer objects controls with the 1 bean class. The best option for Transfer object Pattern is that each transfer object should have its own bean class to provide ability of object's version control. In the case it can bring the network overhead because of frequent remote calls caused by the large number of the bean classes.
* So, should I use the both patterns? If yes, how to manage the interaction the patterns. If no, which one to use.
2. E.g. I have a huge list of the Order objects and each Order object consists of other complicated objects. So, would I have trouble to transfer that list over network? If yes, how to manage it.
Thank you!
Astghik

Astghik wrote:
Hello All!
I'm working on an enterprise application. Presentation layer is a stand alone client, business logic is build on the Glassfish v2.1 and MySQL is used as a database. The client is connection to the GlassFishj server remotely using EJBs.
I have problems with business logic architecture.
Here is the brief description of backend application architecture design:
1. Session Facade pattern is used to simplify the client and application server interface and to provide application layers between backend (http://java.sun.com/blueprints/corej2eepatterns/Patterns/SessionFacade.html).
I would simply recommend establishing a service tier. Your services should be stateless. You can go the extra mile and have a session facade, but in the majority of cases, coding to an interface for your service accomplishes the same goals.
2.Transfer Object pattern to define update transfer objects strategy in order to decrease network overhead during client and application server interactions and to provide version control for objects. Transfer objects are designed as simple java business serializable objects. (http://java.sun.com/blueprints/corej2eepatterns/Patterns/TransferObject.html)
The idea of the transfer object is very similar to the Command pattern. I think if you investigate that pattern, it will be more obvious. The transfer object reduces network latency by consolidating all the parameters into an object, ideally, this also consolidates multiple method calls. If you combine a transfer object (or command object) with a service tier, you get the best of both worlds. The service can delegate calls to helper objects (or other services or components) using the data in the transfer / command object.
3. Originally the backend application consisted of three modules: users, storage and orders, but at the end I have decided to divide my application into the following parts - assortments, map, menu, orders, transactions, users.
The is your domain. It will vary from application to application. The principles above are more general (e.g., patterns and architectural tiers) and should apply to most domains. However, your actual use case may require something different.
4. All MySQL database transactions are via JDBC using procedures. No use of entity beans.
Consider using something like iBatis or Spring's JDBC templating to make your life easier with JDBC.
Questions:
1. I have some doubts about using Session Facade and Transfer object patterns at the same time. At first I'd mike to cite the definitions of the patters from the SUN official web site.
* Use a session bean as a facade to encapsulate the complexity of interactions between the business objects participating in a workflow. The Session Facade manages the business objects, and provides a uniform coarse-grained service access layer to clients.
* Use a Transfer Object to encapsulate the business data. A single method call is used to send and retrieve the Transfer Object. When the client requests the enterprise bean for the business data, the enterprise bean can construct the Transfer Object, populate it with its attribute values, and pass it by value to the client.
* So, if I use Transfer Object along with Session Facade, it makes some difficulties with object version control, because I 2 or
3 transfer objects controls with the 1 bean class. The best option for Transfer object Pattern is that each transfer object should have its own bean class to provide ability of object's version control. In the case it can bring the network overhead because of frequent remote calls caused by the large number of the bean classes.
* So, should I use the both patterns? If yes, how to manage the interaction the patterns. If no, which one to use.
Versioning is a separate issue. Generally, the more coarsely grained your transfer / command object is, the more changes are likely to impact dependent objects.
Your command or transfer object does not have to be a vanilla JavaBean, where you are basically creating a bean that has data from other objects. You can simply use your command / transfer object to encapsulate already existing domain objects. I see no need to map to a JavaBean with what you have described.
Generally, a method signature should be understandable. This means that many times it is better to pass the method, say, two coarsely grained objects than a signature with a dozen primitives. There are no hard and fast rules here. If you find a method signature getting large, consider a transfer / command object. If you want one service to delegate calls to a number of other services, you can also create a transfer / command object to furnish the controlling service with the data it needs to invoke the dependent services.
2. E.g. I have a huge list of the Order objects and each Order object consists of other complicated objects. So, would I have trouble to transfer that list over network? If yes, how to manage it.
This is a large, open-ended question. If you are going to display it to a user on a screen, I do not see how you avoid a network transfer with the data. The general answer is to not pass the data itself but rather a token (such as a primary key, or a primary key and a start and stop range such as you see on a Google search result). You do want to limit the data over the network, but this comes at a cost. Usually, the database will receive additional load. Once that becomes unacceptable, you might start putting things into session. Then you worry about memory concerns, etc. There is no silver bullet to the problem. It depends on what issues you are trying to address and what trade-offs are acceptable in your environment.
Thank you!
AstghikBest of luck.
- Saish

What is session facade

what is session facade and what is its use in session beans

SessionFacade shows how to partition business logic in the system to help minimize dependencies between client and server, while forcing use cases to execute in one network call and in one transaction. It avoids inefficient remote client access of Entity Beans by wrapping them with a Session Bean.
The Session Fa�ade design pattern is useful in situations where client objects need to interact with a set of EJBs to perform tasks in a workflow. Take the case of an on-line trading system where customers submit orders to buy and sell stocks, the orders are verified and executed, and results are returned. Here the client need to make numerous remote calls to get the work done.
A session fa�ade solves such problems by presenting client objects with a unified interface to the underlying EJBs. Client objects interact only with the fa�ade, which resides on the server and invokes the appropriate EJB methods. As a result, dependencies and communication between clients and EJBs is reduced.

EJBs only for session facade?

Hi all,
With EJB 2.1 many were saying that it is good to place POJOs behind a session facade of ejbs for a distributed application.
This will allow a developer to test his business logic outside the container.
But with EJB 3.0, all ejbs are pojos, so can i use ejbs for all my business logic?
Is it advisable?
Will this have any performance problem?
Kindly suggest.

Hi,
Thanks for your reply.
I have a distributed application with numerous web clients as well as a few multithreaded application clients accessing the business logic layer.
Definitely there will be a huge load especially if the number of clients increase.
So there will be a lot of distributed transactions.
I have no doubt whether i should use ejbs or not.
I must because the business logic layer must support remote access.
Considering this scenario, should i use ejbs beyond the session facade layer?
I understand that by using ejbs only in the session facade layer is an adavantage as that will not tie my business logic to a framework.
But considering the scope of the application, kindly provide your suggestions.
Thanks in advance,
James.

Session Facade + DTO

Hi.
I am using session facade & also created DTO of Entity. can any body tell me what are the advantages of using the DTO's . what are the problems that I get by accessing the entity beans directly. Please can any body send the sample code of using the Session facade & DTO design petterns with an explanation.
Itz urgent.
Rakesh

For design patterns take a look at http://www.sun.com/blueprints/and browse http://www.theserverside.com
IMHO The biggest problem with DTOs is you end up with parallel class hierachies, which are a maintenance headache. Another problem is issues around stale data.
The problem with not using a DTO for entity beans is that you end up making multiple remote calls to the bean. e.g.
bean.setFirstName("john");
bean.setLastName("smith");
bean.setPostCode("AB123 123");
instead of on method call
bean.setCustomer(customerDTO)

Problem with sessions in Kate Editor

Hey guys!
I'm using Kate Editor to code and i'm having problems with sessions. If kate is open and I logout KDE, when I come back to KDE all my customizations in Kate's session (activated plugins, font size, etc) are lost.
If I manually close Kate before logout from KDE, all the customizations are kept when a manually start Kate. I tried a lot of workarounds, but none worked.
Is this a bug? Someone else with this issue?
Thanks in advance!

The Warning errors are simply because you don't have the tablespaces, users, and roles defined in your application system under the DB Admin tab. Unless it is important to you to capture the physical implementation of your tables exactly as well as the table definitions, you can safely ignore these. If the physical implementation IS important to you, then you need to create these tablespaces, roles and users under the database that you created under the DB Admin tab before you start the capture.
The Error is because in the set of objects you are capturing there is a foreign key that references the table named "PLEASANT". This table must be among the objects that you are capturing, or must already be in a Table Definition in your application system in the repository.

Problem with Sessions in JSP

Hi,
I am working on a JSP based website, where I am facing problem with sessions. The user is asked to login by providing her id and password. If found correct, a bean is created and populated with all her details and placed in session scope. I plan to use the information stored in the bean on other related pages until she logs out.
<jsp:useBean id="validUser" scope="session" class="UserBean" >
<c:set target="${validUser}" property="userId" value="${fn:trim(dbValues.UserId)}" />
<c:set target="${validUser}" property="userName" value="${fn:trim(dbValues.UserName)}" />
</jsp:useBean>
<c:redirect url="userHome.jsp" /> The user is presented her homepage - 'userHome.jsp', where she can find various links, like 'Update Profile', 'Pay Registration Fees', 'Book Room' etc. The information stored in the bean is available on 'userHome.jsp'page.
<A HREF='userHome.jsp'>Home</A>
<A HREF='editPersonal.jsp'>Update Profile</A>
<A HREF='registrationFee.jsp'>Pay Registration Fees</A>
<A HREF='bookRoom.jsp'>Book Room</A>
<A HREF='logout.jsp'>Logout</A> The problems are:
1. Whenever user clicks on any of the above mentioned links and moves to any page, the bean comes out as null.
<%-- Verify that the user is logged in --%>
<c:if test="${validUser == null}">
<jsp:forward page="loginForm.jsp">
<jsp:param name="origURL" value="${pageContext.request.requestURL}" />
<jsp:param name="errorMsg" value="You must be logged in to access this site." />
</jsp:forward>
</c:if> 2. The URL shows an additional jsessionid, which my client doesn't want to see.
3. On every click on any link, the value of this jsessionid changes.
What I presume, when I am clicking on different links, my session changes, and so I am seeing a different jsessionid. And since session is changing, therefore the bean is not available in a different session.
All this works fine with localhost, problem comes into picture, when I upload my pages to the server.
Puzzled, can anyone help, where am I going wrong? Let me add here, I am new to JSP and hence don't have much resources with me.

There are several ways sessions can be exchanged between the browser and the server in a j2ee web application.
1. The default is through cookies. However when the client does not accept cookies, the server appends the session id to the url.
2. Some servers also facilitate session information exchange using session id in the url even if the client does accept cookies. This is usually ahieved through a setting in some server configuration file.
You will have to find out why the server in your application is appending the session id to the url.
Whatever be the case, the server should be able to look up the session from the incoming request (be it from the session id in the url or a session cookie).
When session information is exchanged through the JSESSIONID in the url, you should ensure that each and every url that goes to the server has this input parameter. To do that all links and form post urls in your servlet/jsp should be treated with a call to encodeURL().
For example, in a jsp
   <a href = "<%=response.encodeURL("/nextJsp.jsp")%>">Click here </a>
or
   <form action = "<%=response.encodeURL("/nextJsp.jsp")%>">
   </form>etc.
ram.

Problem with Sessions, Servlets, Netscape and Solaris

We are experiencing a problem that is confounding and frustrating us (I have
          a felling that it is something exremely minor that we are overlooking).
          Here goes:
          Context:
          The problem only occurs when using a netscape browser against weblogic
          4.51running on our Solaris 7 box (Everything works fine through IE, and
          through both browsers against our development machines which are on NT)
          Problem:
          We have a bunch of JSP pages and servlets that are used togehter throughout
          our site. They both manage session information for the user. What is
          happening is that there is no problem maintaining session information among
          all the JSP pages, but when we hit a servlet that we use to stream graphs
          back to the browser, it gets the session but it has no contents all of a
          sudden. What seems to be even more strange is that the session is not
          tagged as new (by checking isNew()), it is just empty of the contents that
          were placed it by the JSP pages. Again, this is only occurring from
          Netscape browsers against our Solaris server.
          If anyone can provide any help it would be greatly appreciated. I can
          provide more details if need be.
          Jeremy


There is a property in the weblogic.properties file that lets you set
          the cookie name. If this isn't set, the port will be appended as part of
          the name. I've had a similar problem switching between http and https
          and losing sessions.
          Carles
          Jeremy wrote:
          >
          > in the link tothe servlet the URL had a :80 in it. This was because the url
          > was generated by a JSP page so that when it was moved from server to server
          > and port to port the code wouldn't have to be changed. Unfortuneately,
          > Netscape sucks and takes this to mean that x.x.x.x and x.x.x.x:80 are
          > different and won't acknowledge the cookie from the JSP pages (x.x.x.x) to
          > the servlet (x.x.x.x:80). Thanks fpr your help.
          >
          > Jeremy <[email protected]> wrote in message
          > news:[email protected]...
          > > my mistake, it appears to always happen on port 80 regardless of the
          > server
          > > it is on.
          > >
          > > Jeff Martin <[email protected]> wrote in message
          > > news:[email protected]...
          > > > It really sounds like your servlet is making a new session, even though
          > > > isNew() doesn't say so. What you might try to do is use session.getId()
          > > > to print out the session ID from your jsp pages as well as your servlets
          > > > to determine if it really is a new session.
          > > >
          > > > Do your servlets and JSPs both use the same scheme (http or https) or
          > > > cookie.setSecure()? Do your cookies use domains or paths in either
          > > > servlets or jsps (cookies can be restricted to certain subdirectories
          > > > which might be different between jsps and servlets)? Are you testing
          > > > through a proxy or firewall, or does either browser have different proxy
          > > > settings than the others?
          > > >
          > > > Jeff
          > > >
          > > > Jeremy wrote:
          > > > >
          > > > > We are experiencing a problem that is confounding and frustrating us
          > (I
          > > have
          > > > > a felling that it is something exremely minor that we are
          > overlooking).
          > > > > Here goes:
          > > > >
          > > > > Context:
          > > > > The problem only occurs when using a netscape browser against weblogic
          > > > > 4.51running on our Solaris 7 box (Everything works fine through IE,
          > and
          > > > > through both browsers against our development machines which are on
          > NT)
          > > > >
          > > > > Problem:
          > > > > We have a bunch of JSP pages and servlets that are used togehter
          > > throughout
          > > > > our site. They both manage session information for the user. What is
          > > > > happening is that there is no problem maintaining session information
          > > among
          > > > > all the JSP pages, but when we hit a servlet that we use to stream
          > > graphs
          > > > > back to the browser, it gets the session but it has no contents all of
          > a
          > > > > sudden. What seems to be even more strange is that the session is not
          > > > > tagged as new (by checking isNew()), it is just empty of the contents
          > > that
          > > > > were placed it by the JSP pages. Again, this is only occurring from
          > > > > Netscape browsers against our Solaris server.
          > > > >
          > > > > If anyone can provide any help it would be greatly appreciated. I can
          > > > > provide more details if need be.
          > > > >
          > > > > Jeremy
          > >
          > >

Traction Problem In Session Facade Disign

Similar Messages

Maybe you are looking for