synapser | An R package providing programmatic access to Synapse | Collaboration library
kandi X-RAY | synapser Summary
kandi X-RAY | synapser Summary
The synapser package provides an interface to Synapse, a collaborative workspace for reproducible data intensive research projects, providing support for:. The synapser package lets you communicate with the Synapse platform to create collaborative data analysis projects and access data using the R programming language. Other Synapse clients exist for Python, Java, and the web browser.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of synapser
synapser Key Features
synapser Examples and Code Snippets
Community Discussions
Trending Discussions on synapser
QUESTION
I have a WAR containing a dependency JAR. The JAR contains cross-cutting concerns and is written by me as well. I'm using Spring 4.2.3 and Spring-data-jpa 1.9.1 and my configuration is annotation based. I deploy to Wildfly 10.1.0.
The JAR compiles fine and I install it to my local Maven Repo. From the WAR, the JAR is included as a dependency. So far so good.
On the Spring Configuration file of the WAR, I import the Spring Configuration file of the JAR.
Now, when I have normal Spring Beans (Service or Component), everything works fine and Spring finds and resolves all dependencies and Spring Beans in my JAR, which I can then subsequently invoke from the code in my WAR.
However, as soon as I add a Repository and an Entity, Spring does not find the Entity and subsequently my WAR compiles but it does not deploy. I must note that all of this works if I put the JAR code in my WAR direcetly. I think I'm missing a configuration, but I'm not sure where else to look.
Any assistance will be greatly appreciated. Code and Stack-trace below:
On deployment, I get the following error: Error creating bean with name 'synapseRepo': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Not an managed type: class hyphen.synapse.data.model.Role
So, the error is pretty straightforward, but I'm not sure what else it is that I'm missing to let Spring know about my Entity.
Thanks.
JAR Code for Configuration:
...ANSWER
Answered 2017-Feb-21 at 00:27Your SynapseRepo
and CommandRepo
interface should have the @Repository
annotation.
However the root of the problem is that you have a JPA configuration in your WAR file and a JPA configuration in your JAR. Because the names, properties files, etc. will lead to beans overriding each other. You will need to spend the time to make them unique. You can follow the instructions at https://stackoverflow.com/a/19976132/724835
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install synapser
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page