Jana,
I run a TestNG test, but I must admit that I found some code on the
Internet that showed how to run Embedded Tomcat (5.5) and I use that
for testing a service. You only need some jars and a directory and you
can test the web service. The TestNG test runs a test client and hits
the Embedded
My current test for Axis2-Std-1.0 is to run my end-to-end web service
generation, which builds the service archive and jar, deploys them to
a directory for Embedded Tomcat, runs Tomcat, hits it from the test
client within the TestNG test. I still am seeing the same error with
the daily build for
PROTECTED] wrote:
Hi Jim
Two things
- is this happen in current code base or Axis2 1.0
- any possibility of helping me to regenerate the problem
( I mean can you give me the source file so that I can test.)
Jim Bender wrote:
Deepal,
The main problem is that when I run Java2WSDL
,
Jim
On 6/26/06, Jim Bender [EMAIL PROTECTED] wrote:
Deepal,
The example works with Axis2 0.93, if the interface provided to the
generator is in the default package (otherwise, uncompilable code is
produced). The problem still occurred with the Axis2 Std 1.0 release
and daily builds up
I have been stepping through code in the debugger in Eclipse, to see
if I can tell why there are duplicate complex type definitions for my
parameter class (there is an import in the Java interface and then the
type is used as a parameter to the one method).
The situation seems to be that the
I don't know the precise step, but by the time that we leave the
generateOM() method in the Java2OMBuilder, there are two complex type
definitions in the WSDL.
public OMElement generateOM() throws Exception {
OMFactory fac = OMAbstractFactory.getOMFactory();
wsdl =
immediately by telephone or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: Jim Bender [EMAIL PROTECTED]
To: axis-user@ws.apache.org; Martin Gainty [EMAIL PROTECTED]
Sent: Saturday, June 24, 2006 8:47 AM
Subject: Re: I am ready to create
Unless someone can give a good explanation why I should not, I will
create a new JIRA issue about what I am seeing when trying to use a generated
stub in my test client:
Caught Throwable exception in runPointsCalculator:
org.apache.axiom.om.OMException:
sure that Anne is correct in
what she says, as she knows a great deal more than I do about WSDL,
but the duplicate complex type is what I wrote the JIRA issue about.
Regards,
Jim
On 6/21/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi Jim
pls see my comments below;
Jim Bender wrote
I have been working through issues with building the jar file to
deploy to Tomcat.
I am able to run, with classpath issues solved (seemingly).
I am getting an IllegalStateException, again, from the test client,
when trying to execute the web service deployed to Embedded Tomcat.
Points
I looked down the Eclipse console and saw this, which is relevant to
the problem:
Caused by: java.lang.IllegalStateException
at
org.apache.xmlbeans.impl.store.Jsr173$XMLStreamReaderForString.next(Jsr173.java:1110)
at
Robert,
I suppose that you have tried adding to the run configuration for the test?
You probably know all this and tried it already, but here goes.
Forgive me for being redundant and obvious.
On one TestNG test I have for the end-to-end building of the web
service and testing with Embedded
I was not having this problem with the Axis2 0.93 build, but with the
latest daily build (and that from a week ago, I am not getting the XML
Beans classes generated (such as
schemaorg_apache_xmlbeans.system.sD926C795A3FD513AB921640BAE58ADC6.TypeSystemHolder).
I thought that I was still doing the
I looked into my generated jar, and can see that the TypeSystemHolder
is there, but in a different package than the other code expects:
schemaorg_apache_xmlbeans.system.s00EEDBA506EBCBE06D4AFD9DBBF45729.TypeSystemHolder.
That tells me it is just a classpath issue, and the testclient is
pointing
I made further progress by fixing my classpath.
I am running from a TestNG test class.
Now, while trying to run the Axis2 client, in the test, I am seeing
this exception thrown with an IllegalStateException:
Points Calculation, firing...
Caught Throwable exception in runPointsCalculator:
I am having a good bit of success using the daily build from Monday.
I will update to a more recent one, next Monday.
In my test client, I am getting an error that I have not seen before:
Caught Throwable exception in runPointsCalculator:
java.lang.ExceptionInInitializerErrorjava.lang.Ex
I tried the WSDL2Java generation with a WSDL file that I generated
with this build, and it worked. That was only after I edited the file
and removed the duplicate complex type definition. Now, I am seem to
be getting the full set of generated files. I need to complete the
process and see if the
from the imported namespace, I don't understand
why you import the namespace. I would assume that you want to reference the
element defined in your schema. See my response to one of your other posts
for an updated and corrected WSDL file.
Anne
On 6/8/06, Jim Bender [EMAIL PROTECTED] wrote:
Deepal
It appears that the Axis2 Std 1.0 WSDL file generation from a Java
interface is hard-wired to set the elementFormDefault to
unqualified.
By not setting
// java2WsdlBuilder.setSchemaTargetNamespace();
// java2WsdlBuilder.setSchemaTargetNamespacePrefix();
in the Java2WSDLBuilder, I was able to
I ran the WSDL2Java generator on the WSDL file that I had generated
and got an exception thrown that was caught at line 117 in the
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.
The message in the exception says:
Schema for namespace 'http://testexamples/xsd' already contains type
I am running the WSDL2Java main with arguments, and
CodeGenerationEngine.getBaseUTI(currentURI) is doing bad things to
the file URI I have passed as an argument. My URI is generated
by using File.toURI(path);
This is what I am getting. I have been experimenting, but to no avail.
This is the arg
Perhaps part of my issue with being able to generate a parsable WSDL file
from Java2WSDL is the parameters I am using. I have attached the generated file,
and these are the parameters that I am using in the generator.
I also attached (again) the FoodDescription class for this toy example, as
well
I suspect that I need to regenerate the WSDL file for my toy example
and debug the WSDL2Java to find out what the issue is that I had
been seeing. I had deleted an element that may need to be there for
the WSDL2Java to work.
Regards,
Jim
, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
forward with correct prefix
Jim Bender wrote:
I hand-edited the wsdl file generated from the Java2WSDL process to
remove the duplicate complex type definition and skipped WSDL
generation. What I ended up with was a skeleton for a
non-document
I had been running the WSDL2Java generator from Leafcutter, using the
Java Ant task.
I switched to building an arg array and running the main(String[])
programmatically,
so I can see what is happening. I have been able to make some progress that
way, along with trying to get a closer reading of
I am trying to convert my code to use Axis2 Std 1.0 instead of 0.93.
The various pieces are all done programmatically, rather than using the plugin,
as this is for a product.
The Java2WSDL runs without breaking in 1.0, but generates an incorrect file.
The toy example I am using uses a complex
26 matches
Mail list logo
