Solved....

1. Re-deployed the Archive Generator plugin (new download)
2. Re-attached all jar's required for WS (I removed all the suggestions
given by the wizard (from previous processes))
3. Re-exported project JAR (since certain custom built packages were
required by the WS)
4. Re-started JBoss
5. Re-deployed Axis2
6. Uploaded AAR

Worked perfectly well!

I guess it was an issue of JAR files refresh!

Thanks Sietse for your interest.

Chris



cporter wrote:
> 
> Hi Sietse,
> 
> First of all I thank you for your reply... 
> 
> So...
> 
> 1) The AAR is surely the newly generated one
> 2) I use the Axis2 Eclipse plugin to do that process (I am a bit sceptic
> about it, somehow)
> 3) I restarted JBoss several times... in vain.
> 
> Incredible! It's fascinating to see results coming out of inexistent code!
> :-/
> 
> I thank you for your opinion.... maybe someone has had the same situation.
> 
> Chris
> 
> 
> sietsenicolaas.tenhoeve wrote:
>> 
>> Hello Chris,
>> 
>> I don't know JBoss but that's maybe not relevant. 
>> My ideas about this are the following:
>> - Does the server logs say anything about new deployed services?
>> - Is the provided aar the new one? (Do you use a buildtool which
>> automates this process?)
>> - Do you have the same problem in the test environment?
>> - Have you tried to restart JBoss?
>> 
>> I know this is not an answer on your question, but maybe these points
>> help you.
>> 
>> Regards,
>> Sietse
>> 
>> -----Original Message-----
>> From: cporter [mailto:[EMAIL PROTECTED] 
>> Sent: 05 December 2007 13:06
>> To: [email protected]
>> Subject: Axis2 phantom webservice!
>> 
>> 
>> Hello all,
>> 
>> I have been trying to find the root of my problem for 3 days now, all in
>> vain. I am sure it is some detail which I might be overlooking here, and
>> I hope that someone out there would be able to enlighten me.
>> 
>> The situation is as follows:
>> 
>> 1) JBoss server (with Axis2 hot deployed and archive uploaded through
>> Axis2's admin pages).
>> 2) Webservice returns a simple XML structure
>> 
>> Suddenly, changes on a particular webservice (after compiling,
>> generating AAR and uploading), are not being reproduced when called over
>> any client.
>> Even if I hard code the return value e.g. to null or empty Element, it
>> still somehow provides me with the old (original) return values.
>> 
>> One of the behaviors I am noticing, which obviously is rising some
>> questions is that when I deploy the web service (through Axis2 Admin), I
>> get 2 deployment messages (2 seconds apart) from the JBoss console
>> window.
>> 
>> It seems that there is an old version of my webservice being deployed
>> with Axis2. Is that possible? And if so, how can I go about solving the
>> problem?
>> 
>> On my side, I have tried the following:
>> 1) Remove ALL bin folders, and recompiled all my code
>> 2) Removed all relevant archives (.aar) (even from JBoss tmp folders)
>> and regenerated from newly compiled classes
>> 3) Tested the modified service (successfully) through static debugging,
>> and the results are as desired. But somehow, when I generate an archive
>> and publish the web service, the old web service comes to life (as if a
>> phantom WS).
>> 
>> I appreciate some feedback.
>> 
>> Best Regards,
>> 
>> Chris Porter
>> 
>> 
>> 
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2-phantom-webservice%21-tf4949452.html#a141710
>> 33
>> Sent from the Axis - User mailing list archive at Nabble.com.
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Axis2-phantom-webservice%21-tf4949452.html#a14177709
Sent from the Axis - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to