RE: EntityBean Events inside tx.
Firstly, I wanted to thank the list for all the responses I had. But, the problem is that the suggested solutions involve using 'Transacted JMS' services. I have not been able to make JMS aware of the transacions it is running on. Messages always get sent, inspite of eventual rollbacks. I only wanted to know if anyone got this working under Orion 1.4.7 Thanks in advance Ramiro Diaz Trepat Opetra "Day, Jem BGI WAC" [EMAIL PROTECTED]To: Orion-Interest [EMAIL PROTECTED] mcc: Sent by: Subject: RE: EntityBean Events inside tx. owner-orion-interest@orion server.com 03/04/2001 02:21 p.m. Please respond to Orion-Interest Here's a description of an implementation of the Observer pattern for EJB. http://www.theserverside.com/resources/ObserverPattern.jsp An alternative is to implement your 'Change Events' as JMS messages, if you are using 'Transacted JMS' messages are only 'published' when the encompassing Tx is committed. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 03, 2001 8:25 AM To: Orion-Interest Subject: EntityBean Events inside tx. We would like our entity beans to propagate events in the same fashion than regular java beans. Therefore we must, for example, send events notifying of property changes inside the bean. The problem with this is that we don't know if this method was called inside a transaction that might be rolled back later on, and hence the property change event should not have been sent at all. Clearly, we want to propagate the events only when the transactions are commited. Is there a standard "pattern" to manage this sort of thing ? TIA Ramiro Diaz Trepat Opetra
XA Queues work ?
Hello list,
We've been trying to use, transaction aware queues with no success..
The problem is that messages always get sent, inspite of rollbacks.
We don't know if it is our fault or this type of queues don't work properly
in Orion.
Here is a snip of our configuration and what we are doing.
---
jms.xml:
xa-topic-connection-factory location
="jms/observerConnectionFactory"/
topic name="Observer" location="jms/observer"
/topic
---
/** Some session bean's method */
UserTransaction transaction = ctx.getUserTransaction();
transaction.begin();
sendMessage();
transaction.rollback();
---
/**
Inside the sendMessage method.
We have tryied to use Topic and Queue types.
*/
Topictopic = null;
XATopicSession session = null;
XATopicConnection connection = null;
XATopicConnectionFactory connectionFactory = null;
TopicPublisher publisher;
InitialContext initialContext = new InitialContext ();
connectionFactory = (XATopicConnectionFactory) initialContext.lookup
("java:comp/env/jms/observerConnectionFactory");
topic = (Topic) initialContext.lookup ("java:comp/env/jms/observer");
initialContext.close ();
connection = connectionFactory.createXATopicConnection ();
connection.start ();
session = connection.createXATopicSession ();
publisher = session.getTopicSession ().createPublisher (topic);
Message message = session.createMessage ();
message.setStringProperty ("str", event.getSource ().toString ());
publisher.publish (message);
session.close ();
connection.close ();
---
Ramiro Diaz Trepat
Opetra
EntityBean Events inside tx.
We would like our entity beans to propagate events in the same fashion than regular java beans. Therefore we must, for example, send events notifying of property changes inside the bean. The problem with this is that we don't know if this method was called inside a transaction that might be rolled back later on, and hence the property change event should not have been sent at all. Clearly, we want to propagate the events only when the transactions are commited. Is there a standard "pattern" to manage this sort of thing ? TIA Ramiro Diaz Trepat Opetra
autoupdate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Everytime I run autoupdate, it updates many packages to version 1.4.7 (which was already installed). That did not happen before, autoupdate used to realize when my system was already up to date. Thank you. - -- Ramiro Daz Trepat -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6x6WDxdtZx3eT+MARAqCFAKCaGmPJakkWgvL1xWO0DBjykE1zHACePek0 bSj8NRzqMaFMZRfkuDf1MRI= =JVpn -END PGP SIGNATURE-
Re: Hypersonic website / docs
Hypersonic SQL is a discontinued product now, it is no longer maintained by it's creator and as far as I know no one is continuing it. Ramiro Diaz Trepat Opetra
RE: Shutting down orion
Guys, there is an AWEFUL bug in jdk1.3 when using URLConnection.getInputStream(); This method worked fine until version 1.2.2 of the jdk. The failure of the shutdown process is probably related to this bug. Here is the BugParade url in sun where you can see all the detailed descriptions. http://developer.java.sun.com/developer/bugParade/bugs/4333920.html I wonder why did they have to touch this pice of code which used to work like a charm since version 1... It only has 25 votes by now, CAST YOUR VOTES ! ramiro diaz trepat -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Storm Linux User Sent: Wednesday, November 08, 2000 1:32 PM To: Orion-Interest Subject: Re: Shutting down orion On Wed, Nov 08, 2000 at 10:02:24AM -0500, Jim Crossley wrote: Although I can shutdown orion using the admin.jar with a 1.2 JVM, I've found that I cannot with a 1.3 JVM. The server ceases to accept connections, but its process does not go away. (Running on Redhat/Debian Linux) Anyone else noticed this? Yes, I noticed this too. But only with the new Sun jdk1.3 . In IBM jdk1.3, it works fine. []s Guilherme Ceschiatti [EMAIL PROTECTED]
importing keypairs
Hi all, why keytool can't import keypairs genereted for example by openssl. Is there a workaround for this matter ? We have some keypairs with their thawte certs and we will not be able to use them with orion since we can import the certificates but we can't import the key-pairs... TIA ramiro diaz trepat
