Someone needs to make a JIRA with all the bits and pieces in place.
-Original Message-
From: Piotr W. Berlowski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 23, 2007 8:06 AM
To: cxf-user@incubator.apache.org
Subject: RE: JAX-WS + JAXB problem -
We won't know until we debug it :-)! Just pick one.
-Original Message-
From: Piotr W. Berlowski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 23, 2007 8:29 AM
To: cxf-user@incubator.apache.org
Subject: RE: JAX-WS + JAXB problem -
javax.xml.ws.soap.SOAPFaultException
thrown
In the interests of a less eventful life, I moved my production code to
JAXB from Aegis. My doc guy just pointed out to me that our WSDL has
rather less schema elements than expected. Indeed, there seems to have a
been a giant migration to the service TNS, at least of enums.
In the wsdl that is
Oh, well, that's simple enough.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 23, 2007 3:33 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: Migrating enums
This is probably working as designed for JAX-WS tck/spec
OK, I get it. Namespace=' as well.
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 23, 2007 4:11 PM
To: Daniel Kulp; cxf-user@incubator.apache.org
Subject: RE: Migrating enums
I've already got the following. I take it I need more
chema validation error on node xs:element
http://localhost:8103/sos/v/team/work/008C5960-CCD0-B345-FB71-4DA1E25F3
A7F/cont/7831554/arun/8290304/analysisDetails?workItemKey=66907978-A3C0-
721B-1E3D-681666C7CA8Brules=262148ruleSetId=-1resultMessage=0resourc
e=0
Error resolving component
They have the same effect, but only Aegis looks at the aegis annotation
and only JAXB looks at the first. I've considered making Aegis look at
both.
However, if you are in a position to use @nnotations, why use Aegis?
-Original Message-
From: shaminda perera [mailto:[EMAIL PROTECTED]
Dan,
It would seem that the line of least resistance is to make [] work like
List.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 1:13 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: JAXB + JAX-WS + faults
I'd vote for FINE. The system is 'working as designed'.
If we push it to FINE, I'd not bother to keep track.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 1:13 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re
Should we reduce the logging noisiness of this process?
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 1:01 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: JAXB + JAX-WS + faults
Benson
@incubator.apache.org
Cc: Benson Margulies
Subject: Re: JAXB + JAX-WS + faults
Well, the issue is that the system is working as designed, however,
it
may not be working as the user THINKS it is designed.
For example, if I create an exception like:
public class FooException extends Exception
I was surprised to see that JAXB schematizes the private static final
long serialVersionUID from my exception class. Is there some special
case for these, in spite of being private?
Got it.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 18, 2007 10:27 AM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: JAXB and serialVersionID
On Thursday 18 October 2007, Benson Margulies wrote:
I was surprised
Since moving to the latest 2.0.3 snapshot, I'm getting an exception when
marshalling a fault declared on a 'throws' clause. No @WebFault. This
didn't happen with 2.0.2 afaik.
WARNING: Exception occurred while writing fault.
org.apache.cxf.interceptor.Fault: Marshalling Error:
Well, perhaps you do.
Use the CXF config to hang a handler in front of the CXF handler that
filter-feeds for ?wsdl? I can't prove that jetty allows one handler to
peek into a context owned by a successor.
-Original Message-
From: James Mao [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
My opinion is that using the Simple front end with an interface (as
opposed to a WSDL) is a gun pointed firmly at the user's foot, and we
should prohibit it.
Jonathan, I can't prove it today, but my gut feeling is that you are
still experiencing the client constructing a different contract than
to handle this, I hope. :)
-Jonathan
Benson Margulies wrote:
My opinion is that using the Simple front end with an interface (as
opposed to a WSDL) is a gun pointed firmly at the user's foot, and
we
should prohibit it.
Jonathan, I can't prove it today, but my gut feeling is that you
Has Dan's fix to part names been snapshotted as yet?
Unless you ask special for Bare, a method like
String[] bloop (String bleep, int floup)
And the WSDL will give you one return part and one parameters part.
-Original Message-
From: cunparis [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 16, 2007 3:40 AM
To:
Marshaller to control the
namespace prefix.
Currently we use hard code to set properties for JAXB Marshaller ,
maybe
we need more flexible way to configure JAXB Marshaller.(use spring
configuration ? )
-Jim
Benson Margulies wrote:
I see a way to get a grip on this problem via
I'm negotiating with Microsoft support about a WSDL of mine which, even
though the parts are called 'parameters', doesn't get the desired
'wrap/unwrap' behavior. If I could send a working example to them it
might advance the cause.
Where are you getting the requirement that the response be named
'Response', as opposed to, say, OpNameResponse?
Aside from that, I think that what you are asking for is the default
behavior of JAX-WS + JAXB.
-Original Message-
From: cunparis [mailto:[EMAIL PROTECTED]
Sent: Monday,
I've got the following situation. I've used annotations to control all
the namespace prefixes in my service. The wsdl I can pull with ?wsdl or
java2wsdl has the prefixes I expect. However, responses from my service
do not use the specified prefix. Here's an example. Note the use of
'ns1', which
Willem may have already fixed this.
Consider this (which wouldn't be a bad example for the doc): It adds a
log, a webapp, and some static content to the server. All is well,
except that the process seems never to exit. Is this just 'fixed in
2.0.3'?
?xml version=1.0 encoding=UTF-8?
beans
I added
cxf:bus
cxf:features
cxf:logging/
/cxf:features
/cxf:bus
To my beans. I didn't set up and special j.u.logging properties. I don't
see anything.
Fellow users:
When using JAXB code-first, how much do people worry about the
irritation of Java strings mapping to arrays?
That is: String foo:
Turns into an array of 0 or 1 strings, to account for the possibility of
null versus versus foobar.
One can clean this up with
@incubator.apache.org
Cc: Benson Margulies
Subject: Re: Best practices with min/max occurs/nillable and JAXB
On Thursday 11 October 2007, Benson Margulies wrote:
Fellow users:
When using JAXB code-first, how much do people worry about the
irritation of Java strings mapping to arrays?
Well, I personally
At least with CXF, the namespace prefixes for the wsdl:definition
element ignore any @XmlNs mappings on the package-info.java of the
package containing the SEI.
Is this right?
In my experience, the VS2005 wsdl.exe doesn't like bare, at least when
CXF 2.0.2 and Aegis+JAX-WS are at work. It complains bitterly of name
conflicts.
If this is supposed to work, I'll concoct a JIRA.
-Original Message-
From: William Leung [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
AFICT, this is a Microsoft 'feature'. It is creating 'wrapped'
structures, not 'cracking' the param list. I am thinking of opening a
support request at Microsoft; there used to be a way to avoid this.
-Original Message-
From: William Leung [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
Is there a way to express this with jaxws:? Whether or not, is there an
editor out there for QNames that reduces the noise level of this?
bean id=rni-proxyFactory
class=org.apache.cxf.jaxws.JaxWsProxyFactoryBean
property name=serviceClass
When I run a simple junit test that uses a client created using spring
configuration, I get some INFO level log traffic on the console.
These messages seem a bit noisy. Or, maybe, the real question is who is
setting j.u.l to operate at INFO?
Oct 10, 2007 2:32:07 PM
I tried fussing with the part names and didn't have any impact on the
wsdl.exe.
maxOccurs='unbounded' triggers a bug in wsdl.exe. It would be nice if we
could suppress it.
I have a service request open to Microsoft to find out how get
'unwrapped' method signatures.
-Original Message-
Margulies
Subject: Re: when to write maxOccurs
On Tuesday 09 October 2007, Benson Margulies wrote:
As it happens, Microsoft's tool for consuming WSDL files is not good
at dealing with maxOccurs='unbounded'. Which is, AFAIK, the default
value. How does CXF decide whether to write
Then we got a compliance problem.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 6:06 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: True or false: embedded schemata need to be imported?
If an embedded
Subject: RE: when to write maxOccurs
Nope-- the default value for both minOccurs and maxOccurs is 1. So,
if
you have neither, it means it expects exactly 1 element.
-Chris
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 6:15 PM
@WebMethod
public abstract void addNameBatch(@WebParam(name=indexid) String
indexid,
@WebParam(name=names)Name[]
names) throws NameIndexException;
It looks to me as if an array of names has turned into an array of
arrays of names. Shouldn't
I pointed the Microsoft visual studio 2005 wsdl.exe tool at a WSDL from
one of my CXF services.
The results are not wonderful. I get warnings like the following. Based
on my reading of the WSDL, the Microsoft tool is just confused, but I
wonder if anyone else has been here?
Schema validation
So far, not too good.
'Unable to generate a temporary class (result = 1). Error CS0030: Cannot
convert type BasisTechnology.rnm.ws.Name[] to
BasisTechnology.rnm.ws.Name'
This is thrown on construction of the proxy class generated by their
wsdl tool.
I'm also getting all the parameters wrapped
Also, the Mindreef Soapscope tool has complaints about inaccessible
types that I am harassing their tech support for an explanation of.
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 09, 2007 9:55 AM
To: cxf-user@incubator.apache.org
The cs0030 is this charming bug of Microsoft's:
http://support.microsoft.com/kb/891386
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 09, 2007 9:57 AM
To: cxf-user@incubator.apache.org
Subject: RE: Microsoft interoperability
Also
-Original Message-
From: Mindreef Support [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 09, 2007 5:01 PM
To: Benson Margulies
Subject: [issue #QSU-61718-589]: Validation errors that don't make sense
to me
Hi Benson,
Thanks for sending the WSDL.
Issue #1: When you're
committed your test case few days ago, now the resource handler
should work :)
Willem.
Benson Margulies wrote:
Willem,
Adding a DefaultHandler as per the wiki has the instant result of
disabling CXF on that engine. Perhaps we need a different example?
I'm struggling to make
listener
listener-class
org.springframework.web.context.ContextLoaderListener
/listener-class
/listener
Willem.
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Fri 10/5/2007 21:13
To: cxf-user@incubator.apache.org
Subject
. Is
there a better way to approach all this?
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, October 05, 2007 4:15 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: Self-referential WSDL import from ?wsdl URL
It's a difference in namespace
I tried specifying a jaxws:endpoint with an explicit serviceName
attribute, and was rewarded with a NullPointerException. I'll set up a
test case for JIRA
Is that 'serviceClass' in the jaxws:endpoint element? If so, I'll add it
to the Wiki doc.
-Original Message-
From: Willem2 [mailto:[EMAIL PROTECTED]
Sent: Friday, October 05, 2007 9:48 AM
To: cxf-user@incubator.apache.org
Subject: Re: jaxws:endpoint versus interface versus service
I've got all my nice annotations on the interface, not on the impl.
Could some kind soul clue me in on how to tell the spring config to look
at them there
I'm dismayed to find that the WSDL from ?wsdl from my JAX-WS service has
parameters named 'arg0, arg1, ...' instead of the names derived from
reflection into the method parameter lists. Is this to be expected?
I just answered my own question ... or, to be exact, discovered that Dan
answered it. I guess that I need some @WebParam's, or to switch to
contract-first.
https://issues.apache.org/jira/browse/CXF-897
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Friday
I see this coming out of my service, but I can't say that I can easily
believe it.
wsdl:definitions name=NameIndex
targetNamespace=http://impl.ws.index.rnm.basistech.com/;
wsdl:import
location=http://localhost:8080/development/NameIndex?wsdl=NameIndex.wsd
l
Sending in a random URL provoked this. Would it make sense to make a
JIRA requesting that this situation result in a more concise log
message?
[jetty] org.apache.cxf.interceptor.Fault: No such operation:
[jetty] at
Is this the 'nillable' / 'minOccurs' issue?
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 03, 2007 7:47 AM
To: cxf-user@incubator.apache.org
Cc: Kaleb Walton
Subject: Re: Empty List's not being marshaled?
On Wednesday 03 October 2007,
Well, it could be related to CXF-1080, for which Dan Kulp cooked up a
fix today. However, if you have explicit @WebFaults, I'm not sure what
to think.
A test case might be good.
-Original Message-
From: Tolan, Michael E [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 03, 2007 1:26
I tried that and I still couldn't get to a clean state. My later email
describes my variational adventures with the Spring configuration
alternative.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 02, 2007 6:09 PM
To: Benson Margulies
Cc: cxf
My goal is to figure out whether this person is using the version with
or without all the Aegis repairs.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 02, 2007 5:11 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: FW
I tried that. I still found my configuration changes to the server
'already present' when I create the next application context.
-Original Message-
From: Willem2 [mailto:[EMAIL PROTECTED]
Sent: Monday, October 01, 2007 9:11 AM
To: cxf-user@incubator.apache.org
Subject: Re: Spring,
The server's list of handlers still has the extra handler. Did you look
at the source code I sent? The @Before method inserts an extra handler
into the server. The @After calls bus.shutdown.
The next time we run the @Before, we should be restarting from complete
zero, we are rereading the beans
the test, so would you please check your
configuration of maven-surefire-plugin, ensure that the forkmode
property
is pertest.
Best Regards
Freeman
On 10/1/07, Benson Margulies [EMAIL PROTECTED] wrote:
The server's list of handlers still has the extra handler. Did you
look
Do you have an example of using the handler clause to set up some static
content so that it doesn't get tangled up with web service endpoints?
-Original Message-
From: Willem2 [mailto:[EMAIL PROTECTED]
Sent: Monday, October 01, 2007 8:55 AM
To: cxf-user@incubator.apache.org
Subject:
This problem goes away if I take out the engine config. So, I guess I'm
asking why the following disables handling actual web service endpoints.
Do I need some different bit of spring-ery to add my handlers without
disturbing the usual handler for the endpoints?
httpj:engine-factory bus=cxf
Willem,
Adding a DefaultHandler as per the wiki has the instant result of
disabling CXF on that engine. Perhaps we need a different example?
I'm struggling to make a ResourceHandler work, if I get it going I could
edit the wiki.
--benson
[junit] Testcase:
testEchoNoException(com.basistech.rnm.index.ws.EchoTest): Caused an
ERROR
[junit] null
[junit] java.lang.ExceptionInInitializerError
[junit] at
org.apache.cxf.aegis.util.jdom.StaxBuilder.init(StaxBuilder.java:134)
[junit] at
Please forgive me for pasting a lot of code into here.
I'm trying to set up a unit test framework where the fixture sets up
jetty with an endpoint and some static content. So, as you will see, I
have an @Before that sets everything up, and an @After that tries to
tear everything down.
However,
Looking at the CodeFirstTest, why does the local: URL bother to have
localhost:9000 in it?
[BIM]
Step 1: create a JaxWsServiceFactoryBean. Set the service class.
Step 2: create a JaxWsServerFactoryBean over the service factory bean.
Step 3: observe that the serviceClass of the serverFactory bean is null.
Shouldn't it default to that of the service factory?
here.
Thanks
Jeff
Benson Margulies wrote:
Step 1: create a JaxWsServiceFactoryBean. Set the service class.
Step 2: create a JaxWsServerFactoryBean over the service factory
bean.
Step 3: observe that the serviceClass of the serverFactory bean is
null.
Shouldn't it default
What are the abilities of Aegis (on the one hand) and JAXB (on the
other) to take documentation from somewheres and have it appear in WSDL
annotations?
I've got a log4j config file as follows. Anyone have a guess as to why I
keep seeing CXF 'INFO' level messages?
# Set root logger level to ERROR and its only appender to A1.
#
log4j.rootLogger=ERROR, A1
# A1 is set to be a ConsoleAppender.
Could someone please post a recipe for combing the local transport with
jaxws?
/incubator/cxf/trunk/common/common/src/m
ai
n/java/org/apache/cxf/common/logging/
Best Regards
Freeman
Benson Margulies wrote:
I've got a log4j config file as follows. Anyone have a guess as to
why I
keep seeing CXF 'INFO' level messages?
# Set root logger level to ERROR
.
Thanks
Guillaume
On 9/21/07, Benson Margulies [EMAIL PROTECTED] wrote:
I have a sudden inspiration here.
Make a 'filter' for the TypeCreator interface. Grab the usual type
creator chain (from getTypeCreator()) and stick it into your filter
object. Make your filter post-edit the Type
=org.apache.xerces.jaxp.SAXParserFacto
ryImpl
javax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.Document
BuilderFactoryImpl
Regards,
Ramanand Singh
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Friday, September 21, 2007 3:12 PM
To: cxf-user@incubator.apache.org
I don't have a clue why DefaultTypeMappingRegistry is final. It looks
like a mistake. Why put protected methods in a final class?
Here's my temporary prescription.
1) make a subclass of XMLTypeCreator. You'll probably have to override
createClassInfo(PropertyDescriptor). If you get one of the
Looks like you need to fix your deployment to isolate your CXF
application from the wrong XML parser which seems to be in there by
default.
-Original Message-
From: Singh, Ramanand [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 19, 2007 6:02 PM
To: cxf-user@incubator.apache.org
Something like the following? It's isn't CXF, but it's from the main
function of a plain old java command line that uses Spring to set up
some things.
GenericApplicationContext appContext = new GenericApplicationContext();
XmlBeanDefinitionReader reader = new
XmlBeanDefinitionReader(appContext);
Sorry, I wasn't clear. You only need the .aegis.xml if you don't like
what Aegis comes up with on its own. It will come up with Something for
a map. I'll look into what it does.
-Original Message-
From: kayteeem [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 18, 2007 8:54 PM
To:
Hmm. Let me check the inventory of test cases.
-Original Message-
From: kayteeem [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 18, 2007 8:55 PM
To: cxf-user@incubator.apache.org
Subject: RE: Map contains no data when returned from remote call -
Aegis
databinding - empty Map?
, September 18, 2007 9:01 PM
To: Benson Margulies
Subject: RE: Map contains no data when returned from remote call -
Aegis
databinding - empty Map?
Thanks, much appreciated as this is driving me nuts!
bmargulies wrote:
Sorry, I wasn't clear. You only need the .aegis.xml if you don't
like
Please post a case to JIRA.
-Original Message-
From: girish sonber [mailto:[EMAIL PROTECTED]
Sent: Monday, September 17, 2007 4:23 AM
To: cxf-user@incubator.apache.org
Subject: Problems with ListItem in Java-First Service
hello Criss,
i am using cxf2.1 and eclipse europa
for folowing up on the JIRA!
bmargulies wrote:
Can you send me the precise content of your .aegis.xml
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Monday, September 10, 2007 9:15 PM
To: cxf-user@incubator.apache.org
Subject: RE: Aegis mappings
these are on some one's radar.
Thanks,
Jacob
On 9/12/07, Benson Margulies [EMAIL PROTECTED] wrote:
I have some ideas in this area, but we need to finish some of what's
currently outstanding. We could enhance the options class.
-Original Message-
From: tog [mailto:[EMAIL
Could you post a JIRA with an entire test case, by some chance? If so,
I'll look for the fix.
-Original Message-
From: Tawfik [mailto:[EMAIL PROTECTED]
Sent: Monday, September 10, 2007 4:22 PM
To: cxf-user@incubator.apache.org
Subject: Re: Aegis mappings not reflecting in wsdl method
The service you are talking to is very unhappy with you. Can you get a
trace of the message traffic?
-Original Message-
From: Ryan Moquin [mailto:[EMAIL PROTECTED]
Sent: Monday, September 10, 2007 7:59 PM
To: cxf-user@incubator.apache.org
Subject: Can't figure out why I'm getting
http://cwiki.apache.org/CXF20DOC/debugging.html
-Original Message-
From: Ryan Moquin [mailto:[EMAIL PROTECTED]
Sent: Monday, September 10, 2007 7:59 PM
To: cxf-user@incubator.apache.org
Subject: Can't figure out why I'm getting this error or how to
troubleshoot it
I've been
getting netbeans to make the association
to
the source code so that the breakpoint is hit.
On 9/10/07, Benson Margulies [EMAIL PROTECTED] wrote:
The service you are talking to is very unhappy with you. Can you get
a
trace of the message traffic?
-Original Message-
From: Ryan
For me, at least, I think I'd need to ask you to post up enough Java
code to demonstrate the effect. Some of the others might be more
energetic. I'll see if I can construct a test case that repros your
problem, however.
-Original Message-
From: Tawfik [mailto:[EMAIL PROTECTED]
Sent:
Can you send me the precise content of your .aegis.xml
-Original Message-
From: Benson Margulies [mailto:[EMAIL PROTECTED]
Sent: Monday, September 10, 2007 9:15 PM
To: cxf-user@incubator.apache.org
Subject: RE: Aegis mappings not reflecting in wsdl method parameters
Hmm. I've been
Does CXF look for package-info.aegis.xml for namespace? If not, is
anyone opposed to having it do so?
Subject: Re: returning tabular data from a webmethod
2.0.1. Do you recommend moving to a snapshot build?
On 9/7/07, Benson Margulies [EMAIL PROTECTED] wrote:
What version do you have? Nested arrays were not feeling too swift
in
2.0.
-Original Message-
From: Drew Hite [mailto
@incubator.apache.org
Subject: RE: Aegis and JAXB-WS
I don't think so; AFAICT this is a WSDL that *he* created manually,
no?
Glen
Am Mittwoch, den 05.09.2007, 13:01 -0400 schrieb Benson Margulies:
Let's open a JIRA that CXF should create a TNS prefix and use it.
-Original Message-
From: Glen
more readable than ns1 for
the target namespace.
Glen
Am Mittwoch, den 05.09.2007, 13:18 -0400 schrieb Benson Margulies:
I'm changing the subject, sorry. I happened to notice yesterday
that
when it *is* CXF that generates, it lets targetNamespace items
fall
into ns1
This patch consists of installing the namespace map into the XmlSchema
object. Apparently, the author of AegisDatabinding thought that the
commons code would do this sensible thing for itself.
I would be most grateful for a snapshot with this fix in it.
I did not propose any change to
cranky at 11pm.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2007 12:13 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: wsdl2java and faults
Benson,
The message parameter is used to set the faultString element
Can I sell you a patch to introduce 1.5 generics in place of Object
(semi-serious)? This looks very interesting, thanks.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2007 12:05 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
The question about thread pools leads me to ask a dumb question:
definitionally, are SEI classes required to be reentrant? It seems from
this thread that the default behavior includes entry in multiple jetty
threads.
The objects generated by wsdl2java for faults seem unnecessarily clumsy.
I get a POJO + annotations that corresponds to the fault type. Call it
'X'.
Then I get XFault.
To construct an XFault over a Throwable, I need to provide a message ---
(String message, X x, Throwable cause)
This is perhaps really a spring question, but the readers of this list
must have hit this before.
SEI classes are reentrant.
CXF services are frequently deployed in Spring and constructed with
Spring-managed beans.
Spring doesn't seem to offer much in the multithreading department.
I tried something like this once in an effort to take control of
namespace prefix selection. I failed. However, it looks here as if the
protocol facilitates what you want here, unlike (sadly) what I wanted.
-Original Message-
From: Dan Diephouse [mailto:[EMAIL PROTECTED]
Sent: Monday,
We've decided to just maintain a 'union' class that has get methods for
all the possible items that can get into the map.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, August 24, 2007 1:11 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
201 - 300 of 355 matches
Mail list logo
