[JBoss Seam] - Re: Can Seam work with no ejb3 but with Hibernate ORM?
by pgrillo
Yes, different flavor means different class. Multiple factories by productID may return specializations of any of our DAOs.
Sorry, for this last question. Just trying to inject my Hibernate session, and the doc reads.
anonymous wrote : Seam will bootstrap a Hibernate SessionFactory from your hibernate.cfg.xml file if you install the built-in
| component named org.jboss.seam.core.hibernate.
|
Does this mean that my Hibernate session must be fully defined through the hibernate.cfg.xml?
Because, I build the Hibernate Factory dynamically. I start with a hibernate properties file, then dynamically find optional mapping files that may or may not exist, and dynamically add them, then build it.
So, everything is not self contained or static in a configuration file. Is there a way to somehow provide Seam with the Factory that our app built? Or have i misread what i required to get Seam a reference to our factory so it can manage our session.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993910#3993910
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993910
19 years, 4 months
[JBossWS] - Re: java.lang.UnsupportedOperationException when connecting
by rayymlai
this seems to be a compatibility issue of JBossWS 1.0.x with Java SE 6.0's JAX-WS 2.0. I've siimlar problem.
I had the JSR181EJB3 example from JBossWS 1.0.3/1.0.4 running well on JBoss AS 4.0.4/4.0.5 (after some painful patches). After I upgrade my JDK to 6.0, the same example generates the exception UnsupportedOperationException.
I try to remove the javax.xml.SOAPMessage*.class from the jbossws-client.jar and let the example uses Java SE 6.0's JAX-WS API. but it seems that there are more APIs impacted.
Previous email threads mention JDK 6.0 beta. But the same exception occurs for the GA version of 6.0 as well.
Java SE 6.0 provides amazing JAXWS 2.0 support. You can use its embedded HTTP web server to publish web services. New JAXWS 2.0 APIs are provided. I'd assume the current JBossWS 1.0.4's JAXWS API is not sync up with the latest JAXWS 2.0 yet.
Perhaps JBossWS team can advise the compatibility issue. Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993905#3993905
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993905
19 years, 4 months