[
https://issues.apache.org/jira/browse/OLINGO-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219844#comment-15219844
]
Ramesh Reddy commented on OLINGO-925:
-------------------------------------
BTW, this will leads to errors like
{code}
07:32:34,331 ERROR [io.undertow.request] (default task-6) UT005023: Exception
handling request to /odata4/customers/m/Customers: java.lang.LinkageError:
loader constraint violation: loader (instance of
org/jboss/modules/ModuleClassLoader) previously initiated loading for a
different type with name "org/apache/olingo/server/api/edmx/EdmxReference"
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
at
org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:353)
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:432)
at
org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:269)
at
org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77)
at org.jboss.modules.Module.loadModuleClass(Module.java:560)
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
{code}
> EdmxReference package is in both commons-api and Server-api
> -----------------------------------------------------------
>
> Key: OLINGO-925
> URL: https://issues.apache.org/jira/browse/OLINGO-925
> Project: Olingo
> Issue Type: Bug
> Components: odata4-commons, odata4-server
> Affects Versions: (Java) V4 4.1.0
> Reporter: Ramesh Reddy
> Priority: Blocker
> Fix For: (Java) V4 4.2.0
>
>
> After the build, EdmxReference class is in both "commons-api" and
> "server-api" jar files. This leads to class loader issues when EdmxReference
> is used in the code.
> This is due to "bundle" package mechanism, depending upon how it configured,
> it will pull packages from other modules to be complete.
> The solution here is to use the distinct package names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)