[
https://issues.apache.org/jira/browse/OLINGO-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908022#comment-14908022
]
Christian Amend commented on OLINGO-761:
----------------------------------------
Hi Eugenio,
sorry for my late reply I got help up at work.
I just installed a Wildfly 8.2.1 instance and managed it via the JBoss Tools of
Eclipse. I can deploy our ReferenceScenario and it works although I got some
exceptions during deployment. I have attached the stacktrace to this issue in
case you are interested. Still sending and receivieng requests works fine.
As for the sample you provided I had to make some adjustments to make it work.
I added a web.xml file and added the dynamic web project facets 3.0 via eclipse
to even be able to delpoy it to my instance. Afterwards everything went fine. I
did not even get an exception during deployment. Here is the log entry I saw on
the console:
15:05:31,633 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6)
JBAS015876: Starting deployment of "bar.war" (runtime-name: "bar.war")
15:05:31,681 INFO [org.jboss.weld.deployer] (MSC service thread 1-5)
JBAS016002: Processing weld deployment bar.war
15:05:31,728 INFO [org.jboss.weld.deployer] (MSC service thread 1-2)
JBAS016005: Starting Services for CDI deployment: bar.war
15:05:31,728 INFO [org.jboss.weld.deployer] (MSC service thread 1-1)
JBAS016008: Starting weld service for deployment bar.war
15:05:31,962 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service
thread 1-5) Deploying javax.ws.rs.core.Application: class com.foo.MyApplication
15:05:31,978 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5)
JBAS017534: Registered web context: /bar
15:05:31,993 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1)
JBAS018559: Deployed "bar.war" (runtime-name : "bar.war")
So unfortunately I can`t reproduce your issue. So there is two ways we can go
about this. First I would recommend you try to use the ODataServlet instead of
the CXF Servlet we provide. Here is a tutorial how to do this:
http://olingo.apache.org/doc/odata2/tutorials/servlet.html
This could fix your issue as we do not have static classes in there.
Secondly you could try to take away the final modifier from the class and see
if this allows you to deploy without further issues. If this is the case we
could make such a fix in the Olingo library.
Let me know how it goes.
Best Regards,
Christian
> ODataApplication$MyProvider is not proxyable
> --------------------------------------------
>
> Key: OLINGO-761
> URL: https://issues.apache.org/jira/browse/OLINGO-761
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 2.0.2, V2 2.0.4
> Reporter: Eugenio Lentini
> Assignee: Christian Amend
> Attachments: OlingoIssue.zip
>
>
> I am trying to deploy a web application into WildFly 8.2.0 along with a
> service REST written with JAX-RS,there are just a couple of resources and a
> class extending Application annotated with @ApplicationScoped.
> The application has even a module OData based on Olingo OData 2, version
> 2.0.2.
> During the deployment I get this exception
> {code:borderStyle=solid}
> Caused by: org.jboss.weld.exceptions.UnproxyableResolutionException:
> WELD-001437: Normal scoped bean class
> org.apache.olingo.odata2.core.rest.app.ODataApplication$MyProvider is not
> proxyable because the type is final or it contains a final method class
> org.apache.olingo.odata2.core.rest.app.ODataApplication$MyProvider - <unknown
> javax.enterprise.inject.spi.Bean instance>.
> at
> org.jboss.weld.util.Proxies.getUnproxyableClassException(Proxies.java:229)
> at
> org.jboss.weld.util.Proxies.getUnproxyableTypeException(Proxies.java:178)
> {code}
> According to the documentation more or less all the injected beans are
> proxies, the final modifier prevent the subclass to be created.
> Have you already got experience like that?
> Thanks for the attention.
> Eugenio
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
