I found the issue with my test... in my case the annotation is only present
in the SEI implementation class but not in SEI...
After revisiting the documentation I realized that we should always annotate
everything in the SEI and only a well qualified @WebService is required in
the SEI implementati
I've honestly never even heard of a sealing violation. A google
search yielded info like:
http://www.visi.com/~gyles19/fom-serve/cache/173.html
I would suggest looking at the classpath and other dependencies to see
if there are multiple versions of jetty being picked up. Other than
th
Any chance you can provide an example? I ran a quick check here and
it seemed to work correctly.
Dan
On May 22, 2008, at 7:15 AM, harbhanu wrote:
Hi,
For the code first approach I am trying to generate wsdl by
providing SEI as
input to java2ws.
Here in my case when I provide "e
We've had major problems with Jetty with shutting down the port and
then retrying to restart it immediately.
If we tried to cycle things quickly (like a shutdown of one service
and than immediately a publish of another on the same port), then
requests to the second service sometimes wouldn'
Hi,
I am trying to get the dynamic client to handle attachments for the web
service whose wsdl is attached. I am starting to feel a bit lost...I am
looking for the bit of code that adds attachments to the message object
when the Java stubs are used rather than the dynamic client but I could
not fi
Yes. There are a couple of options:
1) When you create your Service object, the first parameter is the
wsdl URL to use.If you point that to the wsdl (possibly the live "?
wsdl" on the host you want), any proxies (getPort(..)/createPort(...))
stuff created from there will use the URL's
Hello Chris,
I am using the JaxWsProxyFactoryBean to do what you described. In the
sample code here I went java first but this should work the same for
wsdl2java.
You simply set the url of the service in setAddress and then initialize
a stub for this service.
Is this what you wanted?
Best re
In <2.0.4, we logged stack traces for all the exceptions and everyone
complained about it as they didn't want stack traces for the
exceptions they were throwing from their implementation as they are
rightfully supposed to be mapped to faults. Logs were filling very
fast, etc... Every
Hello,
Is it possible to generate a java service using the CXF wsdl2java
(JAX-WS front end) in such a way that we can use the service with more
than one host?
Basically, I am working on a project where a centralized console
communicates via web services to a number of agents running on remote
hos
Indeed!
Thanks.
Daniel Kulp <[EMAIL PROTECTED]> wrote:
Double check those annotations. I expect the one on the impl has:
"http://videoservice.xx.yy.com";
and the one on the interface has:
"http://videoservice.xx.yy.com/";
The trailing slash is significant.
Dan
On May 22, 2008, at 3:20 PM
Double check those annotations. I expect the one on the impl has:
"http://videoservice.xx.yy.com";
and the one on the interface has:
"http://videoservice.xx.yy.com/";
The trailing slash is significant.
Dan
On May 22, 2008, at 3:20 PM, Jo wrote:
Dan,
The annotated targetNameSpace on the
Dan,
The annotated targetNameSpace on the interface and the
implementation class were the same:
The following is part of the generated WSDL.
Apparently, CXF treats the same string differently. As
you can see
the generated wsdl comes with the default namespace,
"ns1", and "tsn" all pointed to the
In XFire, I think you can get TNS variations by magic.
On Thu, May 22, 2008 at 3:09 PM, Jo <[EMAIL PROTECTED]> wrote:
> I had exactly the same targetNamespace annotation on
> both the interface and the implementation class.
>
>
> -
> From
I had exactly the same targetNamespace annotation on
both the interface and the implementation class.
-
From£ºDaniel Kulp
Sent£º2008-05-22 14:52:14
To£ºusers
cc£º
Subject£ºRe: XFire to CXF issue
OOOHHH this is a completely differ
I figured out how to work my GSOAP/Java mis-match problem after a lot of
effort and some helpful pointers along the way.
The currently documented (in the GSOAP user's guide) approach to enable
attachments is to specify an attachment type in your service header file
(diag.h) that you run soapcpp2.
OOOHHH this is a completely different issue. :-)
If you look, the wsdl at the first one imports the wsdl at the second
one and different targetNamespaces are set. This is caused by the
"targetNamespace" attribute on you @WebService annotations being
different for the interface and
if I use the following URL (deployed both in tomcat
5.5 and 6.0), I got the wrong WSDL (WebParam missing):
http://localhost:8080/video/services/testVideoService?wsdl
If I use the following URL, everything is alright.
http://localhost:8080/video/services/testVideoService?wsdl=videoService.wsdl
Is
using default data binding, spring/cxf enabled Java First services and I
have a operation in a service class that has a Calendar param and while
invoking the operation, I get this exception:
org.apache.cxf.interceptor.Fault: argument type mismatch while invoking
public abstract java.util.List
com.
Any chance you can submit a test case? I just added your method to
one of our test cases and the wsdl generated completely properly:
...
..
name="setImageResolution">
..
On May 22, 2008, at 11:46 AM, Jo wrote:
In my java interface, I have
Hi, I'm writing a unit test for one of my service implementations and
followed the code listed here:
http://cwiki.apache.org/CXF20DOC/a-simple-jax-ws-service.html#AsimpleJAX-WSservice-Publishingyourservice
However, when it gets to the line: svrFactory.create(); I get a stack
trace that indicates
BLOCKQUOTE {MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em}OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px}UL {MARGIN-TOP: 0px; MARGIN-BOTTOM:
0px}Both use the default JAXB binding.
-
What data binding in CXF and in XFire?
On Thu, May 22, 2008
BLOCKQUOTE {MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em}OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px}UL {MARGIN-TOP: 0px; MARGIN-BOTTOM:
0px}CXF with the following config (SoapBindingFactory?):
__
XFire w
What data binding in CXF and in XFire?
On Thu, May 22, 2008 at 11:46 AM, Jo <[EMAIL PROTECTED]> wrote:
> In my java interface, I have the following annotated
> method:
>
>
> @WebMethod(operationName = "setImageResolution",
> action = "urn:setImageResolution")
> @Oneway
> public void setImageRes
In my java interface, I have the following annotated
method:
@WebMethod(operationName = "setImageResolution",
action = "urn:setImageResolution")
@Oneway
public void setImageResolution(@WebParam(name =
"width", header = false)
int width, @WebParam(name = "height", header = false)
int height)
It works great with the extra empty attribute! Thanks for the help!
- Yanping
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 21, 2008 10:42 PM
To: users@cxf.apache.org
Subject: Re: WSDL2Java error
This is a one-line fix in the cxf code to fix this(a
Hi,
I have two question regarding the closing of services. I have made an
user interface for a webservice and it shall be possible to start and
stop the service from the interface. I use the following code to create
and publish the service:
import javax.xml.ws.Endpoint;
import org.apache.cxf.jaxw
Dan,
I think that he started with Aegis and then later wandered to Metro
for comparison purposes, and I also think that there is indeed an
xmime:base64binary that I ran into when I was tweaking Aegis MTOM.
--benson
On Wed, May 21, 2008 at 5:11 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> On M
Hi
My understanding is that if you download a cxf distribution then all the
required abdera dependencies will be there.
There're also plans to for the cxf-jaxrs distribution (or the JAX-RS extensions it provides) available as a seperate bundle, so that
say people relying on Jersey could plugin
Hi,
For the code first approach I am trying to generate wsdl by providing SEI as
input to java2ws.
Here in my case when I provide "exclude = true" for a method then contrary
to the expectation the method
description is still present in the generated wsdl document.
Am I missing something
Hello,
CXF is swallowing exceptions:
22-May-2008 11:59:29 org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
INFO: Application has thrown exception, unwinding now:
java.lang.NullPointerException: null
I think it should provide a full stack trace for all throwable exceptiosn,
because when
> Hi
> May be the easiest way to fix the issue is just drop the Abdera 0.4.0 libs
> into a shared/libs or into your webapp/WEB_INF/libs, or dropping just some
> core Abdera libs (-core, parser, i18n) :
> a.. Core API: abdera.core.0.4.0-incubating.jar (required)
> a.. Parser Impl: abdera.parser.0.4
Hi
Currently CXF JAX-RS installs all providers it supports from a start rather
than loading them lazily, and AtomProvider which depends on Abdera is one of
them. In fact, providing a custom Atom provider would be trivial, but I thought
originally that by shipping a default one would kind of ens
32 matches
Mail list logo
