"vickyk" wrote : Can I get some description about the above specified states ?
What more do you need?
The names tell it all.
"vickyk" wrote :
| Normally I would have expected CREATE,START,STOP,DESTROY states .
Ok, the first two you have.
And when you go back over those two you are actually stopping and destroying.
"vickyk" wrote : The default one being the NOT_INSTALLED .
|
Inital context also has to have a state.
ps: look me up at JBW for more details
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987579#3987579
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987579
Hello friends,
The SSL protocol allows client/server applications to communicate in a way designed to prevent eavesdropping, tampering, and data forgery. SSL protects network access, online communications, and digital transactions by enabling a secure channel between your servers and your users. With SSL in place, information transmitted from your online store (e.g., via web forms) is encrypted before it is sent over the Internet.
I've got SSL Certificate for my own site and getting advantages of it.
http://www.ssl.com./
IVAN
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987539#3987539
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987539
Excellent.
The motivation for the JcaXAResourceWrapper is largely the same:
1) Recovery made easier for JBossTS
2) Overriding the isSameRM to fix 'broken' providers
3) Jira task to move the Pad Xid stuff out of the XidFactory and have it be a configurable option per JCA deployment (ConnectionFactory or Endpoint (inflow)).
Right now this is JCA specific but I don't see any reason why would couldn't do this as a general thing.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987537#3987537
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987537
"bstansberry(a)jboss.com" wrote : I thought PojoCache already required the pojo to implement Subject, and that the mixin was being added via your standard pojocache-aop.xml transformation? So, it's just a matter of the session registering as an Observer. That's a PITA, but its a PITA that's already implemented from 4.0.x, so no big deal.
OK, are you aware that PojoCache has its own class of Subject and Observer then (o.j.c.pojo.observable.*)? Make sure you subscribe to that instead. Reason is becuase I need to piggyback information such as field and pre and post events as well that are not present in the AOP package.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987519#3987519
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987519