-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File-Store/File-Client not compatible with Wildfly 8 #11
Comments
BTW: The resource adapter configuration section in the standalone.xml of Wildfly is:
|
I am struggling with this issue. How did you resolve it? |
Hi, I tried the following: ................org.connectorz.files.store.Client........... import java.net.URI; /**
// @resource(name = "jca/files")
// public String fetch(@PathParam("id") String id) {
................... I changed the return type from Object to FileBucketStore .................org.connectorz.files.store.GenericManagedConnectionFactory..............
................... The client is getting the injection (Yuppiiiii!!!) but still getting an strange error during casting :-( ............Console.......... Some suggestions or solved in the meantime? Thanks and regards Frank |
Same error here on Payara: |
this is a clasloading-issue. the .rar-file as well as the client.war contain the api.jar. it should not be part of the client.jar. change the pom.xml of the client.jar to have the api as provided-scope:
|
How do we solve the problem, if we aren't using maven to do the deployments. I basically extracted the "Bucket" and "BucketStore" interfaces into a saperate jar . and injected this jar as a dependency in both the rar-file and the Jax-RS-client of this rar. But i still see the first error reported in the issue even on the latest package of build. Questions:
|
Hi Adam,
after hacking around some problems in the code because of missing hashCode() and equals() in FileAdapter class and removing the not supported "@min(1)" annotation for setRootDirectory() function in GenericManagedConnectionFactory class, I'm stuck.
I can deploy the the file-store and the file client (with changed resource name "java:jboss/eis/Bucket") successfully.
But when I try to use a REST resource (getting a connection), I always get the following stack-trace in Wildfly:
Maybe you can have a quick look what's going on here.
cheers,
Dino
The text was updated successfully, but these errors were encountered: