Mon Mayor

The wl-proxy plugin is sending the post multple times to the server and the web server error logs contain protocol error for the multiple times it sent. The error also complains about malformed url and a backend exception.
Thanks
MM

The weblogic 6.1 server is receiving multiple form posts from iPlanet for a single form click. I don't know if this happens because of cookies.
If anyone has faced this please provide solution.
Thanks
MM

try &

Your problem is that you are calling findByPrimaryKey on a Session bean.

Good point. I was actually thinking about the same thing. I wrote a jndi client that lists out all the objects listed in a server and I did not find the datasources. So the datasources are not stored as objects. I wonder what is happening inside. My guess is that even though there is a jndi name for the datasource it is not a remote object and there is only a local reference to the instance. It is just a non corba, non rmi interface and hence cannot be accessed remotely as such.

you have to use security constraints in the web.xml file.

I agree that for smaller projects things can easily be worked with scratches of paper and some thinking. But if you are working on a medium sized project developing frameworks then UML really helps in clarifying all the chaotic expressions in the mind and can be thrown away to a corner. However in enterprise level integration it is extremely useful in churning out interfaces for service level agreements.

Use Stateful Session beans
1. for sharing session across multiple applications
2. for maintaining transactional state
3. for application clients

Set action to an intermediate page and set the attributes in session and redirect to j_security_check in there.
Hope this helps.

I agree with all that is said here. However there are couple of possibilities by mixing and matching connection and connectionless layers.
I think there are lot of articles and guidelines in selecting the match according to application criteria. So coming from that angle http is a connecionless layer built on top of a connection oriented layer with the notion of servicing many clients. Similary there could be connection oriented layer somehow maintaining connection information over connectionless layer.
So categorizing a session level layer as connection or connectionless just based on the transport layer may not be right.
I think I have added some more confusion and the question that is http connection oriented or connectionless still remains ambiguous.

True JMS confuses me all the time and I have to go back to refer the specs every now and then.
This is what I understand:
JMS is inherently asynchronous meaning there is no dependency between sending and receiving a message.
However the consumer can exhibit synchronous behavior like it can block untill it receives a message or asynchronous through the onMessage method.
The only way a sender can exhibit synchronous is using temporary destinations.
Hope this helps.
-MM(SCEA)

Looks like the java orb class is used instead of Visibroker Orb. Hope this helps.

I guess that the first load is the actual loading of the data into the bean. Since the bean already exists EjbActivate is used to move the bean from the pool to ready state. EjbLoad always follows EjbActivate like ejbstore is called before ejbpassivate. I could be wrong though.
Thanks
MM(SCEA)

I think what is meant here is that Sun has left the door open for complexities over data cache. This causes problems over transactions and locking. All these should be hidden away from developers. That seems to be Microsoft's take.
As far as Session beans go there could be some uses like non web clients or multiple web applications sharing sessions and for transactional session state. Tyler's article on SFSB are beasts of burden discusses all these.
Thanks
MM(SCEA)

A simple idea would be to drop some debug code in ejbcreate to see if they are actually created. It would be good to know when the association happens because it already exists and the create is not called explicitly.
Thanks
-MM(scea)