Wsdlgetinterceptor i think
Le 1 juil. 2011 15:19, "Freeman Fang" a écrit :
> Hi,
>
> It's replaced with org.apache.cxf.frontend.WSDLGetInterceptor.
>
> Freeman
> On 2011-7-1, at 下午9:10, Jacek Laskowski wrote:
>
>> Hi,
>>
>> I've never worked with CXF at the source code level and thought I may
>>
Hi Ryan
On Fri, Jul 1, 2011 at 2:36 PM, Ryan Zoerner wrote:
> Hi Sergey,
>
> Yes, I've been looking at that package and exploring the same issues. I see
> that there is
> an EasyBeansCXFBootstrap. I am unsure whether the bootstrap is what is
> directly
> instantiated by a server such as Jetty or
Correction, I found it searching for which class instantiates
CXFEJBWebserviceEndpoint,
which class instantiates that, etc.
Ryan
Hi Sergey,
Yes, I've been looking at that package and exploring the same issues. I see
that there is
an EasyBeansCXFBootstrap. I am unsure whether the bootstrap is what is
directly
instantiated by a server such as Jetty or Tomcat. I found it, tracing
constructor calls
out from the CXFEJBWebservice
Hi,
It's replaced with org.apache.cxf.frontend.WSDLGetInterceptor.
Freeman
On 2011-7-1, at 下午9:10, Jacek Laskowski wrote:
Hi,
I've never worked with CXF at the source code level and thought I may
change it while migrating openejb from cxf 2.3.x to 2.4.1. There's a
lot to learn and am not havi
Hi,
I've never worked with CXF at the source code level and thought I may
change it while migrating openejb from cxf 2.3.x to 2.4.1. There's a
lot to learn and am not having much luck, and now run into missing
org.apache.cxf.transport.http.WSDLQueryHandler. The class was
available in 2.3.x, but ne
Hi,
Regards,
Lalit Kumar
http://cxf.547215.n5.nabble.com/file/n4541555/Servlet_references.jpg
-
Lalit Kumar
Technical Specialist
Fidelity International
--
View this message in context:
http://cxf.547215.n5.nabble.com/Could-not-instantiate-bean-SpringBus-2-4-1-tp4539354p4541555.html
Sent
On Fri, Jul 1, 2011 at 11:12, Freeman Fang wrote:
> Hi,
>
> I believe this is from another classloder issue, that said, the
> classloader(it could be your servlet war classloader) which load
> org.apache.cxf.transport.servlet.CXFServlet isn't the one(it could be the
> container classloader) which
Hi,
I think that's because CXF 2.3.5 still use neethi 2.x, it's probably
just compatible with your container.
Freeman
On 2011-7-1, at 下午4:39, Lalit Kumar wrote:
Hi,
Even I checked the code 2.3.5 version it works fine. Don't know if
there is
any trouble with 2.4.1 version.
Regards,
--
Hi,
I believe this is from another classloder issue, that said, the
classloader(it could be your servlet war classloader) which load
org.apache.cxf.transport.servlet.CXFServlet isn't the one(it could be
the container classloader) which load javax.servlet.Servlet, so
although org.apache.c
Hi Ryan
On Wed, Jun 29, 2011 at 9:19 PM, Ryan Zoerner wrote:
> Hi Sergey,
>
>>>The fact you have seen EJB-related annotations being associated with a
>>>given CRI instance in debugger simply confirms the fact JVM retains
>>>them. But the sole responsibility of CRI is to model a JAX-RS root
>>>res
There are some change on the bus extensions loading since CXF 2.4.0.
The issue may be related to this part of change.
On 7/1/11 4:39 PM, Lalit Kumar wrote:
Hi,
Even I checked the code 2.3.5 version it works fine. Don't know if there is
any trouble with 2.4.1 version.
Regards,
-
Lalit Kum
Hi,
Even I checked the code 2.3.5 version it works fine. Don't know if there is
any trouble with 2.4.1 version.
Regards,
-
Lalit Kumar
Technical Specialist
Fidelity International
--
View this message in context:
http://cxf.547215.n5.nabble.com/Could-not-instantiate-bean-SpringBus-2-4-1-tp4
13 matches
Mail list logo