Re: Java2WSDL error....!

2004-01-23 Thread siva kondapalli
Hi,
 Iam still couldnt fix my problem,and getting the below mentioned error..,
Can anyone please help me to fix this...,

Exception in thread "main" java.lang.NoClassDefFoundError: javax/wsdl/extensions/soap/SOAPFault at org.apache.axis.wsdl.Java2WSDL.createEmitter(Java2WSDL.java:236) at org.apache.axis.wsdl.Java2WSDL.init(Java2WSDL.java:228) at org.apache.axis.wsdl.Java2WSDL.main(Java2WSDL.java:541)


Thanks 
Rao.,
siva kondapalli [EMAIL PROTECTED] wrote:

Hi,
 Adding to my previous question..,i found somewhere in the User's list(http://www.mail-archive.com/[EMAIL PROTECTED]/msg04385.html) that we need to have "WSDL4j.jar" from IBM now and Axis is no more supporting.
Can anyone calrify that..,and also why iam getting that error..?

Thanks 
Rao.,
siva kondapalli [EMAIL PROTECTED] wrote:

Hi, I tried using Java2WSDL from the Samples directory for the example "example6" and endup with the error Exception in thread "main" java.lang.NoClassDefFoundError: javax/wsdl/extensions /soap/SOAPFault at org.apache.axis.wsdl.Java2WSDL.createEmitter(Java2WSDL.java:236) at org.apache.axis.wsdl.Java2WSDL.init(Java2WSDL.java:228) at org.apache.axis.wsdl.Java2WSDL.main(Java2WSDL.java:541)

Any hlep will be appreciated...

Thanks in advanceRao.,
 


Do you Yahoo!?Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes


Do you Yahoo!?Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!

Axis C++ and Tomcat

2004-01-23 Thread Kavita Ashok Sukerkar
Hi,

  I currently have apache and tomcat working together (with a jk
connector) and I've been successfully using Axis (for Java) to invoke
Java methods, but want to do the same for C++.  I attempted to install
axis C++ by following the docs online and failed; I think I need
something to install Axis C++ with tomcat+apache.  Are there any
links/books that one knows of that can help me with this?

Thanks,
 Kavita





Axis and Maven

2004-01-23 Thread luis . novais

Hi all,

Have any of you already created a project were used maven and axis?
I'm considering that possibility now, but there are issues like the generation of java 
from wsdl, which requires some work, like creating a plugin!

Does any of you already had to battle with this?


Thanks 
Luis Novais

Re: Axis and Maven

2004-01-23 Thread __matthewHawthorne
[EMAIL PROTECTED] wrote:
 Have any of you already created a project were used maven and axis?
 I'm considering that possibility now, but there are issues like the
 generation of java from wsdl, which requires some work, like creating 
 a plugin!

 Does any of you already had to battle with this?

You shouldn't have to create a plugin unless you're into that sort of 
thing.

I'm not doing any generation using .wsdl, so I just wrote a maven.xml 
file that uses the axis-admin tasks to deploy and undeploy the service.

I'm sure that you could do the same, by adding the wsdl2java task to 
your maven.xml.  You could use it in a postgoal to java:compile maybe.



Re: Multiple Classes in the Same package

2004-01-23 Thread Sai Pradeep - Hotmail
Thanks to everyone who helped me, I resolved my problem. Just copy your
class files into your webapps/axis/classes/package name. It should work
when dealing with multiple classes in the same package.


- Original Message -
From: sai pradeep [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 7:44 PM
Subject: RE: Multiple Classes in the Same package


 Hi Shrikanth!

 I couldnt get this thing working. Well, Just have a look at my code and
 suggest me what to do.

 /*
 * WFlink.java
 *
 * Created on January 11, 2004, 2:52 AM
 */

 package test;

 public class WFlink {

 /** Creates a new instance of WFlink */
 public WFlink() {
 }

 public String get(String variable)
 {
 return variable+ +in WFLink;
 }

 public short put(String variable, String activity)
 {
 return 0;
 }

 public  void start(long wfType, long wfID, long procID)
 {
  
 }
 }


 /*
 * WFImpl.java
 *
 * Created on January 10, 2004, 6:45 PM
 */
 package test;

 public class WFImple {
 public void runWF(long wftype, long wfID, long procID) {
 WFlink wf = new WFlink();
 wf.start(wftype,wfID, procID);
 }

 public short putAct(String variable, String activity) {
 WFlink wf = new WFlink();
 short h = wf.put(variable,activity);
 return h;
 }

 public String getAct(String variable) {
 WFlink wf = new WFlink();
 String act = wf.get(variable);
 return act;
 }

 }


 WFImpl class is the one which has to be deployed on the server. I renamed
it
 as WFImpl.jws and deployed it on the AXIS service under
 tomcat/webapps/axis/test. I tried to place the WFLink class in the
 /WEB-INF/axis/test/ directory. But i still get the same message that 
Class
 WFLink could not be found. Please give me your valuable suggestions.

 Cheers
 Sai.

 _
 Games, MMS cards, ringtones. Operator logos, picture messages  more.
 http://server1.msn.co.in/sp03/mobilesms/ Jazz up your mobile!




Dynamic type serialization

2004-01-23 Thread Aaron Hamid
Hi all,

  Dims, Tom, Glen, I am {aaron} from Freenode.

Anyway, I am having problems implementing dynamic type serialization 
 under Axis.  I can probably best explain what I mean with an example:

Say we have some sort of opaque complex type as input and output 
messages to some soap call.  Let's also say I'm doing dynamic 
invocation.  That means I do not have proper 
serialization/deserialization stubs for the aforementioned opaque 
input/output types.  Is all lost?  No.  If I take a Map object, I can 
make a best-effort to serialize key/value pairs as elements in the 
opaque type.  Of course this is not going to be accurate, and without 
recursion will only work for one level of nesting, however, it is 
probably going to still catch a majority of cases (at least in my 
environment).

The problem is, that serialization and deserialization factories and 
TypeDescs, are mapped on Class.  This renders the above scheme 
impossible without some sort of ThreadLocal hacks.

Let's examine.  Let's say I create a new custom bean DynamicType. 
DynamicType, will take a Map object, inspect the map for key/value 
pairs, and expose those key/value pairs as ElementDescs in the 
TypeDesc it holds.  We will have to create a TypeDesc subclass that 
can store an explicitly constructed BeanPropertyDescriptor array, as 
the default TypeDesc implementation does implicit bean introspection 
(which of course will produce the wrong thing when introspecting a 
Map - it will just produce the interface of the Map object itself).

That is straightforward enough.  Since BeanSerializerFactory 
dynamically looks up the TypeDesc from the class it is passed, we must 
subclass BeanSerializerFactory (let's call it 
DynamicSerializerFactory) so that it takes a concrete instance of our 
aforementioned DynamicType, initialized with the Map object. 
Everything looks good so far - our DynamicSerializer factory will 
behave like a BeanSerializerFactory which produces Serializers for 
beans whose interface is that provided by the DynamicTypeDesc and 
explicit properties inspected in the Map.  Sounds good.

But now comes the catch.  We have to register this factory based on 
the _CLASS_ of input type - DynamicType.  However, if we register this 
specific factory instance for ALL DynamicType classes, we will 
inevitably produce the wrong interface at some point if this mapping 
gets overwritten with one initialized with a different concrete Map 
object.

The only solution I see is to go ahead and register our 
DynamicSerializerFactory, however, instead of keeping a member 
instance of DynamicTypeDesc, keep a ThreadLocal instance containing a 
DynamicTypeDesc, so that when we are called somewhere down the line in 
the invoke process we will produce the correct serializer for the 
interface provided by the correct DynamicType for THIS SPECIFIC 
invocation.

HOWEVER this is a big hack, and relies on the assumption that the 
invocation dispatching thread is the SAME THREAD in which we map the 
factory.

So my question is:

1) does this make sense
2) is there any way around it, or better way to implement what I want 
that I haven't found
3) does, in fact, the invocation get executed by the same thread as 
the caller? (I /think/ so, but I don't want to assume this, as all 
sorts of things like thread pools, etc., could potentially be coming 
into play)


Re: JNI with AXIS - InvocationTargetException

2004-01-23 Thread Sai Pradeep - Hotmail



Hi All!

Thanks to everyone who gave their valuable 
suggestions and ideas in eliminating my exception. I resolved my exception 
successfully.

So, my suggestion for all those who want to invoke 
a JNI application from AXIS Service is as follows.

1. Check whether the JNI application works offline, 
I mean when it is not deployed on the Tomcat. If it works fine, 

2. then check whether you have copied the DLL and 
LIB files of your c/c++ application in your System path. i.e., in 
Windows/System32 folder. It is mandatory to copy both the DLL and LIB files in 
to this folder.If the files are not placed 
in the System path, you will get an InvocationTargetException.

Optional Check whether you have placed all 
the dependency classes, if you have anyin the webapps/axis/package 
name of your tomcat server.

Hope this works!!! Best of luck
Cheers
Sai.


FW: Unable to invoke the web services using SOAPscope tool.

2004-01-23 Thread Wagh, Shrikant








Hi Jim,



Here is the issues I logged on Nov 11, 2003, with Mindreef Support
team (Please take a look at the forwarded e-mail). The only reply I got so far
from MindReef Support Team is, they will look into the issue. You can check the
issues log yourself, if Mindreef maintains the customer issues. I never heard
anything from them afterwards (more than three months now). This again shows
how good their customer support is?



Please check the Mindreef customer issues
log. You will find all the information I sent to them, including WSDL file.
Test with that WSDL and let me know if it works. If it works with our WSDL then
only Ill be interested in trying the new 3.0 version, else I wont
be interested in spending my cycles.



Hope this makes very clear that my
comments are VERY true. Please do let me know if you hear anything about
the issue I logged from your customer support.



Best regards,



HPP/eProfile QA Lead. HP



For
those who are interested in Web Services testing:

-

I found
that WebServiceTester from Optimyz software is a very good tool for testing any
types of web services, and I'm great fan of this tool. It supports all types of
web services, and all simple and complex types and it very usable than any
other tool in the market I ever used/evaluated. It automatically generates the
SOAP requests and invokes the intended web services. It can perform functional,
regression and load testing of web services. Result analysis and status
reporting is just wonderful. I'll highly recommend this tool for testing
web services, saves lots of time and efforts in testing web services. For more
information visit http://www.optimyz.com. 



DISCLAIMER




THESE
ARE MY PERSONAL VIEWS/OPINIONS AND DOES NOT REPRESENT HP, AND THE INFORMATION
PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE I/HP BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS INFORMATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 

=





-Original Message-
From: Wagh, Shrikant 
Sent: Monday, December 01, 2003
12:09 PM
To: '[EMAIL PROTECTED]'
Cc: Wagh, Shrikant
Subject: Unable to invoke the web
services using SOAPscope tool.



Hi SOAPscope Support team,I have been evaluating the SOAPscope tool to test our web services and WSDL file. Im unable to invoke our web services using SOAPscope tool. Please find the attached WSDL file for your reference. When I analyzed this WSDL file, it reported no errors and the WSDL is found to be correct. In Service View screen it does display the correct operation signatures. I also attached the request generated by SOAPscope and the received error message when I tried to invoke the web service, at the end of this email.The same WSDL when tested with other testing tools like WebServiceTester, it works fine.The web services described in WSDL file are document-literal and take the XML document as input argument and returns the XML document. I found that the SOAP request body has the wrapper element eprofile:eCreateProfile. May I know the reason WHY the XML document passed as input argument is wrapped in eprofile:eCreateProfile element.If the input is null then the body part of the request should be soap:Body /soap:Bodyand NOT soap:Body eprofile:createProfile/ /soap:BodyIf the input is docvalval1/val/doc then the body part of the request should be soap:Body docvalval1/val/doc /soap:Bodyand NOT soap:Body eprofile:createProfile  docvalval1/val/doc /eprofile:createProfile /soap:BodyI also noticed that the request generated by Axis Client does not have the wrapper element as it is in the request generated by SOAPscope.Ill highly appreciate your response to this email.Best regards,Shrikant WaghHPP/eProfile QA LeadHewlett Packard Company.Request generated by SOAPscope--?xml version=1.0 encoding=UTF-8?soap:Envelope xmlns:eprofile=http://eprofile.globalops.hp.com/eProfileService xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/ xmlns:xs=http://www.w3.org/2001/XMLSchema soap:Header eprofile:eProfileHeader ApplicationID111/ApplicationID LanguageCode111/LanguageCode HPPID111/HPPID SiteMinderSID111/SiteMinderSID TemplateID111/TemplateID /eprofile:eProfileHeader /soap:Header soap:Body eprofile:createProfile/ /soap:Body/soap:Envelope





Response

---

Malformed XML: 

Line: 4, Column: 

RE: Axis and Basic Profile 1.0a

2004-01-23 Thread Wagh, Shrikant
Hi Jim,

Here is the issues I logged on Nov 11, 2003, with Mindreef Support team
(Please take alook at the forwarded e-mail). The only reply I got so far
from MindReef Support Team is, they will look into the issue. You can
check the issues log yourself, if Mindreef maintains the customer
issues. I never heard anything from them afterwards (more than three
months now). This again shows how good their customer support is?

Please check the Mindreef customer issues log. You will find all the
information I sent to them, including WSDL file. Test with that WSDL and
let me know if it works. If it works with our WSDL then only I'll be
interested in trying the new 3.0 version, else I won't be interested in
spending my cycles.

Hope this makes very clear that my comments are VERY true.  Please do
let me know if you hear anything about the issue I logged from your
customer support.

Best regards,

HPP/eProfile QA Lead. HP

For those who are interested in Web Services testing:
-
I found that WebServiceTester from Optimyz software is a very good tool
for testing any types of web services, and I'm great fan of this tool.
It supports all types of web services, and all simple and complex types
and it very usable than any other tool in the market I ever
used/evaluated. It automatically generates the SOAP requests and invokes
the intended web services. It can perform functional, regression and
load testing of web services. Result analysis and status reporting is
just wonderful.  I'll highly recommend this tool for testing web
services, saves lots of time and efforts in testing web services. For
more information visit http://www.optimyz.com. 

DISCLAIMER 

THESE ARE MY PERSONAL VIEWS/OPINIONS AND DOES NOT REPRESENT HP, AND THE
INFORMATION PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL
THE I/HP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
INFORMATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 
=


-Original Message-
From: Wagh, Shrikant 
Sent: Monday, December 01, 2003 12:09 PM
To: '[EMAIL PROTECTED]'
Cc: Wagh, Shrikant
Subject: Unable to invoke the web services using SOAPscope tool.

Hi SOAPscope Support team,
 
I have been evaluating the SOAPscope tool to test our web services and
WSDL file. I'm unable to invoke our web services using SOAPscope tool.
Please find the attached WSDL file for your reference. When I analyzed
this WSDL file, it reported no errors and the WSDL is found to be
correct. In Service View screen it does display the correct operation
signatures. I also attached the request generated by SOAPscope and the
received error message when I tried to invoke the web service, at the
end of this email.
 
The same WSDL when tested with other testing tools like
WebServiceTester, it works fine.
 
The web services described in WSDL file are document-literal and take
the XML document as input argument and returns the XML document. I found
that the SOAP request body has the wrapper element
eprofile:eCreateProfile. 
May I know the reason WHY the XML document passed as input argument is
wrapped in eprofile:eCreateProfile element.
 
If the input is null then the body part of the request should be
   soap:Body
   /soap:Body
 
and NOT
 
   soap:Body
  eprofile:createProfile/
   /soap:Body
 
If the input is docvalval1/val/doc then the body part of the
request should be
   soap:Body
docvalval1/val/doc
   /soap:Body
 
and NOT
 
   soap:Body
eprofile:createProfile
docvalval1/val/doc
/eprofile:createProfile
   /soap:Body
 
I also noticed that the request generated by Axis Client does not have
the wrapper element as it is in the request generated by SOAPscope.
 
I'll highly appreciate your response to this email.
 
Best regards,
Shrikant Wagh
HPP/eProfile QA Lead
Hewlett Packard Company.
 
Request generated by SOAPscope
--
?xml version=1.0 encoding=UTF-8?
soap:Envelope
   xmlns:eprofile=http://eprofile.globalops.hp.com/eProfileService;
   xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
   soap:Header
  eprofile:eProfileHeader
 ApplicationID111/ApplicationID
 LanguageCode111/LanguageCode
 HPPID111/HPPID
 SiteMinderSID111/SiteMinderSID
 TemplateID111/TemplateID
  

Problems with Axis generated Java beans from XSD

2004-01-23 Thread Marepalli, Somesh








Hi:

 I am using a WSDL (which refers to an XSD) to generate
the skeleton code for web services

 Axis is generating bean classes correctly for the most
part. However, its generating some bean classes prefixed with an _
and this creates problems when I try to deploy the web service. For classes starting
with an _, the generated deploy.wsdd file has occurrences of _
replaced with a  in the typeMapping entries and the service
is not deployed correctly.



 What rules does Axis follow to decide what beans to
generate? I would assume only the ones needed by operations (and their dependencies)
would be generated. I cant understand the generation of certain bean
classes and I dont know why some are named the way they are (starting
with a _). 



 Is there a way to correct this?



Somesh Marepalli

[EMAIL PROTECTED]










Re: Serializer/Handler/Provider Usage

2004-01-23 Thread Chris Haddad

Hi brian -

if i remember correctly, the scenario that led you to create a provider
was to format the SOAP body in a specific fashion.  IMHO, if everyone
agreed to doc/literal conventions and WS-I guidelines, you wouldn't have
to perform such tricks.

Handlers are used for processing of SOAP headers. For example, to process
infrastructure related directives related to security, reliability, and
transactions.  An analogy, concepts handled by the J2EE container would be
formatted as SOAP headers. Handlers may rely in the serialization framework to convert 
XML objects into native
Java objects.

The serialization framework is used to convert to/from XML and Java.  The
framework currently has to support SOAP Section 5 encoding as well as
literal encoding of SOAP elements. Additionally, in the web services
platform, Axis code, there is a need to be able to map WSDL
descriptions of service operations and messages to actual Java objects..

all in all pretty complicated interactions at times..


hope this helps,

/Chris
http://www.sys-con.com/story/?storyid=37968
http://cvs.apache.org/~haddadc



On Wed, 21 Jan 2004, Brian Abbott wrote:

 Hi,



 I was wondering if anyone could give me a good overview of when
 to use a serializer vs a handler vs a provider. I had a very specific
 sequence of XML that I needed placed in a RPC response and ultimately ended
 up writing a provider for it. By the way, I noticed a while back that
 someone had mentioned registering a provider in a file
 (org.apache.axis.deployment.wsdd.Provider) however, I think a better way is
 to call WSDDProvider.registerProvider(QName, WSDDProvider). Anyway, this had
 me thinking, it's not very clear when the appropriate time to use a
 serializer or a handler or a provider is. Does anyone have any good
 information on this?



 Thanks



 Brian Abbott




RE: Newbie: TestClient example does not work

2004-01-23 Thread Galbreath, Mark A
Why would this be necessary?  If the axis and xml jar files are in
WEB-INF-lib and %AXISCLASSPATH% and samples.userguide.example1.TestClient is
at WEB-INF/classes/samples/userguide/example1/TestClient.class, why would
changing the package namespace be needed?

Further, I got the Java runtime to invoke TestClient, but now it's
complaining of not being able to find an import:
org.apache.axis.client.Service when I

java samples.userguide.example1.TestClient

from /WEB-INF, and if I

java -cp %AXISCLASSPATH% samples.userguide.example1.TestClient

it complains of not being able to find TestClient.

This is really screwed up

Mark

-Original Message-
From: mahen perera [mailto:[EMAIL PROTECTED]
Sent: Friday, January 23, 2004 1:16 AM
To: [EMAIL PROTECTED]
Subject: RE: Newbie: TestClient example does not work


check the package declaration of the Test Client class. If it is

package samples.userguide.example1

then u must add to the classpath variable axis/1.1/
or whatever the directory under which the samples directory is placed. Not 
the
samples\userguide\example1\TestClient path,
and then run using java samples.userguide.example1.TestClient


From: Galbreath, Mark A [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Axis (E-mail) [EMAIL PROTECTED]
Subject: Newbie: TestClient example does not work
Date: Thu, 22 Jan 2004 15:18:51 -0500

Anybody know why I'm getting a ClassDefNotFound exception when I try to run
the TestClient example under Basics - Getting Started at
http://ws.apache.org/axis/java/user-guide.html?  I've even tried

c:\[axis] java -cp %AXISCLASSPATH% samples\userguide\example1\TestClient

and the JVM keeps whining about not being able to find the class.  Clue me?

tia,
Mark

_
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus
application/ms-tnef