I'm using WSDL2Java to generate client and server class for MTOSI
Notification Consumer.
When I run default client and server class, I got the exception:
Nov 09, 2011 12:17:38 PM org.apache.cxf.service.invoker.AbstractInvoker
invoke
SEVERE: Invocation without a binding operation.
Nov 09, 2011 12:1
Well yes, the thing is that I'm still using the client instance when the
ClientProxy is gc, which destroys the state of client.
On Tue, Nov 8, 2011 at 11:30 PM, Jeff Wang-2 [via CXF] <
ml-node+s547215n497647...@n5.nabble.com> wrote:
> This should be expected, right? The client represents an act
This should be expected, right? The client represents an active
connection (the conduit.) Shouldn't you be calling
ClientProxy.getClient(...) again when you need a new client?
Jeff
On Tue, Nov 8, 2011 at 11:28 AM, Evangelina wrote:
> Hi,
>
> I'm having a few issues trying to migrate CXF from 2.
With great anticipation, I am looking through the OAuth 1.0
implementation in CXF. I have some questions:
In AuthorizationRequestService
1) This is just authorization, right? So we actually need to have
secured the (in the example) /forms/oauthAuthorize.jsp so that before
they go there, they are
Hi
On 08/11/11 19:41, Woonsan Ko wrote:
Hi,
When an undefined _type parameter is used for JAX-RS requests (e.g.,
?_type=foo), it doesn't give any warning logs. It just returns 406 http error
code.
Enabling the fine logging should tell that no Accept header was matched...
It seems better to g
I am working on a CXF/JAXB code-first web service. I would like to be able to
modify the WSDL definitions of some of the inputs.
For example, given the following interface snippet:
@WebMethod
public void Something(@WebParam(name="date") Date date);
The WSDL will generate the XMLSchema f
Hi,
When an undefined _type parameter is used for JAX-RS requests (e.g.,
?_type=foo), it doesn't give any warning logs. It just returns 406 http error
code.
It seems better to give a proper warning log in
o.a.cxf.jaxrs.impl.RequestPreprocessor#handleTypeQuery() method in that case.
Also, it cur
Hi,
I'm having a few issues trying to migrate CXF from 2.3.1 version to 2.5.0.
The main issue is with the Client that I'm creating using the
ClientProxyFactoryBean.
I'm creating my client like this:
ClientProxy.getClient(cpf.create())
where cpf is the instance of ClientProxyFactoryBean, and t
On 08/11/11 17:45, Jon Barber wrote:
Hi Sergey,
So now I see :
"No message body writer has been found for response class GreeterInfo."
Please make sure GreeterInfo is annotated and the packages for
XmlRootElement (and other used annotations) are imported
That works like a charm. JSON
> >
> >
> > Hi Sergey,
> >
> > So now I see :
> >
> > "No message body writer has been found for response class GreeterInfo."
>
> Please make sure GreeterInfo is annotated and the packages for
> XmlRootElement (and other used annotations) are imported
>
That works like a charm. JSON data sen
Hi
On 08/11/11 14:31, Jon Barber wrote:
On Tuesday, November 08, 2011 1:24 PM, "Sergey Beryozkin"
wrote:
Hi
On 08/11/11 13:16, Jon Barber wrote:
On Tuesday, November 08, 2011 10:02 AM, "Jon Barber"
wrote:
Apologies for the delayed reply. Comments in line below.
On Monday, October 31,
On Tuesday, November 08, 2011 1:24 PM, "Sergey Beryozkin"
wrote:
> Hi
> On 08/11/11 13:16, Jon Barber wrote:
> > On Tuesday, November 08, 2011 10:02 AM, "Jon Barber"
> > wrote:
> >> Apologies for the delayed reply. Comments in line below.
> >>
> >> On Monday, October 31, 2011 10:28 PM, "Sergey
Hi
On 08/11/11 13:16, Jon Barber wrote:
On Tuesday, November 08, 2011 10:02 AM, "Jon Barber"
wrote:
Apologies for the delayed reply. Comments in line below.
On Monday, October 31, 2011 10:28 PM, "Sergey Beryozkin"
wrote:
Hi
On 27/10/11 16:28, Jon Barber wrote:
Hi List,
I've managed to g
On Tuesday, November 08, 2011 10:02 AM, "Jon Barber"
wrote:
> Apologies for the delayed reply. Comments in line below.
>
> On Monday, October 31, 2011 10:28 PM, "Sergey Beryozkin"
> wrote:
> > Hi
> >
> > On 27/10/11 16:28, Jon Barber wrote:
> > > Hi List,
> > >
> > > I've managed to get CXF DOS
Hi ,
This is my Method code shown below
Actually this serves as a Webservices Method .
*public Response getData(ServiceRequest request)
{
try
{
final boolean toProceedorNot = validate(legdata);
if (!toProceedorNot) {
st
Yeah, the
META-INF/cxf/cxf-extension*
stuff isn't necessary anymore since CXF 2.4
Freeman
On 2011-11-8, at 下午7:14, ctranxuan ctranxuan wrote:
Thanks a lot !
Just had to removed the import "resource="classpath:META-INF/cxf/cxf-extension-jaxrs-binding.xml" /
>" in my
files and download the bund
Thanks a lot !
Just had to removed the import "" in my
files and download the bundles as specified in the Karaf features.
Thanks again for the quick help!
2011/11/8 Freeman Fang
> Hi,
>
> You need install all necessary bundle yourself.
> If you can use Apache karaf/smx then you can use karaf p
Hi,
You need install all necessary bundle yourself.
If you can use Apache karaf/smx then you can use karaf provision
mechanism which use a feature.xml[1] to describe all necessary
bundles, just simply
features:install cxf
can install all necessary bundles.
However, as you're using Virgo, y
Hi,
I am trying to deploy a bundle that uses cxf-bundle-minimal on the Virgo
3.0.1.RELEASE platform. When upgrading cxf-bundle-minimal from 2.2.9 to
2.5.0 version, I've got the error message:
[2011-11-08 10:01:28.052] system-artifacts Unable to
install application from URI 'file:/home
Apologies for the delayed reply. Comments in line below.
On Monday, October 31, 2011 10:28 PM, "Sergey Beryozkin"
wrote:
> Hi
>
> On 27/10/11 16:28, Jon Barber wrote:
> > Hi List,
> >
> > I've managed to get CXF DOSGi 1.2 working with JSON responses following
> > the discussions I found on this
Hi:
I am using camel 's payload CXF component; Now I want publish a service
which doesn't constraint any xml schema, and client can post any xml element to
this webservice; so I define the wsdl which input message's element is xsd:any;
it looks like:
wsdl:operation name="AnyPort">
21 matches
Mail list logo
