I have tried a wide variety of combinations of elements on the WebService annotation on both the class and the interface to no success. The only thing that works is deleting the interface, renaming the class to Echo.
That (and the fact that the wsdlLocation has no effect when added the WebService on the class) is what lead me to think the container is ignoring the WebService annotation on the class - it is as if the endpointInterface element is being totally ignored.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031084#4031084
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031084
anonymous wrote :
| I am assuming this requires an XADataSource, right?
|
Yes.
anonymous wrote :
| Optimized locking seems to fail no matter what, with this except:
|
You need Hibernate's OptimisticTreeCacheProvider if you plan to use optimistic locking. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate
anonymous wrote :
| Ok it does actually start filling in the Node values after a while ...
|
This is because you have:
| <async>true</async>
|
which means writes to the DB will not happen immediately, but are batched instead.
Why are you using a cache loader with Hibernate anyway? The purpose of a cache loader is so that an in-memory cache has a place to persist state so state survives over reboots and evictions. With Hibernate, this state will survive *anyway* (in Hibernate) so why add a cache loader as well?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031083#4031083
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031083
I am trying to integrate the Lucene search engine into a Seam application and found Hiberante search to help me with the task. This seems to work, but the implementation got a bit messy. I read that Seam 1.3 could have support for Hibernate Search which would be great.
Do you guys have any clues when the 1.3 version is due? Before summer, next year? It would be nice to know if I could wait or continue with the "messy" solution I'm working on currently.
//Frippe
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031080#4031080
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031080
Thank you for this helpful reply.
I added method start() at the begining and stop() method at the end. But that was not a good move. I received Exception:
anonymous wrote :
| javax.jms.IllegalStateException: This method is not applicable inside the application server. See the J2EE spec, e.g. J2EE1.4 Section 6.6
When i removed method stop() everything works fine.
consumer.close();
| session.close();
| //con.stop();
| con.close();
| ictx.close();
Thanks again. I would have lost much more time if i had not been told what is wrong.
Best regards.
vitor_b
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031073#4031073
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031073