Doug,
Thanks for the reply. Couple things -- first, @UriParam is now
apparently @PathParam. Additionally, I cannot get the paths to work. I
repeatedly get Tomcat errors that there's No operation matching
request path..., and others like itstill a black artI'd love
to get this
Hi,
I have an interesting case binding/marshalling complex types using the 2.1
snapshot. A NullPointer is thrown [in NamespaceHelper.getPrefix() ] when I
used AegisDataBinding but it works perfectly fine when I use JAXB (see the
comment me to use JAXB line in the server client).
Question: Do I
On Sun, 6 Apr 2008, Brad O'Hearne wrote:
Thanks for the reply. Couple things -- first, @UriParam is now
apparently @PathParam. Additionally, I cannot get the paths to work. I
repeatedly get Tomcat errors that there's No operation matching
request path..., and others like itstill a black
Hi
@Path replaces @UriTemplate and @PathParam replaces @UriParam,
I'm wondering why you have no compilation issues with jsr-311-api 0.6 if
use still can use @UriParam ? May be jsr-311-api 0.5 is also on a class
path ?
Cheers, Sergey
-Original Message-
From: Doug [mailto:[EMAIL
Doug,
Thanks for the reply. I'm still getting the same errors, going to show
you exactly what happens in my implementation. Here is my web.xml:
!DOCTYPE web-app
PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
http://java.sun.com/dtd/web-app_2_3.dtd;
web-app
Aegis does not support unqualified schema. However, it should have just made
up one for you. Please post a JIRA.
On Sun, Apr 6, 2008 at 2:40 AM, Judes Tumuhairwe [EMAIL PROTECTED]
wrote:
Hi,
I have an interesting case binding/marshalling complex types using the 2.1
snapshot. A NullPointer is
Did you enable validation?
On Fri, Apr 4, 2008 at 4:30 PM, Web Man [EMAIL PROTECTED] wrote:
When a SOAP request is submitted without the closing /soapenv:Envelope,
the
Web Service is called and no errors are thrown.
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
Maybe the annotations have to go in the implementation class
instead/as well? I didn't use an interface - just an instantiatable
class (with method bodies).
Apart from broken POST data, thats the only other thing I can think of.
Doug
On Mon, 7 Apr 2008, Brad O'Hearne wrote:
Doug,
Thanks
I have not worked with this type of problem before. Possible guesses:
1.) Anything in our WebLogic docs[1] that may be relevant for your
problem?
2.) We have two types of configuration for web services--via a
cxf-servlet.xml file and directly through Spring configuration[2]. If
you try the
