I want to use HQL editor to test queries but it doesn't work. The problem is that we use annotations instead of configuration file. Is it possible to use annotations instead of configuration file as mapping informations? For now after I run query in HQL editor I got this exception org.hibernate.hql.ast.QuerySyntaxExcetion: HomeEntity is not mapped [select h from HomeEntity h].
Zeus is correct. I guess you may be in a situation similar to me ... I spent a couple of nights to figure it out ... well, I guess, you are using Hibernate with Spring. Those "annotatedClass" classes are defined under the Spring configuration (such as applicationContext.xml) but not in hibernate.cfg.xml. Once I defined those classes with in hibernate.cfg.xml, I can see all the entities available under "Configuration" in the Hibernate (tools) Configurations panel and I can use them in the HQL editor.
Hope this help!
We're migrating an EJB 3.0 application to EJB 3.1 and would like to use #Stereotype to reduce some of the EJB configuration.
The annotations we plan to have are:
#Singleton
#ConcurrencyManagement(BEAN)
#PermitAll
#Interceptors or custom #InterceptorBinding annotation
#SecurityDomain("acme") JBoss / PicketLink
Of those I know that #Singleton can't be put into a #Stereotype and has to be on the EJB itself. What else can't be put into a #Stereotype?
Update
The specification [1], [2] says that
A stereotype encapsulates any combination of:
default scope, and
a set of interceptor bindings.
The examples then use Java EE 7 #Transactional which is an #InterceptorBinding which leads me to believe that none of the above annotations can be put into a stereotype.
The The Java EE 6 Tutorial states the following:
A stereotype is a kind of annotation, applied to a bean, that
incorporates other annotations. Stereotypes can be particularly useful
in large applications where you have a number of beans that perform
similar functions. A stereotype is a kind of annotation that specifies
the following:
A default scope
Zero or more interceptor bindings
Optionally, a #Named annotation, guaranteeing default EL naming
Optionally, an #Alternative annotation, specifying that all beans with this stereotype are alternatives
So as you saw yourself, the annotations you used are not in one of the mentioned groups.
My personal suggestion is, to be careful with creating and using stereotypes, since one then always have to know (or check) what it means, so for example I prefer using #Named #RequestScoped rather than #Model because saving one line of code does not make up to not see the scope at the first glance.
Question pretty much says it all.
Is there an equivalent for org.hibernate.Version.getVersionString() in EclipseLink?
Why isn't there a portable (JPA) way to query provider information in general?
Never used it but from the Eclipselink javadoc you could try the following class:
org.eclipse.persistence.Version
There is a static class and static method to get this information.
Example: How to print in java code
AbstractSessionLog.getLog().log(SessionLog.INFO, DatabaseLogin.getVersion());
I would like to observe or intercept Conversation.begin() method call in CDI in order to stock the new Conversation.getId() and list all the opened conversation.
I don't find in the spec (JSR-299) how to observe such event. I'm thinking of complex system of Extension which would perhaps use ProcessInjectionTarget or ProcessProducer or other events to do that... but I feel like it exists another simpler solution...
Hmm, these are built in beans and so can't be decorated. In CDI 1.1 you could use ProcessInjectionPoint, or add a request to issues.jboss.org/browse/CDI to be able to decorate built in beans.
So right now, not much idea, sorry.
I'm trying to access a data source that is defined within a web container (JBoss) from a fat client outside the container.
I've decided to look up the data source through JNDI. Actually, my persistence framework (Ibatis) does this.
When performing queries I always end up getting this error:
java.lang.IllegalAccessException: Method=public abstract java.sql.Connection java.sql.Statement.getConnection() throws java.sql.SQLException does not return Serializable
Stacktrace:
org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService.doStatementMethod(WrapperDataSourceS
ervice.java:411),
org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService.invoke(WrapperDataSourceService.java
:223),
sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source),
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25),
java.lang.reflect.Method.invoke(Method.java:585),
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155),
org.jboss.mx.server.Invocation.dispatch(Invocation.java:94),
org.jboss.mx.server.Invocation.invoke(Invocation.java:86),
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264),
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659),
My Datasource:
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>jdbc/xxxxxDS</jndi-name>
<connection-url>jdbc:oracle:thin:#xxxxxxxxx:1521:xxxxxxx</connection-url>
<use-java-context>false</use-java-context>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>xxxxxxxx</user-name>
<password>xxxxxx</password>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<min-pool-size>5</min-pool-size>
<max-pool-size>20</max-pool-size>
</local-tx-datasource>
</datasources>
Does anyone have a clue where this could come from?
Maybe someone even knows a better way how to achieve this.
Any hints are much appreciated!
Cheers,
Michael
Not sure if this is the same issue?
JBoss DataSource config
DataSource wrappers are not usable outside of the server VM
#Michael Well, java.sql.Connection is an Interface - it might technically be possible for the concrete implementation you're getting from JBoss to be Serializable - but I don't think you're really going to have any options you can use. If it was possible, it would probably be easy :)
I think #toolkit might have said the right words with useable outside the VM - the JDBC drivers will be talking to native driver code running in the underlying OS I guess, so that might explain why you can't just pass a connection over the network elsewhere.
My advice, (if you don't get any better advice!) would be to find a different approach - if you have access to locate the resource on the JBoss directory, maybe implement a proxy object that you can locate and obtain from the directory that allows you to use the connection remotely from your fat client. That's a design pattern called data transfer object I think Wikipedia entry
#toolkit:
Well, not exactly. Since I can access the data source over JNDI, it is actually visible and thus usable.
Or am I getting something totally wrong?
#Brabster:
I think you're on the right track. Isn't there a way to make the connection serializable? Maybe it's just a configuration issue...
I've read up on Ibatis now - maybe you can make your implementations of Dao etc. Serializable, post them into your directory and so retrieve them and use them in your fat client? You'd get reuse benefits out of that too.
Here's an example of something looks similar for Wicket
JBoss wraps up all DataSources with it's own ones.
That lets it play tricks with autocommit to get the specified J2EE behaviour out of a JDBC connection. They are mostly serailizable. But you needn't trust them.
I'd look carefully at it's wrappers. I've written a surrogate for JBoss's J2EE wrappers wrapper for JDBC that works with OOCJNDI to get my DAO code unit test-able standalone.
You just wrap java.sql.Driver, point OOCJNDI at your class, and run in JUnit.
The Driver wrapper can just directly create a SQL Driver and delegate to it.
Return a java.sql.Connection wrapper of your own devising on Connect.
A ConnectionWrapper can just wrap the Connection your Oracle driver gives you,
and all it does special is set Autocommit true.
Don't forget Eclipse can wrt delgates for you. Add a member you need to delegate to , then select it and right click, source -=>add delgage methods.
This is great when you get paid by the line ;-)
Bada-bing, Bada-boom, JUnit out of the box J2EE testing.
Your problem is probably amenable to the same thing, with JUnit crossed out and FatCLient written in an crayon.
My FatClient uses RMI generated with xdoclet to talk to the J2EE server, so I don't have your problem.
I think the exception indicates that the SQLConnection object you're trying to retrieve doesn't implement the Serializable interface, so it can't be passed to you the way you asked for it.
From the limited work I've done with JDNI, if you're asking for an object via JNDI it must be serializable. As far as I know, there's no way round that - if I think of a better way I'll post it up...
OK, one obvious option is to provide a serializable object local to the datasource that uses it but doesn't have the datasource as part of its serializable object graph. The fat client could then look up that object and query it instead.
Or create a (web?) service through which to access the datasource is governed - again your fat client would hit the service - this would probably be better encapsulated and more reuseable approach if those are concerns for you.