subject:"SOApMonitor"

Please read the manual, that's not the way applets work.

HTH,
Robert

On Dec 4, 2007 10:57 PM, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
> The applet classes are in my WEB-INF\classes. The listing is like:
>
> ...\WEB-INF\classes>ls
> SOAPMonitorApplet$SOAPMonitorData.classlog4j.xml
> SOAPMonitorApplet$SOAPMonitorFilter.class  org
> SOAPMonitorApplet$SOAPMonitorPage.class
> SOAPMonitorApplet$SOAPMonitorTableModel.class
> SOAPMonitorApplet$SOAPMonitorTextArea.class
> SOAPMonitorApplet$ServiceFilterPanel.class
> SOAPMonitorApplet.class
> com
>
> I have done away with the soapmonitor jar and have deleted the applet and 
> servlet classes from the soapmonitor mar to avoid duplication.
>
>
> Thanks,
>
> Vish.
>
> >-Original Message-
> >From: robert lazarski [mailto:[EMAIL PROTECTED]
> >Sent: Tuesday, December 04, 2007 7:50 PM
> >To: axis-user@ws.apache.org
> >Subject: Re: [Axis2] 1.3 Soapmonitor problem
> >
> >Argh!
> >
> >/tomcat/webapps/ROOT> ls
> >
> >HTH,
> >Robert
> >
> >On Dec 4, 2007 10:49 PM, robert lazarski <[EMAIL PROTECTED]> wrote:
> >> Eh, late here - my bad. You overwrote webapps/ROOT ? In that case, you
> >> need something like:
> >>
> >> /tomcat/webapps/axis2> ls
> >> axis2-web
> >> SOAPMonitorApplet$SOAPMonitorData.class
> >> META-INF
> >> SOAPMonitorApplet$SOAPMonitorFilter.class
> >> org
> >> SOAPMonitorApplet$SOAPMonitorPage.class
> >> soapmonitor-1.3-RC3.jar
> >> SOAPMonitorApplet$SOAPMonitorTableModel.class
> >> SOAPMonitorApplet.class
> >> SOAPMonitorApplet$SOAPMonitorTextArea.class
> >> SOAPMonitorApplet$ServiceFilterPanel.class  WEB-INF
> >>
> >> HTH,
> >> Robert
> >>
> >>
> >> On Dec 4, 2007 10:44 PM, robert lazarski <[EMAIL PROTECTED]>
> >wrote:
> >> > Even with a webroot exploded, you still need the url in the form of
> >> > whatever you put in 'Context path' , ie:
> >> >
> >> > http://localhost:8080/mycontextPath/SOAPMonitor
> >> >
> >> > Alternatively. you could try getting the soap monitor working with the
> >> > axis2 war first.
> >> >
> >> > HTH,
> >> > Robert
> >> >
> >> >
> >> > On Dec 4, 2007 10:35 PM, Pantvaidya, Vishwajit <[EMAIL PROTECTED]>
> >wrote:
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > I have deployed soapmonitor into my axis1.3 installation to test my
> >axis2
> >> > > and .NET websvc interaction issues. I followed all config steps as
> >mentioned
> >> > > in the soapmonitor doc (one slight difference - deployed in webroot
> >in an
> >> > > exploded format, so that soapmonitor is access as
> >> > > http://localhost:8080/SOAPMonitor).
> >> > >
> >> > >
> >> > >
> >> > > When I invoke the SOAPMonitor using this URL, I get the exception
> >> > > "java.lang.ClassFormatError: Truncated class file".
> >> > >
> >> > > I researched and saw following probably causes:
> >> > >
> >> > > -  due to problem unzipping the classes from jar at runtime
> >> > >
> >> > > -  due to inability to access classes from WEB-INF
> >> > >
> >> > > To remedy this I tried moving jar elsewhere (away from WEB-INF) to
> >adding
> >> > > the applet source to my Eclipse - nothing worked.
> >> > >
> >> > >
> >> > >
> >> > > Does anyone know what could be the reason for this?
> >> > >
> >> > >
> >> > >
> >> > > Full java console log is as follows:
> >> > >
> >> > >
> >> > >
> >> > > Java Plug-in 1.5.0_12
> >> > >
> >> > > Using JRE version 1.5.0_12 Java HotSpot(TM) Client VM
> >> > >
> >> > > User home directory = C:\Documents and Settings\vpantvai
> >> > >
> >> > > network: Loading user-defined proxy configuration ...
> >> > >
> >> > > network: Done.
> >> > >
> >> > > network: Loading proxy configuration from Internet Explorer ...
> >> > >
> >> > > network: Done.
> >> >

RE: [Axis2] 1.3 Soapmonitor problem

2007-12-04 Thread Pantvaidya, Vishwajit

The applet classes are in my WEB-INF\classes. The listing is like:

...\WEB-INF\classes>ls
SOAPMonitorApplet$SOAPMonitorData.classlog4j.xml
SOAPMonitorApplet$SOAPMonitorFilter.class  org
SOAPMonitorApplet$SOAPMonitorPage.class
SOAPMonitorApplet$SOAPMonitorTableModel.class
SOAPMonitorApplet$SOAPMonitorTextArea.class
SOAPMonitorApplet$ServiceFilterPanel.class
SOAPMonitorApplet.class
com

I have done away with the soapmonitor jar and have deleted the applet and 
servlet classes from the soapmonitor mar to avoid duplication.


Thanks,

Vish.

>-Original Message-
>From: robert lazarski [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, December 04, 2007 7:50 PM
>To: axis-user@ws.apache.org
>Subject: Re: [Axis2] 1.3 Soapmonitor problem
>
>Argh!
>
>/tomcat/webapps/ROOT> ls
>
>HTH,
>Robert
>
>On Dec 4, 2007 10:49 PM, robert lazarski <[EMAIL PROTECTED]> wrote:
>> Eh, late here - my bad. You overwrote webapps/ROOT ? In that case, you
>> need something like:
>>
>> /tomcat/webapps/axis2> ls
>> axis2-web
>> SOAPMonitorApplet$SOAPMonitorData.class
>> META-INF
>> SOAPMonitorApplet$SOAPMonitorFilter.class
>> org
>> SOAPMonitorApplet$SOAPMonitorPage.class
>> soapmonitor-1.3-RC3.jar
>> SOAPMonitorApplet$SOAPMonitorTableModel.class
>> SOAPMonitorApplet.class
>> SOAPMonitorApplet$SOAPMonitorTextArea.class
>> SOAPMonitorApplet$ServiceFilterPanel.class  WEB-INF
>>
>> HTH,
>> Robert
>>
>>
>> On Dec 4, 2007 10:44 PM, robert lazarski <[EMAIL PROTECTED]>
>wrote:
>> > Even with a webroot exploded, you still need the url in the form of
>> > whatever you put in 'Context path' , ie:
>> >
>> > http://localhost:8080/mycontextPath/SOAPMonitor
>> >
>> > Alternatively. you could try getting the soap monitor working with the
>> > axis2 war first.
>> >
>> > HTH,
>> > Robert
>> >
>> >
>> > On Dec 4, 2007 10:35 PM, Pantvaidya, Vishwajit <[EMAIL PROTECTED]>
>wrote:
>> > >
>> > >
>> > >
>> > >
>> > > I have deployed soapmonitor into my axis1.3 installation to test my
>axis2
>> > > and .NET websvc interaction issues. I followed all config steps as
>mentioned
>> > > in the soapmonitor doc (one slight difference - deployed in webroot
>in an
>> > > exploded format, so that soapmonitor is access as
>> > > http://localhost:8080/SOAPMonitor).
>> > >
>> > >
>> > >
>> > > When I invoke the SOAPMonitor using this URL, I get the exception
>> > > "java.lang.ClassFormatError: Truncated class file".
>> > >
>> > > I researched and saw following probably causes:
>> > >
>> > > -  due to problem unzipping the classes from jar at runtime
>> > >
>> > > -  due to inability to access classes from WEB-INF
>> > >
>> > > To remedy this I tried moving jar elsewhere (away from WEB-INF) to
>adding
>> > > the applet source to my Eclipse - nothing worked.
>> > >
>> > >
>> > >
>> > > Does anyone know what could be the reason for this?
>> > >
>> > >
>> > >
>> > > Full java console log is as follows:
>> > >
>> > >
>> > >
>> > > Java Plug-in 1.5.0_12
>> > >
>> > > Using JRE version 1.5.0_12 Java HotSpot(TM) Client VM
>> > >
>> > > User home directory = C:\Documents and Settings\vpantvai
>> > >
>> > > network: Loading user-defined proxy configuration ...
>> > >
>> > > network: Done.
>> > >
>> > > network: Loading proxy configuration from Internet Explorer ...
>> > >
>> > > network: Done.
>> > >
>> > > network: Loading direct proxy configuration ...
>> > >
>> > > network: Done.
>> > >
>> > > network: Proxy Configuration: No proxy
>> > >
>> > > basic: Cache is disabled by user
>> > >
>> > > basic: Plugin modality.register
>> > >
>> > > basic: Registered modality listener
>> > >
>> > > liveconnect: Invoking JS method: document
>> > >
>> > > liveconnect: Invoking JS method: URL
>> > >
>> > > basic: Referencing classloader: [EMAIL PROTECTED],
>> > > refcount=1
>> > >
>> > > basic: Added progress listener: [EMA

Re: [Axis2] 1.3 Soapmonitor problem

Argh!

/tomcat/webapps/ROOT> ls

HTH,
Robert

On Dec 4, 2007 10:49 PM, robert lazarski <[EMAIL PROTECTED]> wrote:
> Eh, late here - my bad. You overwrote webapps/ROOT ? In that case, you
> need something like:
>
> /tomcat/webapps/axis2> ls
> axis2-web
> SOAPMonitorApplet$SOAPMonitorData.class
> META-INF
> SOAPMonitorApplet$SOAPMonitorFilter.class
> org
> SOAPMonitorApplet$SOAPMonitorPage.class
> soapmonitor-1.3-RC3.jar
> SOAPMonitorApplet$SOAPMonitorTableModel.class
> SOAPMonitorApplet.class
> SOAPMonitorApplet$SOAPMonitorTextArea.class
> SOAPMonitorApplet$ServiceFilterPanel.class  WEB-INF
>
> HTH,
> Robert
>
>
> On Dec 4, 2007 10:44 PM, robert lazarski <[EMAIL PROTECTED]> wrote:
> > Even with a webroot exploded, you still need the url in the form of
> > whatever you put in 'Context path' , ie:
> >
> > http://localhost:8080/mycontextPath/SOAPMonitor
> >
> > Alternatively. you could try getting the soap monitor working with the
> > axis2 war first.
> >
> > HTH,
> > Robert
> >
> >
> > On Dec 4, 2007 10:35 PM, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >
> > >
> > > I have deployed soapmonitor into my axis1.3 installation to test my axis2
> > > and .NET websvc interaction issues. I followed all config steps as 
> > > mentioned
> > > in the soapmonitor doc (one slight difference - deployed in webroot in an
> > > exploded format, so that soapmonitor is access as
> > > http://localhost:8080/SOAPMonitor).
> > >
> > >
> > >
> > > When I invoke the SOAPMonitor using this URL, I get the exception
> > > "java.lang.ClassFormatError: Truncated class file".
> > >
> > > I researched and saw following probably causes:
> > >
> > > -  due to problem unzipping the classes from jar at runtime
> > >
> > > -  due to inability to access classes from WEB-INF
> > >
> > > To remedy this I tried moving jar elsewhere (away from WEB-INF) to adding
> > > the applet source to my Eclipse – nothing worked.
> > >
> > >
> > >
> > > Does anyone know what could be the reason for this?
> > >
> > >
> > >
> > > Full java console log is as follows:
> > >
> > >
> > >
> > > Java Plug-in 1.5.0_12
> > >
> > > Using JRE version 1.5.0_12 Java HotSpot(TM) Client VM
> > >
> > > User home directory = C:\Documents and Settings\vpantvai
> > >
> > > network: Loading user-defined proxy configuration ...
> > >
> > > network: Done.
> > >
> > > network: Loading proxy configuration from Internet Explorer ...
> > >
> > > network: Done.
> > >
> > > network: Loading direct proxy configuration ...
> > >
> > > network: Done.
> > >
> > > network: Proxy Configuration: No proxy
> > >
> > > basic: Cache is disabled by user
> > >
> > > basic: Plugin modality.register
> > >
> > > basic: Registered modality listener
> > >
> > > liveconnect: Invoking JS method: document
> > >
> > > liveconnect: Invoking JS method: URL
> > >
> > > basic: Referencing classloader: [EMAIL PROTECTED],
> > > refcount=1
> > >
> > > basic: Added progress listener: [EMAIL PROTECTED]
> > >
> > > basic: Loading applet ...
> > >
> > > basic: Initializing applet ...
> > >
> > > basic: Starting applet ...
> > >
> > > basic: Referencing classloader: [EMAIL PROTECTED],
> > > refcount=2
> > >
> > > basic: Releasing classloader: [EMAIL PROTECTED], refcount=1
> > >
> > > network: Connecting http://localhost:8080/SOAPMonitorApplet.class with
> > > proxy=DIRECT
> > >
> > > network: Connecting http://localhost:8080/SOAPMonitorApplet.class with
> > > cookie "JSESSIONID=1FAF54A700367497E0792833D0A411FC"
> > >
> > > java.lang.ClassFormatError: Truncated class file
> > >
> > > at java.lang.ClassLoader.defineClass1(Native Method)
> > >
> > > at java.lang.ClassLoader.defineClass(Unknown Source)
> > >
> > > at java.security.SecureClassLoader.defineClass(Unknown Source)
> > >
> > > at sun.applet.AppletClassLoader.findClass(Unknown Source)
> > >
> > > at java.lang.ClassLoader.loadClass(Unknown Source)
> > >
> > > at sun.applet.AppletClassLoader.loadClass(Unknown Source)
> > >
> > > at java.lang.ClassLoader.loadClass(Unknown Source)
> > >
> > > at sun.applet.AppletClassLoader.loadCode(Unknown Source)
> > >
> > > at sun.applet.AppletPanel.createApplet(Unknown Source)
> > >
> > > at sun.plugin.AppletViewer.createApplet(Unknown Source)
> > >
> > > at sun.applet.AppletPanel.runLoader(Unknown Source)
> > >
> > > at sun.applet.AppletPanel.run(Unknown Source)
> > >
> > > at java.lang.Thread.run(Unknown Source)
> >
>

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

Re: [Axis2] 1.3 Soapmonitor problem

Eh, late here - my bad. You overwrote webapps/ROOT ? In that case, you
need something like:

/tomcat/webapps/axis2> ls
axis2-web
SOAPMonitorApplet$SOAPMonitorData.class
META-INF
SOAPMonitorApplet$SOAPMonitorFilter.class
org
SOAPMonitorApplet$SOAPMonitorPage.class
soapmonitor-1.3-RC3.jar
SOAPMonitorApplet$SOAPMonitorTableModel.class
SOAPMonitorApplet.class
SOAPMonitorApplet$SOAPMonitorTextArea.class
SOAPMonitorApplet$ServiceFilterPanel.class  WEB-INF

HTH,
Robert

On Dec 4, 2007 10:44 PM, robert lazarski <[EMAIL PROTECTED]> wrote:
> Even with a webroot exploded, you still need the url in the form of
> whatever you put in 'Context path' , ie:
>
> http://localhost:8080/mycontextPath/SOAPMonitor
>
> Alternatively. you could try getting the soap monitor working with the
> axis2 war first.
>
> HTH,
> Robert
>
>
> On Dec 4, 2007 10:35 PM, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > I have deployed soapmonitor into my axis1.3 installation to test my axis2
> > and .NET websvc interaction issues. I followed all config steps as mentioned
> > in the soapmonitor doc (one slight difference - deployed in webroot in an
> > exploded format, so that soapmonitor is access as
> > http://localhost:8080/SOAPMonitor).
> >
> >
> >
> > When I invoke the SOAPMonitor using this URL, I get the exception
> > "java.lang.ClassFormatError: Truncated class file".
> >
> > I researched and saw following probably causes:
> >
> > -  due to problem unzipping the classes from jar at runtime
> >
> > -  due to inability to access classes from WEB-INF
> >
> > To remedy this I tried moving jar elsewhere (away from WEB-INF) to adding
> > the applet source to my Eclipse – nothing worked.
> >
> >
> >
> > Does anyone know what could be the reason for this?
> >
> >
> >
> > Full java console log is as follows:
> >
> >
> >
> > Java Plug-in 1.5.0_12
> >
> > Using JRE version 1.5.0_12 Java HotSpot(TM) Client VM
> >
> > User home directory = C:\Documents and Settings\vpantvai
> >
> > network: Loading user-defined proxy configuration ...
> >
> > network: Done.
> >
> > network: Loading proxy configuration from Internet Explorer ...
> >
> > network: Done.
> >
> > network: Loading direct proxy configuration ...
> >
> > network: Done.
> >
> > network: Proxy Configuration: No proxy
> >
> > basic: Cache is disabled by user
> >
> > basic: Plugin modality.register
> >
> > basic: Registered modality listener
> >
> > liveconnect: Invoking JS method: document
> >
> > liveconnect: Invoking JS method: URL
> >
> > basic: Referencing classloader: [EMAIL PROTECTED],
> > refcount=1
> >
> > basic: Added progress listener: [EMAIL PROTECTED]
> >
> > basic: Loading applet ...
> >
> > basic: Initializing applet ...
> >
> > basic: Starting applet ...
> >
> > basic: Referencing classloader: [EMAIL PROTECTED],
> > refcount=2
> >
> > basic: Releasing classloader: [EMAIL PROTECTED], refcount=1
> >
> > network: Connecting http://localhost:8080/SOAPMonitorApplet.class with
> > proxy=DIRECT
> >
> > network: Connecting http://localhost:8080/SOAPMonitorApplet.class with
> > cookie "JSESSIONID=1FAF54A700367497E0792833D0A411FC"
> >
> > java.lang.ClassFormatError: Truncated class file
> >
> > at java.lang.ClassLoader.defineClass1(Native Method)
> >
> > at java.lang.ClassLoader.defineClass(Unknown Source)
> >
> > at java.security.SecureClassLoader.defineClass(Unknown Source)
> >
> > at sun.applet.AppletClassLoader.findClass(Unknown Source)
> >
> > at java.lang.ClassLoader.loadClass(Unknown Source)
> >
> > at sun.applet.AppletClassLoader.loadClass(Unknown Source)
> >
> > at java.lang.ClassLoader.loadClass(Unknown Source)
> >
> > at sun.applet.AppletClassLoader.loadCode(Unknown Source)
> >
> > at sun.applet.AppletPanel.createApplet(Unknown Source)
> >
> > at sun.plugin.AppletViewer.createApplet(Unknown Source)
> >
> > at sun.applet.AppletPanel.runLoader(Unknown Source)
> >
> > at sun.applet.AppletPanel.run(Unknown Source)
> >
> > at java.lang.Thread.run(Unknown Source)
>

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

Re: [Axis2] 1.3 Soapmonitor problem

Even with a webroot exploded, you still need the url in the form of
whatever you put in 'Context path' , ie:

http://localhost:8080/mycontextPath/SOAPMonitor

Alternatively. you could try getting the soap monitor working with the
axis2 war first.

HTH,
Robert

On Dec 4, 2007 10:35 PM, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I have deployed soapmonitor into my axis1.3 installation to test my axis2
> and .NET websvc interaction issues. I followed all config steps as mentioned
> in the soapmonitor doc (one slight difference - deployed in webroot in an
> exploded format, so that soapmonitor is access as
> http://localhost:8080/SOAPMonitor).
>
>
>
> When I invoke the SOAPMonitor using this URL, I get the exception
> "java.lang.ClassFormatError: Truncated class file".
>
> I researched and saw following probably causes:
>
> -  due to problem unzipping the classes from jar at runtime
>
> -  due to inability to access classes from WEB-INF
>
> To remedy this I tried moving jar elsewhere (away from WEB-INF) to adding
> the applet source to my Eclipse – nothing worked.
>
>
>
> Does anyone know what could be the reason for this?
>
>
>
> Full java console log is as follows:
>
>
>
> Java Plug-in 1.5.0_12
>
> Using JRE version 1.5.0_12 Java HotSpot(TM) Client VM
>
> User home directory = C:\Documents and Settings\vpantvai
>
> network: Loading user-defined proxy configuration ...
>
> network: Done.
>
> network: Loading proxy configuration from Internet Explorer ...
>
> network: Done.
>
> network: Loading direct proxy configuration ...
>
> network: Done.
>
> network: Proxy Configuration: No proxy
>
> basic: Cache is disabled by user
>
> basic: Plugin modality.register
>
> basic: Registered modality listener
>
> liveconnect: Invoking JS method: document
>
> liveconnect: Invoking JS method: URL
>
> basic: Referencing classloader: [EMAIL PROTECTED],
> refcount=1
>
> basic: Added progress listener: [EMAIL PROTECTED]
>
> basic: Loading applet ...
>
> basic: Initializing applet ...
>
> basic: Starting applet ...
>
> basic: Referencing classloader: [EMAIL PROTECTED],
> refcount=2
>
> basic: Releasing classloader: [EMAIL PROTECTED], refcount=1
>
> network: Connecting http://localhost:8080/SOAPMonitorApplet.class with
> proxy=DIRECT
>
> network: Connecting http://localhost:8080/SOAPMonitorApplet.class with
> cookie "JSESSIONID=1FAF54A700367497E0792833D0A411FC"
>
> java.lang.ClassFormatError: Truncated class file
>
> at java.lang.ClassLoader.defineClass1(Native Method)
>
> at java.lang.ClassLoader.defineClass(Unknown Source)
>
> at java.security.SecureClassLoader.defineClass(Unknown Source)
>
> at sun.applet.AppletClassLoader.findClass(Unknown Source)
>
> at java.lang.ClassLoader.loadClass(Unknown Source)
>
> at sun.applet.AppletClassLoader.loadClass(Unknown Source)
>
> at java.lang.ClassLoader.loadClass(Unknown Source)
>
> at sun.applet.AppletClassLoader.loadCode(Unknown Source)
>
> at sun.applet.AppletPanel.createApplet(Unknown Source)
>
> at sun.plugin.AppletViewer.createApplet(Unknown Source)
>
> at sun.applet.AppletPanel.runLoader(Unknown Source)
>
> at sun.applet.AppletPanel.run(Unknown Source)
>
> at java.lang.Thread.run(Unknown Source)

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

[Axis2] 1.3 Soapmonitor problem

2007-12-04 Thread Pantvaidya, Vishwajit

I have deployed soapmonitor into my axis1.3 installation to test my axis2 and 
.NET websvc interaction issues. I followed all config steps as mentioned in the 
soapmonitor doc (one slight difference - deployed in webroot in an exploded 
format, so that soapmonitor is access as http://localhost:8080/SOAPMonitor).

When I invoke the SOAPMonitor using this URL, I get the exception 
"java.lang.ClassFormatError: Truncated class file".
I researched and saw following probably causes:
-  due to problem unzipping the classes from jar at runtime
-  due to inability to access classes from WEB-INF
To remedy this I tried moving jar elsewhere (away from WEB-INF) to adding the 
applet source to my Eclipse - nothing worked.

Does anyone know what could be the reason for this?

Full java console log is as follows:

Java Plug-in 1.5.0_12
Using JRE version 1.5.0_12 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\vpantvai
network: Loading user-defined proxy configuration ...
network: Done.
network: Loading proxy configuration from Internet Explorer ...
network: Done.
network: Loading direct proxy configuration ...
network: Done.
network: Proxy Configuration: No proxy
basic: Cache is disabled by user
basic: Plugin modality.register
basic: Registered modality listener
liveconnect: Invoking JS method: document
liveconnect: Invoking JS method: URL
basic: Referencing classloader: [EMAIL PROTECTED], refcount=1
basic: Added progress listener: [EMAIL PROTECTED]
basic: Loading applet ...
basic: Initializing applet ...
basic: Starting applet ...
basic: Referencing classloader: [EMAIL PROTECTED], refcount=2
basic: Releasing classloader: [EMAIL PROTECTED], refcount=1
network: Connecting http://localhost:8080/SOAPMonitorApplet.class with 
proxy=DIRECT
network: Connecting http://localhost:8080/SOAPMonitorApplet.class with cookie 
"JSESSIONID=1FAF54A700367497E0792833D0A411FC"
java.lang.ClassFormatError: Truncated class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at sun.applet.AppletClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.applet.AppletClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.applet.AppletClassLoader.loadCode(Unknown Source)
at sun.applet.AppletPanel.createApplet(Unknown Source)
at sun.plugin.AppletViewer.createApplet(Unknown Source)
at sun.applet.AppletPanel.runLoader(Unknown Source)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-28 Thread Wang Han

Hi Robert,

The SOAPMonitor worked well before I changed the axis/WEB-INF/web.xml.
But it is not there after I changed
  
   AxisServlet
   /services/*
...
  to
  
   AxisServlet
   /*
...

I will try to find out the reason and if it doesn't work yet, I will change
to axis.
Thanks for your reply!


On Nov 28, 2007 10:16 PM, robert lazarski <[EMAIL PROTECTED]> wrote:

> My advice is to move to axis2 if possible for many reasons including
> performance and its more modern features. Looks like your applet isn't
> even loading - you need at least java 1.3 in firefox / IE . If you get
> the "load applet failed" error message, I'd check that java is
> configured properly.
>
> If all else fails, there is a tool called tcpmon that largely does the
> same thing as the soap monitor as a stand alone, non-browser based
> application.
>
> HTH,
> Robert
>
> On Nov 28, 2007 2:38 AM, Wang Han <[EMAIL PROTECTED]> wrote:
> > Hi Robert & Martin,
> >
> > Thanks for your reply.
> >
> > Robert:
> > I also wonder this... I changed the web.xml and
> > http://localhost:8080/axis/service/echo is changed to
> > http://localhost:8080/echo.
> > But originally the SOAPMonitor is deployed at
> > http://localhost:8080/axis/SOAPMonitor (no 'services' in the url), so
> where
> > should it be after I re-deployed the service? any suggestion is welcome
> :)
> >
> > Martin: do u mean we can use SOAPMonitor in axis2 independently? So if I
> > have a service which is deployed at http://localhost:8080/echo, I can
> > monitor it by
> >
> >
> http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=echo&submit=+Engage
> > + regardless where the service is deployed?
> > I have no idea about axis2 since I always work with axis1.4, is axis2
> better
> > than axis1.4 ?
> >
> > Thanks!
> > Han
> >
> > On Nov 28, 2007 10:19 AM, robert lazarski < [EMAIL PROTECTED]>
> wrote:
> > > The axis 1.x version of the soap monitor is pretty silent on errors -
> > > I tried to fix that in axis2. In axis 1.x or axis2, look to make sure
> > > nothing else is listening on port 5001 or try moving to a different
> > > port to see if that helps. Double check your servlet setup in the
> > > web.xml file. Firefox has an applet console which is sometimes helpful
> > > in showing what the errors are.
> > >
> > > HTH,
> > > Robert
> > >
> > >
> > >
> > >
> > > On Nov 27, 2007 9:07 PM, Martin Gainty < [EMAIL PROTECTED]> wrote:
> > > >
> > > >
> > > > Han-
> > > >
> > > > In axis2 soapmonitor is an independent module which is engaged to
> the
> > > > selected service
> > > > as Version is installed as as default service if you want to engage
> > > > soapmonitor module for the axisService 'Version' place this in
> browser
> > > >
> >
> http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=Version&submit=+Engage+
> > > >
> > > > M--
> > > >
> > > >
> > > > - Original Message -
> > > > From: Wang Han
> > > > To: axis-user@ws.apache.org
> > > > Sent: Tuesday, November 27, 2007 8:47 PM
> > > > Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual
> host.
> > > >
> > > > Hi guys,
> > > > Any clue please?
> > > >
> > > >
> > > > On Nov 27, 2007 10:44 PM, Wang Han <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > Hi Vaibhav,
> > > > >
> > > > > "load applet failed" occurs when I use firefox.
> > > > > But I can't access the SOAPMonitor either by IE -- it brings me to
> a
> > > > > searching page immediately
> > > > > with " http://localhost:8080"; in the searching bar once I try to
> open
> > > > > the link in IE.
> > > > >
> > > > > I do read the appendix and deployed the service successfully
> before
> > > > > setting the virtual host.
> > > > >
> > > > > After setting the virtual host, I try to re-deploy the SOAPMonitor
> > > > > according to the appendix as below:
> > > > > 1. compiled the SOAPMonitor class and copy them to
> tomcat/webapps/ROOT
> > > > > 2. executing "java org.apache.axis.client.A

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-28 Thread robert lazarski

My advice is to move to axis2 if possible for many reasons including
performance and its more modern features. Looks like your applet isn't
even loading - you need at least java 1.3 in firefox / IE . If you get
the "load applet failed" error message, I'd check that java is
configured properly.

If all else fails, there is a tool called tcpmon that largely does the
same thing as the soap monitor as a stand alone, non-browser based
application.

HTH,
Robert

On Nov 28, 2007 2:38 AM, Wang Han <[EMAIL PROTECTED]> wrote:
> Hi Robert & Martin,
>
> Thanks for your reply.
>
> Robert:
> I also wonder this... I changed the web.xml and
> http://localhost:8080/axis/service/echo is changed to
> http://localhost:8080/echo.
> But originally the SOAPMonitor is deployed at
> http://localhost:8080/axis/SOAPMonitor (no 'services' in the url), so where
> should it be after I re-deployed the service? any suggestion is welcome :)
>
> Martin: do u mean we can use SOAPMonitor in axis2 independently? So if I
> have a service which is deployed at http://localhost:8080/echo, I can
> monitor it by
>
> http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=echo&submit=+Engage
> + regardless where the service is deployed?
> I have no idea about axis2 since I always work with axis1.4, is axis2 better
> than axis1.4 ?
>
> Thanks!
> Han
>
> On Nov 28, 2007 10:19 AM, robert lazarski < [EMAIL PROTECTED]> wrote:
> > The axis 1.x version of the soap monitor is pretty silent on errors -
> > I tried to fix that in axis2. In axis 1.x or axis2, look to make sure
> > nothing else is listening on port 5001 or try moving to a different
> > port to see if that helps. Double check your servlet setup in the
> > web.xml file. Firefox has an applet console which is sometimes helpful
> > in showing what the errors are.
> >
> > HTH,
> > Robert
> >
> >
> >
> >
> > On Nov 27, 2007 9:07 PM, Martin Gainty < [EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Han-
> > >
> > > In axis2 soapmonitor is an independent module which is engaged to the
> > > selected service
> > > as Version is installed as as default service if you want to engage
> > > soapmonitor module for the axisService 'Version' place this in browser
> > >
> http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=Version&submit=+Engage+
> > >
> > > M--
> > >
> > >
> > > - Original Message -
> > > From: Wang Han
> > > To: axis-user@ws.apache.org
> > > Sent: Tuesday, November 27, 2007 8:47 PM
> > > Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual host.
> > >
> > > Hi guys,
> > > Any clue please?
> > >
> > >
> > > On Nov 27, 2007 10:44 PM, Wang Han <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi Vaibhav,
> > > >
> > > > "load applet failed" occurs when I use firefox.
> > > > But I can't access the SOAPMonitor either by IE -- it brings me to a
> > > > searching page immediately
> > > > with " http://localhost:8080"; in the searching bar once I try to open
> > > > the link in IE.
> > > >
> > > > I do read the appendix and deployed the service successfully before
> > > > setting the virtual host.
> > > >
> > > > After setting the virtual host, I try to re-deploy the SOAPMonitor
> > > > according to the appendix as below:
> > > > 1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
> > > > 2. executing "java org.apache.axis.client.AdminClient
> > > > -lhttp://localhost:8080/AdminService deploy-monitor.wsdd "
> > > > successfully.
> > > > 3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
> > > > then failed.
> > > >
> > > > Please correct me if I made any mistake here,Thanks.
> > > >
> > > >
> > > >
> > > >
> > > > On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
> > > > >
> > > > > I guess it should work fine with IE. If not, refer to "Appendix:
> > > Enabling the
> > > > > SOAP Monitor' under User Guide in your docs folder.
> > > > >
> > > > >
> > > > > Wang Han wrote:
> > > > > >
> > > > > > Hi guys,
>

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-28 Thread Wang Han

Hi Robert,
I try it with Firefox and there comes the msg "SOAPMonitorApplet notinited"
in the statusbar.
Seems axis can't find the SOAPMonitor class. but I do copied them to
webapps/axis and webapps/root separately, any comments please?

B.R
Han

On Nov 28, 2007 3:38 PM, Wang Han <[EMAIL PROTECTED]> wrote:

> Hi Robert & Martin,
>
> Thanks for your reply.
>
> Robert:
> I also wonder this... I changed the web.xml and
> http://localhost:8080/axis/service/echo is changed to
> http://localhost:8080/echo.
> But originally the SOAPMonitor is deployed at
> http://localhost:8080/axis/SOAPMonitor (no 'services' in the url), so
> where should it be after I re-deployed the service? any suggestion is
> welcome :)
>
> Martin: do u mean we can use SOAPMonitor in axis2 independently? So if I
> have a service which is deployed at http://localhost:8080/echo, I can
> monitor it by
> http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=echo&submit=+Engage
>
> <http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=Version&submit=+Engage>+
> regardless where the service is deployed?
> I have no idea about axis2 since I always work with axis1.4, is axis2
> better than axis1.4 ?
>
> Thanks!
> Han
>
>
> On Nov 28, 2007 10:19 AM, robert lazarski < [EMAIL PROTECTED]>
> wrote:
>
> > The axis 1.x version of the soap monitor is pretty silent on errors -
> > I tried to fix that in axis2. In axis 1.x or axis2, look to make sure
> > nothing else is listening on port 5001 or try moving to a different
> > port to see if that helps. Double check your servlet setup in the
> > web.xml file. Firefox has an applet console which is sometimes helpful
> > in showing what the errors are.
> >
> > HTH,
> > Robert
> >
> > On Nov 27, 2007 9:07 PM, Martin Gainty < [EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Han-
> > >
> > > In axis2 soapmonitor is an independent module which is engaged to the
> > > selected service
> > > as Version is installed as as default service if you want to engage
> > > soapmonitor module for the axisService 'Version' place this in browser
> > >
> > http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=Version&submit=+Engage+
> > >
> > > M--
> > >
> > >
> > > - Original Message -
> > > From: Wang Han
> > > To: axis-user@ws.apache.org
> > > Sent: Tuesday, November 27, 2007 8:47 PM
> > > Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual
> > host.
> > >
> > > Hi guys,
> > > Any clue please?
> > >
> > >
> > > On Nov 27, 2007 10:44 PM, Wang Han <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi Vaibhav,
> > > >
> > > > "load applet failed" occurs when I use firefox.
> > > > But I can't access the SOAPMonitor either by IE -- it brings me to a
> > > > searching page immediately
> > > > with " http://localhost:8080"; in the searching bar once I try to
> > open
> > > > the link in IE.
> > > >
> > > > I do read the appendix and deployed the service successfully before
> > > > setting the virtual host.
> > > >
> > > > After setting the virtual host, I try to re-deploy the SOAPMonitor
> > > > according to the appendix as below:
> > > > 1. compiled the SOAPMonitor class and copy them to
> > tomcat/webapps/ROOT
> > > > 2. executing "java org.apache.axis.client.AdminClient
> > > > -lhttp://localhost:8080/AdminService deploy-monitor.wsdd "
> > > > successfully.
> > > > 3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
> > > > then failed.
> > > >
> > > > Please correct me if I made any mistake here,Thanks.
> > > >
> > > >
> > > >
> > > >
> > > > On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > wrote:
> > > > >
> > > > > I guess it should work fine with IE. If not, refer to "Appendix:
> > > Enabling the
> > > > > SOAP Monitor' under User Guide in your docs folder.
> > > > >
> > > > >
> > > > > Wang Han wrote:
> > > > > >
> > > > > > Hi guys,
> > > > > >
> > > > >

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

Hi Robert & Martin,

Thanks for your reply.

Robert:
I also wonder this... I changed the web.xml and
http://localhost:8080/axis/service/echo is changed to
http://localhost:8080/echo.
But originally the SOAPMonitor is deployed at
http://localhost:8080/axis/SOAPMonitor (no 'services' in the url), so where
should it be after I re-deployed the service? any suggestion is welcome :)

Martin: do u mean we can use SOAPMonitor in axis2 independently? So if I
have a service which is deployed at http://localhost:8080/echo, I can
monitor it by
http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=echo&submit=+Engage<http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=Version&submit=+Engage>+
regardless where the service is deployed?
I have no idea about axis2 since I always work with axis1.4, is axis2 better
than axis1.4 ?

Thanks!
Han

On Nov 28, 2007 10:19 AM, robert lazarski <[EMAIL PROTECTED]> wrote:

> The axis 1.x version of the soap monitor is pretty silent on errors -
> I tried to fix that in axis2. In axis 1.x or axis2, look to make sure
> nothing else is listening on port 5001 or try moving to a different
> port to see if that helps. Double check your servlet setup in the
> web.xml file. Firefox has an applet console which is sometimes helpful
> in showing what the errors are.
>
> HTH,
> Robert
>
> On Nov 27, 2007 9:07 PM, Martin Gainty <[EMAIL PROTECTED]> wrote:
> >
> >
> > Han-
> >
> > In axis2 soapmonitor is an independent module which is engaged to the
> > selected service
> > as Version is installed as as default service if you want to engage
> > soapmonitor module for the axisService 'Version' place this in browser
> >
> http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=Version&submit=+Engage+
> >
> > M--
> >
> >
> > - Original Message -
> > From: Wang Han
> > To: axis-user@ws.apache.org
> > Sent: Tuesday, November 27, 2007 8:47 PM
> > Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual host.
> >
> > Hi guys,
> > Any clue please?
> >
> >
> > On Nov 27, 2007 10:44 PM, Wang Han <[EMAIL PROTECTED]> wrote:
> >
> > > Hi Vaibhav,
> > >
> > > "load applet failed" occurs when I use firefox.
> > > But I can't access the SOAPMonitor either by IE -- it brings me to a
> > > searching page immediately
> > > with " http://localhost:8080"; in the searching bar once I try to open
> > > the link in IE.
> > >
> > > I do read the appendix and deployed the service successfully before
> > > setting the virtual host.
> > >
> > > After setting the virtual host, I try to re-deploy the SOAPMonitor
> > > according to the appendix as below:
> > > 1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
> > > 2. executing "java org.apache.axis.client.AdminClient
> > > -lhttp://localhost:8080/AdminService deploy-monitor.wsdd "
> > > successfully.
> > > 3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
> > > then failed.
> > >
> > > Please correct me if I made any mistake here,Thanks.
> > >
> > >
> > >
> > >
> > > On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
> > > >
> > > > I guess it should work fine with IE. If not, refer to "Appendix:
> > Enabling the
> > > > SOAP Monitor' under User Guide in your docs folder.
> > > >
> > > >
> > > > Wang Han wrote:
> > > > >
> > > > > Hi guys,
> > > > >
> > > > > Service "echo" is deployed at:
> > > > > http://localhost:8080/axis/services/echo, SOAPMonitor is at
> > > > > http://localhost:8080/axis/SOAPMonitor.
> > > > > I can use SOAPMonitor to monitor all soap messages between echo
> > > > > service and its client.
> > > > >
> > > > > For some special requirement, I need re-deploy the echo service to
> > > > > http://localhost:8080/echo .
> > > > > I implement it successfully by modifying tomcat/conf/server.xml
> and
> > > > > webapps/axis/web.xml.
> > > > >
> > > > > But the SOAPMonitor is not there any more. I  try to access it by
> > > > > http://localhost:8080/SOAPMonitor,
> > > > > It always gives me "load app

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread robert lazarski

The axis 1.x version of the soap monitor is pretty silent on errors -
I tried to fix that in axis2. In axis 1.x or axis2, look to make sure
nothing else is listening on port 5001 or try moving to a different
port to see if that helps. Double check your servlet setup in the
web.xml file. Firefox has an applet console which is sometimes helpful
in showing what the errors are.

HTH,
Robert

On Nov 27, 2007 9:07 PM, Martin Gainty <[EMAIL PROTECTED]> wrote:
>
>
> Han-
>
> In axis2 soapmonitor is an independent module which is engaged to the
> selected service
> as Version is installed as as default service if you want to engage
> soapmonitor module for the axisService 'Version' place this in browser
> http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=Version&submit=+Engage+
>
> M--
>
>
> - Original Message -
> From: Wang Han
> To: axis-user@ws.apache.org
> Sent: Tuesday, November 27, 2007 8:47 PM
> Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual host.
>
> Hi guys,
> Any clue please?
>
>
> On Nov 27, 2007 10:44 PM, Wang Han <[EMAIL PROTECTED]> wrote:
>
> > Hi Vaibhav,
> >
> > "load applet failed" occurs when I use firefox.
> > But I can't access the SOAPMonitor either by IE -- it brings me to a
> > searching page immediately
> > with " http://localhost:8080"; in the searching bar once I try to open
> > the link in IE.
> >
> > I do read the appendix and deployed the service successfully before
> > setting the virtual host.
> >
> > After setting the virtual host, I try to re-deploy the SOAPMonitor
> > according to the appendix as below:
> > 1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
> > 2. executing "java org.apache.axis.client.AdminClient
> > -lhttp://localhost:8080/AdminService deploy-monitor.wsdd "
> > successfully.
> > 3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
> > then failed.
> >
> > Please correct me if I made any mistake here,Thanks.
> >
> >
> >
> >
> > On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > >
> > > I guess it should work fine with IE. If not, refer to "Appendix:
> Enabling the
> > > SOAP Monitor' under User Guide in your docs folder.
> > >
> > >
> > > Wang Han wrote:
> > > >
> > > > Hi guys,
> > > >
> > > > Service "echo" is deployed at:
> > > > http://localhost:8080/axis/services/echo, SOAPMonitor is at
> > > > http://localhost:8080/axis/SOAPMonitor.
> > > > I can use SOAPMonitor to monitor all soap messages between echo
> > > > service and its client.
> > > >
> > > > For some special requirement, I need re-deploy the echo service to
> > > > http://localhost:8080/echo .
> > > > I implement it successfully by modifying tomcat/conf/server.xml and
> > > > webapps/axis/web.xml.
> > > >
> > > > But the SOAPMonitor is not there any more. I  try to access it by
> > > > http://localhost:8080/SOAPMonitor,
> > > > It always gives me "load applet failed" error message.
> > > >
> > > > Could someone tell me how can I find back the SOAPMonitor? thanks a
> lot!
> > > >
> > > > Tomcat6.0 + axis1.4.
> > > > tomcat/conf/server.xml:
> > > >> > > unpackWARs="true" autoDeploy="true"
> > > > xmlValidation="false" xmlNamespaceAware="false">
> > > >  
> > > >
> > > > webapps/axis/WEB-INF/web.xml:
> > > >   
> > > >AxisServlet
> > > >
> > > >/*
> > > >   
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > >
> > > --
> > > View this message in context:
> http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
> > > 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]

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread Martin Gainty

Han-

In axis2 soapmonitor is an independent module which is engaged to the selected 
service
as Version is installed as as default service if you want to engage soapmonitor 
module for the axisService 'Version' place this in browser
http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=Version&submit=+Engage+

M--

  - Original Message - 
  From: Wang Han 
  To: axis-user@ws.apache.org 
  Sent: Tuesday, November 27, 2007 8:47 PM
  Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual host.


  Hi guys,
  Any clue please?


  On Nov 27, 2007 10:44 PM, Wang Han <[EMAIL PROTECTED]> wrote:

Hi Vaibhav,

"load applet failed" occurs when I use firefox.
But I can't access the SOAPMonitor either by IE -- it brings me to a
searching page immediately
with " http://localhost:8080"; in the searching bar once I try to open
the link in IE.

I do read the appendix and deployed the service successfully before
setting the virtual host.

After setting the virtual host, I try to re-deploy the SOAPMonitor 
according to the appendix as below:
1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
2. executing "java org.apache.axis.client.AdminClient
-lhttp://localhost:8080/AdminService deploy-monitor.wsdd "
successfully.
3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
then failed.

Please correct me if I made any mistake here,Thanks. 


On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I guess it should work fine with IE. If not, refer to "Appendix: Enabling 
the 
> SOAP Monitor' under User Guide in your docs folder.
>
>
> Wang Han wrote:
> >
> > Hi guys,
> >
> > Service "echo" is deployed at:
    > > http://localhost:8080/axis/services/echo, SOAPMonitor is at
> > http://localhost:8080/axis/SOAPMonitor.
> > I can use SOAPMonitor to monitor all soap messages between echo 
> > service and its client.
> >
> > For some special requirement, I need re-deploy the echo service to
> > http://localhost:8080/echo .
> > I implement it successfully by modifying tomcat/conf/server.xml and
> > webapps/axis/web.xml.
> >
> > But the SOAPMonitor is not there any more. I  try to access it by
> > http://localhost:8080/SOAPMonitor,
> > It always gives me "load applet failed" error message.
> >
> > Could someone tell me how can I find back the SOAPMonitor? thanks a 
lot! 
> >
> > Tomcat6.0 + axis1.4.
> > tomcat/conf/server.xml:
> >> unpackWARs="true" autoDeploy="true" 
> > xmlValidation="false" xmlNamespaceAware="false">
> >  
> >
> > webapps/axis/WEB-INF/web.xml: 
> >   
> >AxisServlet
> > 
> >/*
> >   
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> --
> View this message in context: 
http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
> Sent from the Axis - User mailing list archive at Nabble.com .
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] 
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

Hi guys,
Any clue please?

On Nov 27, 2007 10:44 PM, Wang Han <[EMAIL PROTECTED]> wrote:

> Hi Vaibhav,
>
> "load applet failed" occurs when I use firefox.
> But I can't access the SOAPMonitor either by IE -- it brings me to a
> searching page immediately
> with "http://localhost:8080"; in the searching bar once I try to open
> the link in IE.
>
> I do read the appendix and deployed the service successfully before
> setting the virtual host.
>
> After setting the virtual host, I try to re-deploy the SOAPMonitor
> according to the appendix as below:
> 1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
> 2. executing "java org.apache.axis.client.AdminClient
> -lhttp://localhost:8080/AdminService deploy-monitor.wsdd"
> successfully.
> 3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
> then failed.
>
> Please correct me if I made any mistake here,Thanks.
>
> On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > I guess it should work fine with IE. If not, refer to "Appendix:
> Enabling the
> > SOAP Monitor' under User Guide in your docs folder.
> >
> >
> > Wang Han wrote:
> > >
> > > Hi guys,
> > >
> > > Service "echo" is deployed at:
> > > http://localhost:8080/axis/services/echo, SOAPMonitor is at
> > > http://localhost:8080/axis/SOAPMonitor.
> > > I can use SOAPMonitor to monitor all soap messages between echo
> > > service and its client.
> > >
> > > For some special requirement, I need re-deploy the echo service to
> > > http://localhost:8080/echo.
> > > I implement it successfully by modifying tomcat/conf/server.xml and
> > > webapps/axis/web.xml.
> > >
> > > But the SOAPMonitor is not there any more. I  try to access it by
> > > http://localhost:8080/SOAPMonitor,
> > > It always gives me "load applet failed" error message.
> > >
> > > Could someone tell me how can I find back the SOAPMonitor? thanks a
> lot!
> > >
> > > Tomcat6.0 + axis1.4.
> > > tomcat/conf/server.xml:
> > >> > unpackWARs="true" autoDeploy="true"
> > > xmlValidation="false" xmlNamespaceAware="false">
> > >  
> > >
> > > webapps/axis/WEB-INF/web.xml:
> > >   
> > >AxisServlet
> > >
> > >/*
> > >   
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> >
> > --
> > View this message in context:
> http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
> > Sent from the Axis - User mailing list archive at Nabble.com.
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

Hi Vaibhav,

"load applet failed" occurs when I use firefox.
But I can't access the SOAPMonitor either by IE -- it brings me to a
searching page immediately
with "http://localhost:8080"; in the searching bar once I try to open
the link in IE.

I do read the appendix and deployed the service successfully before
setting the virtual host.

After setting the virtual host, I try to re-deploy the SOAPMonitor
according to the appendix as below:
1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
2. executing "java org.apache.axis.client.AdminClient
-lhttp://localhost:8080/AdminService deploy-monitor.wsdd"
successfully.
3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
then failed.

Please correct me if I made any mistake here,Thanks.

On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I guess it should work fine with IE. If not, refer to "Appendix: Enabling the
> SOAP Monitor' under User Guide in your docs folder.
>
>
> Wang Han wrote:
> >
> > Hi guys,
> >
> > Service "echo" is deployed at:
> > http://localhost:8080/axis/services/echo, SOAPMonitor is at
> > http://localhost:8080/axis/SOAPMonitor.
> > I can use SOAPMonitor to monitor all soap messages between echo
> > service and its client.
> >
> > For some special requirement, I need re-deploy the echo service to
> > http://localhost:8080/echo.
> > I implement it successfully by modifying tomcat/conf/server.xml and
> > webapps/axis/web.xml.
> >
> > But the SOAPMonitor is not there any more. I  try to access it by
> > http://localhost:8080/SOAPMonitor,
> > It always gives me "load applet failed" error message.
> >
> > Could someone tell me how can I find back the SOAPMonitor? thanks a lot!
> >
> > Tomcat6.0 + axis1.4.
> > tomcat/conf/server.xml:
> >> unpackWARs="true" autoDeploy="true"
> > xmlValidation="false" xmlNamespaceAware="false">
> >  
> >
> > webapps/axis/WEB-INF/web.xml:
> >   
> >AxisServlet
> >
> >/*
> >   
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> --
> View this message in context: 
> http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
> 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]

Re: SOAPMonitor doesn't work after setting tomcat virtual host.

2007-11-27 Thread [EMAIL PROTECTED]


I guess it should work fine with IE. If not, refer to "Appendix: Enabling the
SOAP Monitor' under User Guide in your docs folder.

Wang Han wrote:
> 
> Hi guys,
> 
> Service "echo" is deployed at:
> http://localhost:8080/axis/services/echo, SOAPMonitor is at
> http://localhost:8080/axis/SOAPMonitor.
> I can use SOAPMonitor to monitor all soap messages between echo
> service and its client.
> 
> For some special requirement, I need re-deploy the echo service to
> http://localhost:8080/echo.
> I implement it successfully by modifying tomcat/conf/server.xml and
> webapps/axis/web.xml.
> 
> But the SOAPMonitor is not there any more. I  try to access it by
> http://localhost:8080/SOAPMonitor,
> It always gives me "load applet failed" error message.
> 
> Could someone tell me how can I find back the SOAPMonitor? thanks a lot!
> 
> Tomcat6.0 + axis1.4.
> tomcat/conf/server.xml:
>unpackWARs="true" autoDeploy="true"
> xmlValidation="false" xmlNamespaceAware="false">
>  
> 
> webapps/axis/WEB-INF/web.xml:
>   
>AxisServlet
>
>/*
>   
> 
> -----
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
Sent from the Axis - User mailing list archive at Nabble.com.


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

SOAPMonitor doesn't work after setting tomcat virtual host.

Hi guys,

Service "echo" is deployed at:
http://localhost:8080/axis/services/echo, SOAPMonitor is at
http://localhost:8080/axis/SOAPMonitor.
I can use SOAPMonitor to monitor all soap messages between echo
service and its client.

For some special requirement, I need re-deploy the echo service to
http://localhost:8080/echo.
I implement it successfully by modifying tomcat/conf/server.xml and
webapps/axis/web.xml.

But the SOAPMonitor is not there any more. I  try to access it by
http://localhost:8080/SOAPMonitor,
It always gives me "load applet failed" error message.

Could someone tell me how can I find back the SOAPMonitor? thanks a lot!

Tomcat6.0 + axis1.4.
tomcat/conf/server.xml:
  
 

webapps/axis/WEB-INF/web.xml:
  
   AxisServlet
   
   /*
  

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

Re: (Rampart) Not seeing encrypted message in SOAPMonitor

2007-10-19 Thread Jon Hanshew


To determine what is SOAP Monitor behavior vs Axis behavior download TCPMon. 
It is a WYSIWUG tool.

For example, SOAP Monitor gives displays unencrypted transactions for SSL
connections because it hooks into the process above the SSL level.

For the situation you describe, I would suspect an incorrect implementation
of the policy, but TCPMon will tell the true story.


A Sunley wrote:
> 
> Hi folks,
> 
> I'm something of a rookie when it comes to implementing security in web
> services. I'm working with policy example #3 to try and get an idea for
> how security policy works. Direct link here:
> https://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/policy/sample03/
> 
> I've changed the invoked web service method but the policy is the same,
> but I'm a bit confused by something. As I understand it the soap message
> body in this example should be encrypted, correct? But looking at the
> messages in SOAPMonitor, I am seeing the security header but the body in
> plain text. Is the policy not being applied properly? 
> 
> I'm also seeing differences in the response shown in SOAPMonitor and a
> printout of the OMElement response in the client (messages displayed
> below). The OMElement shows the wsa, xenc and wsu namespaces while
> SOAPMonitor does not.
> 
> Basically I'm a bit confused by what I am seeing in SOAPMonitor and I’m
> not sure whether this is indicating that the policy is not being applied
> properly or whether this is typical behaviour of SOAPMonitor itself?  
> 
> Also, despite reading into WS-Policy I'm still rather unsure of it,
> generally. Are there any guides to creating policy documents? Ultimately
> my aim is for the requests to the service to have a UsernameToken and the
> SOAP body encrypted. And the response message body to be encrypted.
> 
> 
> 
> SOAPMonitor Request Body:
> 
> 
>  xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> wsu:Id="Id-21192393">
> http://webservice.example.com/xsd";>
>   username
>   pas
> 
>   
> 
> 
> 
> SOAPMonitor Response Message:
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>   
> http://webservice.example.com/xsd";>
>   
>  xmlns="http://schema.example.com/xsd";>0
> http://schema.example.com/xsd";>Request
> Fulfilled
>   
> 
>   
> 
> 
> 
> Printout of response message at client:
> 
> http://webservice.example.com/xsd";
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://www.w3.org/2005/08/addressing";
> xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
> 
> http://schema.example.com/xsd";
> mlns="http://schema.example.com/xsd";>0
> http://schema.example.com/xsd";
> xmlns:axis2ns8="http://schema.example.com/xsd";>Request
> Fulfilled
> 
> 
> 
> 
> Regards,
> Alan.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/%28Rampart%29-Not-seeing-encrypted-message-in-SOAPMonitor-tf4368000.html#a13297248
Sent from the Axis - User mailing list archive at Nabble.com.


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

Re: SOAPMonitor Problem

Problem solved.

SOAPMonitor not runs on Glassfish.
I have do the same on Tomcat and it runs.


Thaks for all.

2007/10/9, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]>:
>
> Mmm, I´m using axis distribution deployed on Glassfish server. ¿Is this a
> problem?
> I think that axis is independent of the servlet container.
>
> 2007/10/9, robert lazarski < [EMAIL PROTECTED]>:
> >
> > Ehh, looks like you are already engaging the module.
> >
> > "The requested resource is not available".
> >
> > Where do you see that, in the browser? I think that's a tomcat error.
> > So you've edited web.xml, engaged the module, you have expanded the
> > soapmonitor.jar to webapps/axis2 and there is a module under
> > WEB-INF/modules ? Hmm, this does work in 1.3 because I use it.
> >
> > Try looking in the tomcat logs for some clues - you might be getting
> > an error somewhere. Also verify you are in fact binding to port 5001
> > and some other program has stolen the port - you should get lots of
> > error messages in the logs if that happens.
> >
> > If all else fails, put axis2 in debug mode via the log4j.properties.
> >
> > HTH,
> > Robert
> >
> > On 10/9/07, robert lazarski <[EMAIL PROTECTED]> wrote:
> > > In your axis2.xml , you need to have:
> > >
> > > 
> > > 
> > >
> > > As the docs say, don't copy and paste the phases. In fact, you
> > > shouldn't need to change those at all.
> > >
> > > HTH,
> > > Robert
> > >
> > > On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]>
> > wrote:
> > > > I do all steps in documentation. I don´t modify phaseOrder content,
> > because
> > > > the phase soapmonitorPhase already exists.
> > > > Perhaps I don´t understand the phase filosofy.
> > > >
> > > > In my axis2.xml I have:
> > > >
> > > > ...
> > > > 
> > > > ...
> > > > 
> > > > 
> > > > 
> > > >  > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
> > > > 
> > > > 
> > > >  > > >
> > > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
> > > > 
> > > > 
> > > > 
> > > > 
> > > >   > > >
> > > > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > >  
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  > > > class=" org.apache.axis2.engine.DispatchPhase">
> > > >  > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher
> > > > "/>
> > > >  > > >
> > > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > > >  > > >
> > > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > > >  > > >
> > > > class=" org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> > > > "/>
> > > >
> > > >  > > >
> > > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher "/>
> > > > 
> > > >  
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > >   > > >  class="
> > > > org.apache.axis2.dispatchers.AddressingBasedDispatcher ">
> > > >  
> > > > 
> > > > 
> > > > 
> > > >

Re: SOAPMonitor Problem

Mmm, I´m using axis distribution deployed on Glassfish server. ¿Is this a
problem?
I think that axis is independent of the servlet container.

2007/10/9, robert lazarski <[EMAIL PROTECTED]>:
>
> Ehh, looks like you are already engaging the module.
>
> "The requested resource is not available".
>
> Where do you see that, in the browser? I think that's a tomcat error.
> So you've edited web.xml, engaged the module, you have expanded the
> soapmonitor.jar to webapps/axis2 and there is a module under
> WEB-INF/modules ? Hmm, this does work in 1.3 because I use it.
>
> Try looking in the tomcat logs for some clues - you might be getting
> an error somewhere. Also verify you are in fact binding to port 5001
> and some other program has stolen the port - you should get lots of
> error messages in the logs if that happens.
>
> If all else fails, put axis2 in debug mode via the log4j.properties.
>
> HTH,
> Robert
>
> On 10/9/07, robert lazarski <[EMAIL PROTECTED]> wrote:
> > In your axis2.xml , you need to have:
> >
> > 
> > 
> >
> > As the docs say, don't copy and paste the phases. In fact, you
> > shouldn't need to change those at all.
> >
> > HTH,
> > Robert
> >
> > On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]>
> wrote:
> > > I do all steps in documentation. I don´t modify phaseOrder content,
> because
> > > the phase soapmonitorPhase already exists.
> > > Perhaps I don´t understand the phase filosofy.
> > >
> > > In my axis2.xml I have:
> > >
> > > ...
> > > 
> > > ...
> > > 
> > > 
> > > 
> > >  > >
> > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
> > > 
> > > 
> > >  > >
> > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
> > > 
> > > 
> > > 
> > > 
> > >   > >
> > > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > >  
> > > 
> > > 
> > > 
> > > 
> > >  > > class="org.apache.axis2.engine.DispatchPhase">
> > >  > >
> > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher
> > > "/>
> > >  > >
> > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > >  > >
> > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > >  > >
> > > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> > > "/>
> > >
> > >  > >
> > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > > 
> > >  
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  
> > > 
> > > 
> > >   > >  class="
> > > org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > >  
> > > 
> > > 
> > > 
> > > 
> > >  > > class="org.apache.axis2.engine.DispatchPhase">
> > >  > >
> > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > >  > >
> > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher
> > > "/>
> > >  > >
> > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> > >  > >
> > > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> > >
> > >  > >
> > > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher
> > > "/>
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > 2007/10/9, robert lazarski <[EMAIL PROTECTED]>:
> > > > On 10/9/07, Fátima Milla Olaya <[EMAIL PROTECTED]>
> wrote:
> > > > > robert lazarski a écrit :
> > > > > > Did you edit the web.xml ? Please read the docs carefully - the
> > > > > > required info is all there.
> > > > > >
> > > > > > HTH,
> > > > > > Robert
> > > > > >
> > > > > FaultFlow">
> > > > > 
> > > > >   > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > > >  
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >  > > > > class="org.apache.axis2.engine.DispatchPhase ">
> > > > >  > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > > > >  > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > > > >  > > name="RequestURIOperationDispatcher"
> > > > >
> > > > >
> > > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher
> > > "/>
> > > > >  > > name="SOAPMessageBodyBasedDispatcher"
> > > > >
> > > > >
> >

Re: SOAPMonitor Problem

2007-10-09 Thread Todd Allen


This can also be done in the services.xml file (instead of axis2.xml).


robert lazarski wrote:

In your axis2.xml , you need to have:




As the docs say, don't copy and paste the phases. In fact, you
shouldn't need to change those at all.

HTH,
Robert

On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]> wrote:
  

I do all steps in documentation. I don´t modify phaseOrder content, because
the phase soapmonitorPhase already exists.
Perhaps I don´t understand the phase filosofy.

In my axis2.xml I have:

...

...











 
 












 















 


 
 


























2007/10/9, robert lazarski <[EMAIL PROTECTED]>:


On 10/9/07, Fátima Milla Olaya <[EMAIL PROTECTED]> wrote:
  

robert lazarski a écrit :


Did you edit the web.xml ? Please read the docs carefully - the
required info is all there.

HTH,
Robert

  

FaultFlow">

 

class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">


 







class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>




class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>




name="RequestURIOperationDispatcher"



class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher
"/>




name="SOAPMessageBodyBasedDispatcher"



class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>




class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>






















Where in the axis2.xml are you engaging the module ?

HTH,
Robert



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

Re: SOAPMonitor Problem

Ehh, looks like you are already engaging the module.

"The requested resource is not available".

Where do you see that, in the browser? I think that's a tomcat error.
So you've edited web.xml, engaged the module, you have expanded the
soapmonitor.jar to webapps/axis2 and there is a module under
WEB-INF/modules ? Hmm, this does work in 1.3 because I use it.

Try looking in the tomcat logs for some clues - you might be getting
an error somewhere. Also verify you are in fact binding to port 5001
and some other program has stolen the port - you should get lots of
error messages in the logs if that happens.

If all else fails, put axis2 in debug mode via the log4j.properties.

HTH,
Robert

On 10/9/07, robert lazarski <[EMAIL PROTECTED]> wrote:
> In your axis2.xml , you need to have:
>
> 
> 
>
> As the docs say, don't copy and paste the phases. In fact, you
> shouldn't need to change those at all.
>
> HTH,
> Robert
>
> On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]> wrote:
> > I do all steps in documentation. I don´t modify phaseOrder content, because
> > the phase soapmonitorPhase already exists.
> > Perhaps I don´t understand the phase filosofy.
> >
> > In my axis2.xml I have:
> >
> > ...
> > 
> > ...
> > 
> > 
> > 
> >  >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
> > 
> > 
> >  >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
> > 
> > 
> > 
> > 
> >   >
> > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> >  
> > 
> > 
> > 
> > 
> >  > class="org.apache.axis2.engine.DispatchPhase">
> >  >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher
> > "/>
> >  >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> >  >
> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> >  >
> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> > "/>
> >
> >  >
> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > 
> >  
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  
> > 
> > 
> >   >  class="
> > org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> >  
> > 
> > 
> > 
> > 
> >  > class="org.apache.axis2.engine.DispatchPhase">
> >  >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> >  >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher
> > "/>
> >  >
> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> >  >
> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> >
> >  >
> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher
> > "/>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > 2007/10/9, robert lazarski <[EMAIL PROTECTED]>:
> > > On 10/9/07, Fátima Milla Olaya <[EMAIL PROTECTED]> wrote:
> > > > robert lazarski a écrit :
> > > > > Did you edit the web.xml ? Please read the docs carefully - the
> > > > > required info is all there.
> > > > >
> > > > > HTH,
> > > > > Robert
> > > > >
> > > > FaultFlow">
> > > > 
> > > >   > > >
> > > >
> > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > > >  
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  > > > class="org.apache.axis2.engine.DispatchPhase ">
> > > >  > > >
> > > >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > > >  > > >
> > > >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > > >  > name="RequestURIOperationDispatcher"
> > > >
> > > >
> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher
> > "/>
> > > >  > name="SOAPMessageBodyBasedDispatcher"
> > > >
> > > >
> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> > > >
> > > >  > > >
> > > >
> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > >
> > > Where in the axis2.xml are you engaging the module ?
> > >
> > > HTH,
> > > Robert
> > >
> > >

Re: SOAPMonitor Problem

In your axis2.xml , you need to have:




As the docs say, don't copy and paste the phases. In fact, you
shouldn't need to change those at all.

HTH,
Robert

On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]> wrote:
> I do all steps in documentation. I don´t modify phaseOrder content, because
> the phase soapmonitorPhase already exists.
> Perhaps I don´t understand the phase filosofy.
>
> In my axis2.xml I have:
>
> ...
> 
> ...
> 
> 
> 
> 
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher">
> 
> 
> 
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher">
> 
> 
> 
> 
>  
> class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
>  
> 
> 
> 
> 
>  class="org.apache.axis2.engine.DispatchPhase">
> 
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher
> "/>
> 
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> 
> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> 
> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher
> "/>
>
> 
> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> 
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  
> 
> 
>class="
> org.apache.axis2.dispatchers.AddressingBasedDispatcher">
>  
> 
> 
> 
> 
>  class="org.apache.axis2.engine.DispatchPhase">
> 
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> 
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher
> "/>
> 
> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> 
> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
>
> 
> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher
> "/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 2007/10/9, robert lazarski <[EMAIL PROTECTED]>:
> > On 10/9/07, Fátima Milla Olaya <[EMAIL PROTECTED]> wrote:
> > > robert lazarski a écrit :
> > > > Did you edit the web.xml ? Please read the docs carefully - the
> > > > required info is all there.
> > > >
> > > > HTH,
> > > > Robert
> > > >
> > > FaultFlow">
> > > 
> > >   > >
> > >
> class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> > >  
> > > 
> > > 
> > > 
> > > 
> > >  > > class="org.apache.axis2.engine.DispatchPhase ">
> > >  > >
> > >
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> > >  > >
> > >
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> > >  name="RequestURIOperationDispatcher"
> > >
> > >
> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher
> "/>
> > >  name="SOAPMessageBodyBasedDispatcher"
> > >
> > >
> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> > >
> > >  > >
> > >
> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> >
> > Where in the axis2.xml are you engaging the module ?
> >
> > HTH,
> > Robert
> >
> >
> -
> > 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]

Re: SOAPMonitor Problem

I do all steps in documentation. I don´t modify phaseOrder content, because
the phase soapmonitorPhase already exists.
Perhaps I don´t understand the phase filosofy.

In my axis2.xml I have:

...

...











 
 































 
 


























2007/10/9, robert lazarski <[EMAIL PROTECTED]>:
>
> On 10/9/07, Fátima Milla Olaya <[EMAIL PROTECTED]> wrote:
> > robert lazarski a écrit :
> > > Did you edit the web.xml ? Please read the docs carefully - the
> > > required info is all there.
> > >
> > > HTH,
> > > Robert
> > >
> > FaultFlow">
> > 
> >   >
> > class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
> >  
> > 
> > 
> > 
> > 
> >  > class="org.apache.axis2.engine.DispatchPhase">
> >  >
> > class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> >  >
> > class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> >  >
> > class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> >  >
> > class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
> >
> >  >
> > class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >
>
> Where in the axis2.xml are you engaging the module ?
>
> HTH,
> Robert
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: SOAPMonitor Problem

On 10/9/07, Fátima Milla Olaya <[EMAIL PROTECTED]> wrote:
> robert lazarski a écrit :
> > Did you edit the web.xml ? Please read the docs carefully - the
> > required info is all there.
> >
> > HTH,
> > Robert
> >
> FaultFlow">
> 
>  
> class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">
>  
> 
> 
> 
> 
>  class="org.apache.axis2.engine.DispatchPhase">
> 
> class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>
> 
> class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>
> 
> class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>
> 
> class="org.apache.axis2.dispatchers.SOAPMessageBodyBasedDispatcher"/>
>
> 
> class="org.apache.axis2.dispatchers.HTTPLocationBasedDispatcher"/>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>

Where in the axis2.xml are you engaging the module ?

HTH,
Robert

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

Re: SOAPMonitor Problem

2007-10-09 Thread Fátima Milla Olaya


robert lazarski a écrit :

Did you edit the web.xml ? Please read the docs carefully - the
required info is all there.

HTH,
Robert

On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]> wrote:
  

This is exactly what I do. And the response is "The requested resource is
not available" when I try /axis2/SOAPMonitor
Another idea?
Thanks.


2007/10/9, Fátima Milla Olaya < [EMAIL PROTECTED]>:


Unzip the applet classes and place them at the root of the war - for
example axis2/SOAPMonitorApplet*.class

Suerte!

Antonio Manuel Muñiz Martín a écrit :
  

Ok. Thanks.

I extract the soapmonitor.jar file in root directory (/axis2) and I
configured the axis2.xml and web.xml in axis2 distribution.
When I put the URL localhost:8080/axis2/SOAPMonitor in


the browser the


response is "The requested resource is not available".
I forgot anything?

Thanks a lot for your effort.
Regards,
Antonio.



axis2-soapmonitor.jar got renamed to soapmonitor.jar during the
  

conversion to maven2 for the 1.3 release. Thanks for pointing that
out, I'll update the docs.


HTH,
Robert

On 10/9/07, Antonio Manuel Muñiz Martín < [EMAIL PROTECTED]
  

<mailto:[EMAIL PROTECTED]>> wrote:



Hi.

 Where is axis2-soapmonitor.jar ? This file appears in the doc but I
  

do


not find it.
 The command javac -classpath axis2-soapmonitor.jar
SOAPMonitorApplet-java uses it.

 Regards.




 Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
contener información clasificada por su emisor como confidencial en el
marco de su Sistema de Gestión de Seguridad de la Información siendo
para uso exclusivo del destinatario, quedando prohibida su divulgación
copia o distribución a terceros sin la autorización expresa del
remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
notifique al remitente y proceda a su borrado. Gracias por su
  

colaboración.



 This message including any attachments may contain confidential
information, according to our Information Security Management System,
and intended solely for a specific individual to whom they are
addressed. Any unauthorised copy, disclosure or distribution of this
message is strictly forbidden. If you have received this transmission
in error, please notify the sender immediately and delete it.




  


-


To unsubscribe, e-mail:


[EMAIL PROTECTED]


<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>



  

-


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]


  

These are the two files that I have written. Take a look or copy them. Bye

*Web.xml*




2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>



   Apache-Axis2
   
   AxisServlet
   Apache-Axis Servlet
   
org.apache.axis2.transport.http.AxisServlet

   
   
   
   
   
   
   
   
   
   
   1
   
   
   AxisAdminServlet
   Apache-Axis AxisAdmin Servlet (Web 
Admin)

   
   org.apache.axis2.transport.http.AxisAdminServlet
   
   
  SOAPMonitorService
  SOAPMonitorService
  
org.apache.axis2.soapmonitor.servlet.SOAPMonitorService
  
  
 SOAPMonitorPort
     5001
  
  100
   

   
   SOAPMonitorService
   /SOAPMonitor
   


   
   AxisServlet
   /servlet/AxisServlet
   

   
   AxisServlet
   *.jws
   

   
   AxisServlet
   /services/*
   

   
   AxisAdminServlet
   /axis2-admin/*
   

   
   inc
   text/plain
   

  
 index.jsp
 index.html
 /axis2-web/index.jsp
   

   
 404
 /axis2-web/Error/error404.jsp
   

   
   500
   /axis2-web/Error/error500.jsp
   


*Axis2.xml*

FaultFlow">
   

class="org.apache.axis2.dispatchers.AddressingBasedDispatcher">


   
   
   
   
   class="org.apache.axis2.engine.DispatchPhase">

   
class="org.apache.axis2.dispatchers.RequestURIBasedDispatcher"/>

   
class="org.apache.axis2.dispatchers.SOAPActionBasedDispatcher"/>

   
class="org.apache.axis2.dispatchers.RequestURIOperationDispatcher"/>

Re: SOAPMonitor Problem

Did you edit the web.xml ? Please read the docs carefully - the
required info is all there.

HTH,
Robert

On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]> wrote:
> This is exactly what I do. And the response is "The requested resource is
> not available" when I try /axis2/SOAPMonitor
> Another idea?
> Thanks.
>
>
> 2007/10/9, Fátima Milla Olaya < [EMAIL PROTECTED]>:
> >Unzip the applet classes and place them at the root of the war - for
> >example axis2/SOAPMonitorApplet*.class
> >
> >Suerte!
> >
> > Antonio Manuel Muñiz Martín a écrit :
> > > Ok. Thanks.
> > >
> > > I extract the soapmonitor.jar file in root directory (/axis2) and I
> > > configured the axis2.xml and web.xml in axis2 distribution.
> > > When I put the URL localhost:8080/axis2/SOAPMonitor in
> the browser the
> > > response is "The requested resource is not available".
> > > I forgot anything?
> > >
> > > Thanks a lot for your effort.
> > > Regards,
> > > Antonio.
> > >
> > > >axis2-soapmonitor.jar got renamed to soapmonitor.jar during the
> > > conversion to maven2 for the 1.3 release. Thanks for pointing that
> > > out, I'll update the docs.
> > > >
> > > >HTH,
> > > >Robert
> > > >
> > > >On 10/9/07, Antonio Manuel Muñiz Martín < [EMAIL PROTECTED]
> > > <mailto:[EMAIL PROTECTED]>> wrote:
> > > >
> > > >
> > > >
> > > > Hi.
> > > >
> > > >  Where is axis2-soapmonitor.jar ? This file appears in the doc but I
> do
> > > > not find it.
> > > >  The command javac -classpath axis2-soapmonitor.jar
> > > > SOAPMonitorApplet-java uses it.
> > > >
> > > >  Regards.
> > > >
> > > >
> > > >
> > > > 
> > > >  Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> > > > contener información clasificada por su emisor como confidencial en el
> > > > marco de su Sistema de Gestión de Seguridad de la Información siendo
> > > > para uso exclusivo del destinatario, quedando prohibida su divulgación
> > > > copia o distribución a terceros sin la autorización expresa del
> > > > remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> > > > notifique al remitente y proceda a su borrado. Gracias por su
> > > colaboración.
> > > > 
> > > >  This message including any attachments may contain confidential
> > > > information, according to our Information Security Management System,
> > > > and intended solely for a specific individual to whom they are
> > > > addressed. Any unauthorised copy, disclosure or distribution of this
> > > > message is strictly forbidden. If you have received this transmission
> > > > in error, please notify the sender immediately and delete it.
> > > > 
> > > >
> > > >
> > > >
> > >
> > >
> -
> > > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > <mailto:[EMAIL PROTECTED]>
> >
> >
> >
> -
> > 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]

Re: SOAPMonitor Problem

This is exactly what I do. And the response is "The requested resource is
not available" when I try /axis2/SOAPMonitor
Another idea?
Thanks.


2007/10/9, Fátima Milla Olaya <[EMAIL PROTECTED]>:
>Unzip the applet classes and place them at the root of the war - for
>example axis2/SOAPMonitorApplet*.class
>
>Suerte!

> Antonio Manuel Muñiz Martín a écrit :
> > Ok. Thanks.
> >
> > I extract the soapmonitor.jar file in root directory (/axis2) and I
> > configured the axis2.xml and web.xml in axis2 distribution.
> > When I put the URL localhost:8080/axis2/SOAPMonitor in the browser the
> > response is "The requested resource is not available".
> > I forgot anything?
> >
> > Thanks a lot for your effort.
> > Regards,
> > Antonio.
> >
> > >axis2-soapmonitor.jar got renamed to soapmonitor.jar during the
> > conversion to maven2 for the 1.3 release. Thanks for pointing that
> > out, I'll update the docs.
> > >
> > >HTH,
> > >Robert
> > >
> > >On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> wrote:
> > >
> > >
> > >
> > > Hi.
> > >
> > >  Where is axis2-soapmonitor.jar ? This file appears in the doc but I
> do
> > > not find it.
> > >  The command javac -classpath axis2-soapmonitor.jar
> > > SOAPMonitorApplet-java uses it.
> > >
> > >  Regards.
> > >
> > >
> > >
> > > 
> > >  Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> > > contener información clasificada por su emisor como confidencial en el
> > > marco de su Sistema de Gestión de Seguridad de la Información siendo
> > > para uso exclusivo del destinatario, quedando prohibida su divulgación
> > > copia o distribución a terceros sin la autorización expresa del
> > > remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> > > notifique al remitente y proceda a su borrado. Gracias por su
> > colaboración.
> > > 
> > >  This message including any attachments may contain confidential
> > > information, according to our Information Security Management System,
> > > and intended solely for a specific individual to whom they are
> > > addressed. Any unauthorised copy, disclosure or distribution of this
> > > message is strictly forbidden. If you have received this transmission
> > > in error, please notify the sender immediately and delete it.
> > > 
> > >
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: SOAPMonitor Problem

2007-10-09 Thread Fátima Milla Olaya


Antonio Manuel Muñiz Martín a écrit :

Ok. Thanks.

I extract the soapmonitor.jar file in root directory (/axis2) and I 
configured the axis2.xml and web.xml in axis2 distribution.
When I put the URL localhost:8080/axis2/SOAPMonitor in the browser the 
response is "The requested resource is not available".

I forgot anything?

Thanks a lot for your effort.
Regards,
Antonio.

>axis2-soapmonitor.jar got renamed to soapmonitor.jar during the 
conversion to maven2 for the 1.3 release. Thanks for pointing that 
out, I'll update the docs.

>
>HTH,
>Robert
>
>On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:

>
>
>
> Hi.
>
>  Where is axis2-soapmonitor.jar ? This file appears in the doc but I do
> not find it.
>  The command javac -classpath axis2-soapmonitor.jar
> SOAPMonitorApplet-java uses it.
>
>  Regards.
>
>
>
> 
>  Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> contener información clasificada por su emisor como confidencial en el
> marco de su Sistema de Gestión de Seguridad de la Información siendo
> para uso exclusivo del destinatario, quedando prohibida su divulgación
> copia o distribución a terceros sin la autorización expresa del
> remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> notifique al remitente y proceda a su borrado. Gracias por su 
colaboración.

> 
>  This message including any attachments may contain confidential
> information, according to our Information Security Management System,
> and intended solely for a specific individual to whom they are
> addressed. Any unauthorised copy, disclosure or distribution of this
> message is strictly forbidden. If you have received this transmission
> in error, please notify the sender immediately and delete it.
> 
>
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>
Unzip the applet classes and place them at the root of the war - for 
example axis2/SOAPMonitorApplet*.class


Suerte!

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

SOAPMonitor Problem

Ok. Thanks.

I extract the soapmonitor.jar file in root directory (/axis2) and I
configured the axis2.xml and web.xml in axis2 distribution.
When I put the URL localhost:8080/axis2/SOAPMonitor in the browser the
response is "The requested resource is not available".
I forgot anything?

Thanks a lot for your effort.
Regards,
Antonio.

>axis2-soapmonitor.jar got renamed to soapmonitor.jar during the conversion
to maven2 for the 1.3 release. Thanks for pointing that out, I'll update the
docs.
>
>HTH,
>Robert
>
>On 10/9/07, Antonio Manuel Muñiz Martín <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi.
>
>  Where is axis2-soapmonitor.jar? This file appears in the doc but I do
> not find it.
>  The command javac -classpath axis2-soapmonitor.jar
> SOAPMonitorApplet-java uses it.
>
>  Regards.
>
>
>
> 
>  Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> contener información clasificada por su emisor como confidencial en el
> marco de su Sistema de Gestión de Seguridad de la Información siendo
> para uso exclusivo del destinatario, quedando prohibida su divulgación
> copia o distribución a terceros sin la autorización expresa del
> remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo
> notifique al remitente y proceda a su borrado. Gracias por su
colaboración.
> 
>  This message including any attachments may contain confidential
> information, according to our Information Security Management System,
> and intended solely for a specific individual to whom they are
> addressed. Any unauthorised copy, disclosure or distribution of this
> message is strictly forbidden. If you have received this transmission
> in error, please notify the sender immediately and delete it.
> 
>
>
>

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

Re: SOAPMonitor for axis2

2007-09-24 Thread robert lazarski

Read the instructions carefully - you need the source distro to
compile the applet. Alternatively, unpack the soapmonitor jar as
explained in the instructions - the applet classes are already
compiled there but they must be moved properly to the right location.

HTH,
Robert

On 9/24/07, Fátima Milla Olaya <[EMAIL PROTECTED]> wrote:
> Hi, I want to use the module SOAPMonitor, in the instructions  it is
> said to compile the applet classes but in the soapmonitor.jar there
> aren't any java files, when I start the SOAPMonitor and I open the Java
> console the error is that it can't find the soapmonitorapplet. Thanks
>
> -
> 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]

SOAPMonitor for axis2

2007-09-24 Thread Fátima Milla Olaya

Hi, I want to use the module SOAPMonitor, in the instructions  it is 
said to compile the applet classes but in the soapmonitor.jar there 
aren't any java files, when I start the SOAPMonitor and I open the Java 
console the error is that it can't find the soapmonitorapplet. Thanks


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

Re: (Rampart) Not seeing encrypted message in SOAPMonitor

2007-09-02 Thread Amila Suriarachchi

Can you please ask this question at
http://ws.apache.org/rampart/

On 9/2/07, A Sunley <[EMAIL PROTECTED]> wrote:
>
>
> Hi folks,
>
> I'm something of a rookie when it comes to implementing security in web
> services. I'm working with policy example #3 to try and get an idea for
> how
> security policy works. Direct link here:
>
> https://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/policy/sample03/
>
> I've changed the invoked web service method but the policy is the same,
> but
> I'm a bit confused by something. As I understand it the soap message body
> in
> this example should be encrypted, correct? But looking at the messages in
> SOAPMonitor, I am seeing the security header but the body in plain text.
> Is
> the policy not being applied properly?
>
> I'm also seeing differences in the response shown in SOAPMonitor and a
> printout of the OMElement response in the client (messages displayed
> below).
> The OMElement shows the wsa, xenc and wsu namespaces while SOAPMonitor
> does
> not.
>
> Basically I'm a bit confused by what I am seeing in SOAPMonitor and I'm
> not
> sure whether this is indicating that the policy is not being applied
> properly or whether this is typical behaviour of SOAPMonitor itself?
>
> Also, despite reading into WS-Policy I'm still rather unsure of it,
> generally. Are there any guides to creating policy documents? Ultimately
> my
> aim is for the requests to the service to have a UsernameToken and the
> SOAP
> body encrypted. And the response message body to be encrypted.
>
>
>
> SOAPMonitor Request Body:
>
> 
>  xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
> "
> wsu:Id="Id-21192393">
> http://webservice.example.com/xsd";>
>   username
>   pas
> 
>   
> 
>
>
> SOAPMonitor Response Message:
>
> http://schemas.xmlsoap.org/soap/envelope/
> ">
>   
> http://webservice.example.com/xsd";>
>   
> http://schema.example.com/xsd
> ">0
> http://schema.example.com/xsd";>Request
> Fulfilled
>   
> 
>   
> 
>
>
> Printout of response message at client:
>
> http://webservice.example.com/xsd";
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://www.w3.org/2005/08/addressing";
> xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";
> xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
> ">
> 
> http://schema.example.com/xsd";
> mlns="http://schema.example.com/xsd";>0
> http://schema.example.com/xsd";
> xmlns:axis2ns8="http://schema.example.com/xsd";>Request
> Fulfilled
> 
> 
>
>
> Regards,
> Alan.
>
> --
> View this message in context:
> http://www.nabble.com/%28Rampart%29-Not-seeing-encrypted-message-in-SOAPMonitor-tf4368000.html#a1245
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

(Rampart) Not seeing encrypted message in SOAPMonitor

2007-09-02 Thread A Sunley

Hi folks,

I'm something of a rookie when it comes to implementing security in web
services. I'm working with policy example #3 to try and get an idea for how
security policy works. Direct link here:
https://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/policy/sample03/

I've changed the invoked web service method but the policy is the same, but
I'm a bit confused by something. As I understand it the soap message body in
this example should be encrypted, correct? But looking at the messages in
SOAPMonitor, I am seeing the security header but the body in plain text. Is
the policy not being applied properly?

I'm also seeing differences in the response shown in SOAPMonitor and a
printout of the OMElement response in the client (messages displayed below).
The OMElement shows the wsa, xenc and wsu namespaces while SOAPMonitor does
not.

Basically I'm a bit confused by what I am seeing in SOAPMonitor and I’m not
sure whether this is indicating that the policy is not being applied
properly or whether this is typical behaviour of SOAPMonitor itself?

Also, despite reading into WS-Policy I'm still rather unsure of it,
generally. Are there any guides to creating policy documents? Ultimately my
aim is for the requests to the service to have a UsernameToken and the SOAP
body encrypted. And the response message body to be encrypted.

SOAPMonitor Request Body:

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
wsu:Id="Id-21192393">
http://webservice.example.com/xsd";>
username
pas

SOAPMonitor Response Message:

http://schemas.xmlsoap.org/soap/envelope/";>

http://webservice.example.com/xsd";>

http://schema.example.com/xsd";>0
http://schema.example.com/xsd";>Request
Fulfilled

Printout of response message at client:

http://webservice.example.com/xsd";
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:xenc="http://www.w3.org/2001/04/xmlenc#";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>

http://schema.example.com/xsd";
mlns="http://schema.example.com/xsd";>0
http://schema.example.com/xsd";
xmlns:axis2ns8="http://schema.example.com/xsd";>Request
Fulfilled

Regards,
Alan.

--
View this message in context:
http://www.nabble.com/%28Rampart%29-Not-seeing-encrypted-message-in-SOAPMonitor-tf4368000.html#a1245
Sent from the Axis - User mailing list archive at Nabble.com.

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

Re: Implementing SOAPMonitor in AXIS2

2007-08-23 Thread Lahiru Sandakith

Hi,

Basically the idea of theSOAPMonitor is to  monitor these SOAP messages
without requiring any special configuration or restarting the server. This
document [1] covers steps that how you can activate the SOAP Monitor as  an
Applet inside the axis2 webapp,

Thanks

Lahiru.

[1] http://ws.apache.org/axis2/1_3/soapmonitor-module.html



On 8/23/07, Karuppusamy, Thamayanthi (Consultant)
<[EMAIL PROTECTED]
> wrote:
>
>  Hi,
>
>   Can anybody explain what is the use of SOAPMonitor and how to implement
> that one axis2?
>
> Thanks & Regards
> Thamayanthi Karuppusamy
>
>
> --
>
> * This email may contain confidential and privileged material for the sole
> use of the intended recipient(s). Any review, use, retention, distribution
> or disclosure by others is strictly prohibited. If you are not the intended
> recipient (or authorized to receive for the recipient), please contact the
> sender by reply email and delete all copies of this message. Also, email is
> susceptible to data corruption, interception, tampering, unauthorized
> amendment and viruses. We only send and receive emails on the basis that we
> are not liable for any such corruption, interception, tampering, amendment
> or viruses or any consequence thereof. *
>



-- 
Thanks
Lahiru Sandakith

http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC  1AB1 FE5E 7464 1F01 9A0F

RE: Axis2 1.2 SOAPMonitor

2007-07-18 Thread Michael.Davis

Also, tcpmonitor looks just like the soapmonitor and it's very easy to use.
 
http://ws.apache.org/commons/tcpmon/
 

cheers,
md
  

-Original Message-
From: Co Braspenning [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 6:52 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 1.2 SOAPMonitor


Hi Madhav, 

You can use the stand alone SOAPUI program for this purpose, i think.
SOAPUI can be found on SourceForge.

Co

Op 18-jul-2007, om 12:46 heeft < [EMAIL PROTECTED]> < [EMAIL PROTECTED]> het 
volgende geschreven:


Hi,
 
Can we use soap monitor without any web app container (Tomcat etc.). I mean the 
module archive 'soapmonitor-1.2.mar' is already present in 
'C:\axis2-1.2\repository\modules' directory? I'm using the 'axis2server.bat' 
command to start the axis server (Axis2 1.2).
 
Thanks, 
Madhav

Re: Axis2 1.2 SOAPMonitor

2007-07-18 Thread Co Braspenning


Hi Madhav,

You can use the stand alone SOAPUI program for this purpose, i think.
SOAPUI can be found on SourceForge.

Co

Op 18-jul-2007, om 12:46 heeft <[EMAIL PROTECTED]>  
<[EMAIL PROTECTED]> het volgende geschreven:



Hi,

Can we use soap monitor without any web app container (Tomcat  
etc.). I mean the module archive 'soapmonitor-1.2.mar' is already  
present in 'C:\axis2-1.2\repository\modules' directory? I'm using  
the 'axis2server.bat' command to start the axis server (Axis2 1.2).


Thanks,
Madhav

Axis2 1.2 SOAPMonitor

2007-07-18 Thread ranjan.madhav

Hi,
 
Can we use soap monitor without any web app container (Tomcat etc.). I
mean the module archive 'soapmonitor-1.2.mar' is already present in
'C:\axis2-1.2\repository\modules' directory? I'm using the
'axis2server.bat' command to start the axis server (Axis2 1.2).
 
Thanks, 
Madhav

Re: How to password protect access to SOAPMonitor

2007-06-20 Thread robert lazarski

It might require more effort than your time permits, so I would say disable
the soapmonitor module until you need it.

Since this really has nothing to do with axis2 - you just want to password
protect a url - there really is nothing to integrate. The way I'd do it -
acegi - is far beyond the scope of axis2 I'd imagine.

Robert

On 6/20/07, Gul Onural <[EMAIL PROTECTED]> wrote:

 How easy is this? We are about to deliver the product for trial and I
cannot make to much change right now.
Are you planning to integrate this solution to next version of Axis2 ?

Gul

 --
*From:* robert lazarski [mailto:[EMAIL PROTECTED]
*Sent:* Wednesday, June 20, 2007 8:55 PM
*To:* axis-user@ws.apache.org
*Subject:* Re: How to password protect access to SOAPMonitor

I tend to put basic auth on the soap monitor using acegi - a security
framework that requires spring, but doesn't need any axis2 / spring
integration. If you decide to go that route I can help you implement it as
its pretty easy once you know how to do it.

Robert

On 6/20/07, Gul Onural <[EMAIL PROTECTED]> wrote:
>
>  Hi,
>
> I noticed that the SOAPMonitor is not protected with userId/password. If
> somebody knows the url of the service,
> he can then launch the SOAPMonitor and see the messages coming back and
> forth.
>
> Is there a way to password protect the SOAPMonitor, or we just have to
> take it out from our production system?
>
> Gul
>

RE: How to password protect access to SOAPMonitor

2007-06-20 Thread Gul Onural

How easy is this? We are about to deliver the product for trial and I
cannot make to much change right now.
Are you planning to integrate this solution to next version of Axis2 ?
 
Gul



From: robert lazarski [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 20, 2007 8:55 PM
To: axis-user@ws.apache.org
Subject: Re: How to password protect access to SOAPMonitor


I tend to put basic auth on the soap monitor using acegi - a security
framework that requires spring, but doesn't need any axis2 / spring
integration. If you decide to go that route I can help you implement it
as its pretty easy once you know how to do it. 

Robert 


On 6/20/07, Gul Onural <[EMAIL PROTECTED]> wrote: 

Hi,
 
I noticed that the SOAPMonitor is not protected with
userId/password. If somebody knows the url of the service,
he can then launch the SOAPMonitor and see the messages coming
back and forth.
 
Is there a way to password protect the SOAPMonitor, or we just
have to take it out from our production system?
 
Gul

Re: How to password protect access to SOAPMonitor

2007-06-20 Thread Martin Gainty

When used with ORM tools such as hibernate with lazy-init="true" where 
LazyInitializaionExceptions happen you'll want to look into
OpenSessionInViewFilter
http://www.thearcmind.com/confluence/display/SpribernateSF/Configuring+Hibernate,+Spring,+OpenInSessionViewFilter+and+MyFaces+JSF

Automatically assigning the datasource for all beans from the configured 
BeanFactory thru Spring is a nice advantage though
http://static.springframework.org/spring/docs/1.1.5/reference/transactionhtml

M--

This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  - Original Message - 
  From: robert lazarski 
  To: axis-user@ws.apache.org 
  Sent: Wednesday, June 20, 2007 8:54 PM
  Subject: Re: How to password protect access to SOAPMonitor


  I tend to put basic auth on the soap monitor using acegi - a security 
framework that requires spring, but doesn't need any axis2 / spring 
integration. If you decide to go that route I can help you implement it as its 
pretty easy once you know how to do it. 

  Robert 


  On 6/20/07, Gul Onural <[EMAIL PROTECTED]> wrote:
Hi,

I noticed that the SOAPMonitor is not protected with userId/password. If 
somebody knows the url of the service,
    he can then launch the SOAPMonitor and see the messages coming back and 
forth.

Is there a way to password protect the SOAPMonitor, or we just have to take 
it out from our production system?

Gul

Re: How to password protect access to SOAPMonitor

2007-06-20 Thread robert lazarski


I tend to put basic auth on the soap monitor using acegi - a security
framework that requires spring, but doesn't need any axis2 / spring
integration. If you decide to go that route I can help you implement it as
its pretty easy once you know how to do it.

Robert

On 6/20/07, Gul Onural <[EMAIL PROTECTED]> wrote:


 Hi,

I noticed that the SOAPMonitor is not protected with userId/password. If
somebody knows the url of the service,
he can then launch the SOAPMonitor and see the messages coming back and
forth.

Is there a way to password protect the SOAPMonitor, or we just have to
take it out from our production system?

Gul

Re: How to password protect access to SOAPMonitor

2007-06-20 Thread Martin Gainty

Have you looked into Rampart?
http://ws.apache.org/axis2/modules/rampart/1_2/security-module.html

M--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

  - Original Message - 
  From: Gul Onural 
  To: axis-user@ws.apache.org 
  Sent: Wednesday, June 20, 2007 7:55 PM
  Subject: How to password protect access to SOAPMonitor 


  Hi,

  I noticed that the SOAPMonitor is not protected with userId/password. If 
somebody knows the url of the service,
  he can then launch the SOAPMonitor and see the messages coming back and forth.

  Is there a way to password protect the SOAPMonitor, or we just have to take 
it out from our production system?

  Gul

How to password protect access to SOAPMonitor

2007-06-20 Thread Gul Onural

Hi,
 
I noticed that the SOAPMonitor is not protected with userId/password. If
somebody knows the url of the service,
he can then launch the SOAPMonitor and see the messages coming back and
forth.
 
Is there a way to password protect the SOAPMonitor, or we just have to
take it out from our production system?
 
Gul

Re: AXIS 2 Service SOAPMonitor

2007-06-18 Thread Chris Shah

I was trying to figure out how to get it to work with the standalone server . 
But that does not work. I deployed the axis war to tomcat and could configure 
SOAPMonitor. I will configure the tcpmon now. 
   
  Chris

robert lazarski <[EMAIL PROTECTED]> wrote:
  Can you elaborate on 'things do not work' ?  Don't forget to edit web.xml 
also. 

Anyways, use tcpmon for mtom for now as the soapmonitor still doesn't do mime 
parts. 

HTH,
Robert 

  On 6/18/07, Chris Shah <[EMAIL PROTECTED]> wrote:What is better to use to 
monitor the sample AXIS2 MTOM Service ? SOAPMonitor ot tcpmonitor. 
   
  I am struggling to install SOAPMonitor but am failing. I have unjarred the 
SOAPMonitor Applet classes here : 
   
  c:\axis2-1.2\webapp AND changed my web.xml and added 
  to axis2.xml. 
   
  But things do not work. ANy pointers ?
   
  Thanks
  Chris
   
   
  
  
-
  Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games.   




   
-
Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV.

Re: AXIS 2 Service SOAPMonitor

2007-06-18 Thread robert lazarski


Can you elaborate on 'things do not work' ?  Don't forget to edit web.xmlalso.

Anyways, use tcpmon for mtom for now as the soapmonitor still doesn't do
mime parts.

HTH,
Robert

On 6/18/07, Chris Shah <[EMAIL PROTECTED]> wrote:


What is better to use to monitor the sample AXIS2 MTOM Service ?
SOAPMonitor ot tcpmonitor.

I am struggling to install SOAPMonitor but am failing. I have unjarred the
SOAPMonitor Applet classes here :

c:\axis2-1.2\webapp AND changed my web.xml and added 
to axis2.xml.

But things do not work. ANy pointers ?

Thanks
Chris



--
Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games.
<http://us.rd.yahoo.com/evt=48224/*http://sims.yahoo.com/>

AXIS 2 Service SOAPMonitor

2007-06-18 Thread Chris Shah

What is better to use to monitor the sample AXIS2 MTOM Service ? SOAPMonitor ot 
tcpmonitor. 
   
  I am struggling to install SOAPMonitor but am failing. I have unjarred the 
SOAPMonitor Applet classes here : 
   
  c:\axis2-1.2\webapp AND changed my web.xml and added 
  to axis2.xml. 
   
  But things do not work. ANy pointers ?
   
  Thanks
  Chris
   
   

   
-
Moody friends. Drama queens. Your life? Nope! - their life, your story.
 Play Sims Stories at Yahoo! Games.

Re: Axis1.4 error to enable SOAPMonitor applet is not loading

2007-06-03 Thread Vikas

Thanks Michael ..

Solved my problem ...

With best regards

From
Vikas R. Khengare

- Original Message - 
From: <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Friday, June 01, 2007 11:22 PM
Subject: RE: Axis1.4 error to enable SOAPMonitor applet is not loading


> Try moving the SOAPMonitor classes to apache-tomcat-5.5.17/webapps/axis.
The applet loader is trying to find the class in the context root, not in
WEB-INF/classes.
>
> cheers
> Michael Davis
>
> -Original Message-
> From: Vikas [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 01, 2007 3:06 AM
> To: axis user
> Subject: Axis1.4 error to enable SOAPMonitor applet is not loading
>
>
> Hi Friends,
>
> I have just installed "axis-1_4", every thing is ok, but SOAP monitor is
not working.
> When I click link http://localhost:8080/axis/ ; it will show us options
validation, list, call ... & SOAPMonitor(this option are disabled by
default).
> So I have enabled that option though "WEB-INF/web.xml", but SOAPMonitor
applet is not loading.
>
> Rest of all links(validation, list, call etc.) are working very well.
>
> All SOAPMonitor*.class files are in
"apache-tomcat-5.5.17\webapps\axis\WEB-INF\classes"
>
> Stack trace is as follows
>
> load: class SOAPMonitorApplet.class not found.
> java.lang.ClassNotFoundException: SOAPMonitorApplet.class
>  at sun.applet.AppletClassLoader.findClass(Unknown Source)
>  at java.lang.ClassLoader.loadClass(Unknown Source)
>  at sun.applet.AppletClassLoader.loadClass(Unknown Source)
>  at java.lang.ClassLoader.loadClass(Unknown Source)
>  at sun.applet.AppletClassLoader.loadCode(Unknown Source)
>  at sun.applet.AppletPanel.createApplet(Unknown Source)
>  at sun.plugin.AppletViewer.createApplet(Unknown Source)
>  at sun.applet.AppletPanel.runLoader(Unknown Source)
>  at sun.applet.AppletPanel.run(Unknown Source)
>  at java.lang.Thread.run(Unknown Source)
> Caused by: java.io.IOException: open HTTP connection failed.
>  at sun.applet.AppletClassLoader.getBytes(Unknown Source)
>  at sun.applet.AppletClassLoader.access$100(Unknown Source)
>  at sun.applet.AppletClassLoader$1.run(Unknown Source)
>  at java.security.AccessController.doPrivileged(Native Method)
>  ... 10 more
> Exception in thread "Thread-4" java.lang.NullPointerException
>  at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
>  at sun.plugin.AppletViewer.showAppletException(Unknown Source)
>  at sun.applet.AppletPanel.runLoader(Unknown Source)
>  at sun.applet.AppletPanel.run(Unknown Source)
>  at java.lang.Thread.run(Unknown Source)
> java.lang.NullPointerException
>  at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
>  at sun.plugin.AppletViewer.showAppletStatus(Unknown Source)
>  at sun.applet.AppletPanel.run(Unknown Source)
>  at java.lang.Thread.run(Unknown Source)
> Exception in thread "thread applet-SOAPMonitorApplet.class"
java.lang.NullPointerException
>  at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
>  at sun.plugin.AppletViewer.showAppletException(Unknown Source)
>  at sun.applet.AppletPanel.run(Unknown Source)
>  at java.lang.Thread.run(Unknown Source)
>
> Can some one will help me?
>
> With best regards
>
> From
> Vikas R. Khengare


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

RE: Axis1.4 error to enable SOAPMonitor applet is not loading

2007-06-01 Thread Michael.Davis

Try moving the SOAPMonitor classes to apache-tomcat-5.5.17/webapps/axis. The 
applet loader is trying to find the class in the context root, not in 
WEB-INF/classes.

cheers
Michael Davis

-Original Message-
From: Vikas [mailto:[EMAIL PROTECTED]
Sent: Friday, June 01, 2007 3:06 AM
To: axis user
Subject: Axis1.4 error to enable SOAPMonitor applet is not loading


Hi Friends,

I have just installed "axis-1_4", every thing is ok, but SOAP monitor is not 
working.
When I click link http://localhost:8080/axis/ ; it will show us options 
validation, list, call ... & SOAPMonitor(this option are disabled by default).
So I have enabled that option though "WEB-INF/web.xml", but SOAPMonitor applet 
is not loading.

Rest of all links(validation, list, call etc.) are working very well.

All SOAPMonitor*.class files are in 
"apache-tomcat-5.5.17\webapps\axis\WEB-INF\classes"

Stack trace is as follows

load: class SOAPMonitorApplet.class not found.
java.lang.ClassNotFoundException: SOAPMonitorApplet.class
 at sun.applet.AppletClassLoader.findClass(Unknown Source)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at sun.applet.AppletClassLoader.loadClass(Unknown Source)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at sun.applet.AppletClassLoader.loadCode(Unknown Source)
 at sun.applet.AppletPanel.createApplet(Unknown Source)
 at sun.plugin.AppletViewer.createApplet(Unknown Source)
 at sun.applet.AppletPanel.runLoader(Unknown Source)
 at sun.applet.AppletPanel.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: open HTTP connection failed.
 at sun.applet.AppletClassLoader.getBytes(Unknown Source)
 at sun.applet.AppletClassLoader.access$100(Unknown Source)
 at sun.applet.AppletClassLoader$1.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 ... 10 more
Exception in thread "Thread-4" java.lang.NullPointerException
 at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
 at sun.plugin.AppletViewer.showAppletException(Unknown Source)
 at sun.applet.AppletPanel.runLoader(Unknown Source)
 at sun.applet.AppletPanel.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
 at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
 at sun.plugin.AppletViewer.showAppletStatus(Unknown Source)
 at sun.applet.AppletPanel.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
Exception in thread "thread applet-SOAPMonitorApplet.class" 
java.lang.NullPointerException
 at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
 at sun.plugin.AppletViewer.showAppletException(Unknown Source)
 at sun.applet.AppletPanel.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

Can some one will help me?

With best regards

From
Vikas R. Khengare

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

Axis1.4 error to enable SOAPMonitor applet is not loading

2007-06-01 Thread Vikas

Hi Friends,

I have just installed "axis-1_4", every thing is ok, but SOAP monitor is not 
working.
When I click link http://localhost:8080/axis/ ; it will show us options 
validation, list, call ... & SOAPMonitor(this option are disabled by default).
So I have enabled that option though "WEB-INF/web.xml", but SOAPMonitor applet 
is not loading.

Rest of all links(validation, list, call etc.) are working very well.

All SOAPMonitor*.class files are in 
"apache-tomcat-5.5.17\webapps\axis\WEB-INF\classes"

Stack trace is as follows

load: class SOAPMonitorApplet.class not found.
java.lang.ClassNotFoundException: SOAPMonitorApplet.class
 at sun.applet.AppletClassLoader.findClass(Unknown Source)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at sun.applet.AppletClassLoader.loadClass(Unknown Source)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at sun.applet.AppletClassLoader.loadCode(Unknown Source)
 at sun.applet.AppletPanel.createApplet(Unknown Source)
 at sun.plugin.AppletViewer.createApplet(Unknown Source)
 at sun.applet.AppletPanel.runLoader(Unknown Source)
 at sun.applet.AppletPanel.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: open HTTP connection failed.
 at sun.applet.AppletClassLoader.getBytes(Unknown Source)
 at sun.applet.AppletClassLoader.access$100(Unknown Source)
 at sun.applet.AppletClassLoader$1.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 ... 10 more
Exception in thread "Thread-4" java.lang.NullPointerException
 at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
 at sun.plugin.AppletViewer.showAppletException(Unknown Source)
 at sun.applet.AppletPanel.runLoader(Unknown Source)
 at sun.applet.AppletPanel.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
 at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
 at sun.plugin.AppletViewer.showAppletStatus(Unknown Source)
 at sun.applet.AppletPanel.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
Exception in thread "thread applet-SOAPMonitorApplet.class" 
java.lang.NullPointerException
 at sun.plugin.util.GrayBoxPainter.showLoadingError(Unknown Source)
 at sun.plugin.AppletViewer.showAppletException(Unknown Source)
 at sun.applet.AppletPanel.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

Can some one will help me?

With best regards

From
Vikas R. Khengare

Re: SoapMonitor NullPointerException

2007-02-19 Thread Thilina Gunarathne


Please post a JIRA along with your axis2.xml NPE is not acceptable at all...

Thanks,
Thilina

On 2/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


Hi,

Where have you placed the soapmonitorPhase?
You can get a NPE if it is placed with the system phases!

Regards
Multi-Support A/S

Torben Riis

Phone +45 96 600 600, Fax +45 96 600 601
E-mail: [EMAIL PROTECTED]
http://www.multi-support.com



 "Kang, Kamaljeet
 K."
 <[EMAIL PROTECTED]  To
 labs.com> 
cc
 16-02-2007 09:22
   Subject
       SoapMonitor NullPointerException
 Please respond to
 [EMAIL PROTECTED]
  he.org







Hi,

Enabling SOAPMonitor is throwing NPE and causing an operation to fail.
It works fine if SOAPMonitor is not enabled. Why would failure in
SOAPMonitor module result in operation failure?


org.apache.axis2.AxisFault: java.lang.NullPointerException
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java
:396)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:352)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:273)
at
tellabs.mtosi.DiscoveryServiceStub.getAllCapabilities(DiscoveryServiceSt
ub.java:170)
at
tellabs.mtosi.DiscoveryServiceStub.main(DiscoveryServiceStub.java:464)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault:
java.lang.NullPointerException; nested exception is:
java.lang.NullPointerException
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:319)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:228)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2
12)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:81
8)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
Http11Protocol.java:624)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr(BaseNsStreamWriter.java:4
67)
at
com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute(BaseNsStreamWriter.jav
a:229)
at
org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeAttribute(MTOMXMLStrea
mWriter.java:134)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSeri
alizerUtil.java:387)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSeri
alizerUtil.java:171)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:803)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMS
ourcedElementImpl.java:555)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:792)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMS
ourcedElementImpl.java:546)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:807)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:792)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:807)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPE
nvelopeImpl.java:180)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:792)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:
951)


kamal

The information contained in this message may be privileged
and confidential and protected from disclo

Re: SoapMonitor NullPointerException

2007-02-18 Thread riis


Hi,

Where have you placed the soapmonitorPhase?
You can get a NPE if it is placed with the system phases!

Regards
Multi-Support A/S

Torben Riis

Phone +45 96 600 600, Fax +45 96 600 601
E-mail: [EMAIL PROTECTED]
http://www.multi-support.com


   
 "Kang, Kamaljeet  
 K."   
 <[EMAIL PROTECTED]  To 
 labs.com>
cc 
 16-02-2007 09:22  
   Subject 
       SoapMonitor NullPointerException
 Please respond to 
 [EMAIL PROTECTED] 
  he.org   
   
   
   




Hi,

Enabling SOAPMonitor is throwing NPE and causing an operation to fail.
It works fine if SOAPMonitor is not enabled. Why would failure in
SOAPMonitor module result in operation failure?


org.apache.axis2.AxisFault: java.lang.NullPointerException
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java
:396)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:352)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:273)
at
tellabs.mtosi.DiscoveryServiceStub.getAllCapabilities(DiscoveryServiceSt
ub.java:170)
at
tellabs.mtosi.DiscoveryServiceStub.main(DiscoveryServiceStub.java:464)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault:
java.lang.NullPointerException; nested exception is:
java.lang.NullPointerException
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:319)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:228)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2
12)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:81
8)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
Http11Protocol.java:624)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr(BaseNsStreamWriter.java:4
67)
at
com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute(BaseNsStreamWriter.jav
a:229)
at
org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeAttribute(MTOMXMLStrea
mWriter.java:134)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSeri
alizerUtil.java:387)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSeri
alizerUtil.java:171)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:803)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMS
ourcedElementImpl.java:555)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:792)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMS
ourcedElementImpl.java:546)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:807)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:792)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:807)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPE
nvelopeImpl.java

SoapMonitor NullPointerException

2007-02-16 Thread Kang, Kamaljeet K.

Hi,

Enabling SOAPMonitor is throwing NPE and causing an operation to fail.
It works fine if SOAPMonitor is not enabled. Why would failure in
SOAPMonitor module result in operation failure?

 
org.apache.axis2.AxisFault: java.lang.NullPointerException
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java
:396)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:352)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:273)
at
tellabs.mtosi.DiscoveryServiceStub.getAllCapabilities(DiscoveryServiceSt
ub.java:170)
at
tellabs.mtosi.DiscoveryServiceStub.main(DiscoveryServiceStub.java:464)
Caused by: java.lang.Exception: org.apache.axis2.AxisFault:
java.lang.NullPointerException; nested exception is: 
java.lang.NullPointerException
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:319)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:228)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:2
12)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:81
8)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
Http11Protocol.java:624)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
at
com.ctc.wstx.sw.BaseNsStreamWriter.doWriteAttr(BaseNsStreamWriter.java:4
67)
at
com.ctc.wstx.sw.BaseNsStreamWriter.writeAttribute(BaseNsStreamWriter.jav
a:229)
at
org.apache.axiom.om.impl.MTOMXMLStreamWriter.writeAttribute(MTOMXMLStrea
mWriter.java:134)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSeri
alizerUtil.java:387)
at
org.apache.axiom.om.impl.util.OMSerializerUtil.serializeStartpart(OMSeri
alizerUtil.java:171)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:803)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMS
ourcedElementImpl.java:555)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:792)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMS
ourcedElementImpl.java:546)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:807)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:792)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:807)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPE
nvelopeImpl.java:180)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementI
mpl.java:792)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345)
at
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:
951)


kamal

The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs


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

Re: engaging soapmonitor-1.1 in Axis2

2007-01-18 Thread Sathija Pavuluri

You can use tcpmon as well to sniff axis request and response messages.
I thought it was easier to setup and is quite easy to use.

You just need to run the launch script from the download's bin and setup the 
port on which you want to sniff.
Make sure your requests are sent to this port from where they will be forwarded 
onto where ever your services are
deployed.

http://ws.apache.org/commons/tcpmon/


HTH.
Sathija.



> I have a webservices written. It is running correctly as far as I can
> tell. I have a client that's calling the service and is receiving the
> correct responses. Next week, I plan to give a small demo to my
> management. I thought of using soapmonitor in the Axis2 Administrator
> webapp. I was able to "engage" a servicer and/or an "operation" with
> soapmonitor-1.1 module. What do I need to do next so that I can have a
> visual for webservices activities other than usiing the debug logs?
>
> Thanks.
>
> Danny
>
>



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

RE: engaging soapmonitor-1.1 in Axis2

2007-01-18 Thread Gul Onural

copy axis2-soapmonitor-1.1.jar to a temp directory and do : 
jar -xf axis2-soapmonitor-1.1.jar 
 
This jar file is normally located under axis2-\lib 
as part of the axis2 distro.

 
Then remove axis2-soapmonitor-1.1.jar from the temp directory.

List of files under the temp directory should look like :
META-INF
org
SOAPMonitorApplet$ServiceFilterPanel.class
SOAPMonitorApplet$SOAPMonitorData.class
SOAPMonitorApplet$SOAPMonitorFilter.class
SOAPMonitorApplet$SOAPMonitorPage.class
SOAPMonitorApplet$SOAPMonitorTableModel.class
SOAPMonitorApplet$SOAPMonitorTextArea.class
SOAPMonitorApplet.class
 
Copy everything under temp directory to axis2\ which is
your axis2 installation directory (note that if you use tomcat to deploy
axis2, the directory is apache-tomcat-\webapps\axis2)
 
Gul
 
PS : Depending on what version of axis2 you are using the version part
of the name of the axis2-soapmonitor.jar
file might be different (i.e. it could be SNAPSHOT or 1.1.1)
 



From: Danny Lin [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 18, 2007 4:37 PM
To: axis-user@ws.apache.org
Subject: engaging soapmonitor-1.1 in Axis2


I have a webservices written. It is running correctly as far as I can
tell. I have a client that's calling the service and is receiving the
correct responses. Next week, I plan to give a small demo to my
management. I thought of using soapmonitor in the Axis2 Administrator
webapp. I was able to "engage" a servicer and/or an "operation" with
soapmonitor-1.1 module. What do I need to do next so that I can have a
visual for webservices activities other than usiing the debug logs?
 
Thanks.
 
Danny

engaging soapmonitor-1.1 in Axis2

2007-01-18 Thread Danny Lin

I have a webservices written. It is running correctly as far as I can
tell. I have a client that's calling the service and is receiving the
correct responses. Next week, I plan to give a small demo to my
management. I thought of using soapmonitor in the Axis2 Administrator
webapp. I was able to "engage" a servicer and/or an "operation" with
soapmonitor-1.1 module. What do I need to do next so that I can have a
visual for webservices activities other than usiing the debug logs?
 
Thanks.
 
Danny

[Axis2] Re: How to get the request envelope without using soapmonitor or tcpmon

2006-12-30 Thread falom

Hi Thilina,

Thanks for the help. But how to engage the logging module at the client side, 
the Axis2 documentation is about enabling logging module at the server side. Do 
you have any sample on how to programmatically enable a module? Thanks!

falom

Thilina Gunarathne <[EMAIL PROTECTED]> 写道： You can write a module containing 
handlers to intercept and print the
message before sending.. This doc [1] talks about how to write an
Axis2 module which is logs the messages..

~Thilina
[1] http://ws.apache.org/axis2/1_1/modules.html

On 12/31/06, falom  wrote:
> Hi,
>
> Anyone help me how to print out the request envelope at the client side,
> before or after sending the request, thanks!
>
> falom
>

-- 
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

 __
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com

Re: [Axis2] How to get the request envelope without using soapmonitor or tcpmon

2006-12-30 Thread Thilina Gunarathne


You can write a module containing handlers to intercept and print the
message before sending.. This doc [1] talks about how to write an
Axis2 module which is logs the messages..

~Thilina
[1] http://ws.apache.org/axis2/1_1/modules.html

On 12/31/06, falom <[EMAIL PROTECTED]> wrote:

Hi,

Anyone help me how to print out the request envelope at the client side,
before or after sending the request, thanks!

falom


 __
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com



--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

[Axis2] How to get the request envelope without using soapmonitor or tcpmon

2006-12-30 Thread falom

Hi,

Anyone help me how to print out the request envelope at the client side, before 
or after sending the request, thanks!

falom

 __
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com

Re: axis2-soapmonitor*.mar ?

2006-12-27 Thread Martin Gainty

when docBase="" the webapp name (in this case axis2-web) needs to be specified 
in the web.xml as in..


  404
  /axis2-web/Error/error404.jsp



500
/axis2-web/Error/error500.jsp


then each and every jsp which jsp:includes any jsp such as 
index.jsp/listServices.jsp/HappyAxis.jsp and every  needs to specify 
/webapp/folder/JSPFile.jsp specifically.. as in
/axis2-web/services/listServices.jsp

(the alternative is to use correct the null specification for docBase)

Martin --
--- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message - 
From: "Martin Gainty" <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Tuesday, December 26, 2006 6:59 PM
Subject: Re: axis2-soapmonitor*.mar ?


> after a bit of digging thru the logs I see
> 
> 
> 
> is always rewritten as 
> 
> 
> where the introductory dot dot notation makes it point to an incorrect folder
> (appears to be a bug in jsp taglib)
> 
> Thx
> Martin --
> --- 
> This e-mail message (including attachments, if any) is intended for the use 
> of the individual or entity to which it is addressed and may contain 
> information that is privileged, proprietary , confidential and exempt from 
> disclosure. If you are not the intended recipient, you are notified that any 
> dissemination, distribution or copying of this communication is strictly 
> prohibited.
> --- 
> Le présent message électronique (y compris les pièces qui y sont annexées, le 
> cas échéant) s'adresse au destinataire indiqué et peut contenir des 
> renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
> destinataire de ce document, nous vous signalons qu'il est strictement 
> interdit de le diffuser, de le distribuer ou de le reproduire.
> - Original Message - 
> From: "Davanum Srinivas" <[EMAIL PROTECTED]>
> To: ; "Martin Gainty" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, December 26, 2006 6:30 PM
> Subject: Re: axis2-soapmonitor*.mar ?
> 
> 
> I beleive this is due to the recent addition of the license headers in jsp's 
> :(
> 
> -- dims
> 
> On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
>> yes now when I deploy
>>
>> I get the same crashing bug as thomas bruckmayer
>>
>> HTTP Status 500 -
>>
>> type Exception report
>>
>> message
>>
>> description The server encountered an internal error () that prevented it
>> from fulfilling this request.
>>
>> exception
>>
>> org.apache.jasper.JasperException: An exception occurred processing JSP page
>> /axis2-web/index.jsp at line 23
>> 20: */
>> 21:   %>
>> 22:   
>> 23: 
>> 24: Axis 2 - Home
>> 25: > type="text/css"/>
>> 26:   
>>
>>  
>> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:555)
>>
>> Martin--
>> ---
>> This e-mail message (including attachments, if any) is intended for the use 
>> of the individual or entity to which it is addressed and may contain 
>> information that is privileged, proprietary , confidential and exempt from 
>> disclosure. If you are not the intended recipient, you are notified that any 
>> dissemination, distribution or copying of this communication is strictly 
>> prohibited.
>> ---
>> Le présent message électronique (y compris les pièces qui y sont annexées, 
>> le cas échéant) s'adresse au destinataire indiqué et peut contenir des 
>> renseigne

Re: axis2-soapmonitor*.mar ?

2006-12-26 Thread Thilina Gunarathne


Ooops.. The link is broken... Note the "addressing" part of the link..
Please log a JIRA... I'll fix that ASAP.. Following is the correct
URL..

http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/soapmonitor/1_1/soapmonitor-1.1.mar

Thanks,
Thilina

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:

404 on each site listed at
http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip
(It appears that the distros never made it to the mirrors)

Martin--
---
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
---
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: "robert lazarski" <[EMAIL PROTECTED]>
To: ; "Martin Gainty" <[EMAIL PROTECTED]>
Sent: Tuesday, December 26, 2006 11:46 AM
Subject: Re: axis2-soapmonitor*.mar ?


http://ws.apache.org/axis2/modules/index.html

HTH,
Robert

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
>
>
> Morning All
>
> where is axis2-soapmonitor*.mar located?
>
> Thanks,
> Martin--
> ---
> This e-mail message (including attachments, if any) is intended for the use
> of the individual or entity to which it is addressed and may contain
> information that is privileged, proprietary , confidential and exempt from
> disclosure. If you are not the intended recipient, you are notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited.
> ---
> Le présent message électronique (y compris les pièces qui y sont annexées,
> le cas échéant) s'adresse au destinataire indiqué et peut contenir des
> renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
> destinataire de ce document, nous vous signalons qu'il est strictement
> interdit de le diffuser, de le distribuer ou de le reproduire.

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





--
Thilina Gunarathne
WSO2, Inc.; http://www.wso2.com/
Home page: http://webservices.apache.org/~thilina/
Blog: http://thilinag.blogspot.com/

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

Re: axis2-soapmonitor*.mar ?

after a bit of digging thru the logs I see



is always rewritten as 


where the introductory dot dot notation makes it point to an incorrect folder
(appears to be a bug in jsp taglib)

Thx
Martin --
--- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message - 
From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: ; "Martin Gainty" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, December 26, 2006 6:30 PM
Subject: Re: axis2-soapmonitor*.mar ?


I beleive this is due to the recent addition of the license headers in jsp's :(

-- dims

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
> yes now when I deploy
>
> I get the same crashing bug as thomas bruckmayer
>
> HTTP Status 500 -
>
> type Exception report
>
> message
>
> description The server encountered an internal error () that prevented it
> from fulfilling this request.
>
> exception
>
> org.apache.jasper.JasperException: An exception occurred processing JSP page
> /axis2-web/index.jsp at line 23
> 20: */
> 21:   %>
> 22:   
> 23: 
> 24: Axis 2 - Home
> 25:  type="text/css"/>
> 26:   
>
>  
> org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:555)
>
> Martin--
> ---
> This e-mail message (including attachments, if any) is intended for the use 
> of the individual or entity to which it is addressed and may contain 
> information that is privileged, proprietary , confidential and exempt from 
> disclosure. If you are not the intended recipient, you are notified that any 
> dissemination, distribution or copying of this communication is strictly 
> prohibited.
> ---
> Le présent message électronique (y compris les pièces qui y sont annexées, le 
> cas échéant) s'adresse au destinataire indiqué et peut contenir des 
> renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
> destinataire de ce document, nous vous signalons qu'il est strictement 
> interdit de le diffuser, de le distribuer ou de le reproduire.
> - Original Message -
> From: "robert lazarski" <[EMAIL PROTECTED]>
> To: ; "Martin Gainty" <[EMAIL PROTECTED]>
> Sent: Tuesday, December 26, 2006 12:17 PM
> Subject: Re: axis2-soapmonitor*.mar ?
>
>
> Please file a jira. In the meantime, with a little help from google:
>
> -inurl:htm -inurl:html -inurl:asp intitle:"index of" +(mar|zip) 
> soapmonitor-1.1
>
> That brings up:
>
> http://www.ibiblio.org/maven/org.apache.axis2/mars/
>
> HTH,
> Robert
>
> On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
> > 404 on each site listed at
> > http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip
> > (It appears that the distros never made it to the mirrors)
> >
> > Martin--
> > ---
> > This e-mail message (including attachments, if any) is intended for the use 
> > of the individual or entity to which it is addressed and may contain 
> > information that is privileged, proprietary , confidential and exempt from 
> > disclosure. If you are not the intended recipient, you are notified that 
> > any dissemination, distribution or copying of this communication is 
> > strictly prohibited.
> > ---
> > Le présent message électronique (y compris les pièces qui y sont annexées, 
> > le cas échéant) s'adresse au destinataire indiqué et peut contenir des 
> > renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
> > destinataire de ce document,

Re: axis2-soapmonitor*.mar ?

2006-12-26 Thread Davanum Srinivas


I beleive this is due to the recent addition of the license headers in jsp's :(

-- dims

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:

yes now when I deploy

I get the same crashing bug as thomas bruckmayer

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it
from fulfilling this request.

exception

org.apache.jasper.JasperException: An exception occurred processing JSP page
/axis2-web/index.jsp at line 23
20: */
21:   %>
22:   
23: 
24: Axis 2 - Home
25: 
26:   

 
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:555)

Martin--
---
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
---
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: "robert lazarski" <[EMAIL PROTECTED]>
To: ; "Martin Gainty" <[EMAIL PROTECTED]>
Sent: Tuesday, December 26, 2006 12:17 PM
Subject: Re: axis2-soapmonitor*.mar ?


Please file a jira. In the meantime, with a little help from google:

-inurl:htm -inurl:html -inurl:asp intitle:"index of" +(mar|zip) soapmonitor-1.1

That brings up:

http://www.ibiblio.org/maven/org.apache.axis2/mars/

HTH,
Robert

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
> 404 on each site listed at
> 
http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip
> (It appears that the distros never made it to the mirrors)
>
> Martin--
> ---
> This e-mail message (including attachments, if any) is intended for the use 
of the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If you 
are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
> ---
> Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements 
de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce 
document, nous vous signalons qu'il est strictement interdit de le diffuser, de le 
distribuer ou de le reproduire.
> - Original Message -
> From: "robert lazarski" <[EMAIL PROTECTED]>
> To: ; "Martin Gainty" <[EMAIL PROTECTED]>
> Sent: Tuesday, December 26, 2006 11:46 AM
> Subject: Re: axis2-soapmonitor*.mar ?
>
>
> http://ws.apache.org/axis2/modules/index.html
>
> HTH,
> Robert
>
> On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
> >
> >
> > Morning All
> >
> > where is axis2-soapmonitor*.mar located?
> >
> > Thanks,
> > Martin--
> > ---
> > This e-mail message (including attachments, if any) is intended for the use
> > of the individual or entity to which it is addressed and may contain
> > information that is privileged, proprietary , confidential and exempt from
> > disclosure. If you are not the intended recipient, you are notified that any
> > dissemination, distribution or copying of this communication is strictly
> > prohibited.
> > ---
> > Le présent message électronique (y compris les pièces qui y sont annexées,
> > le cas échéant) s'adresse au destinataire indiqué et peut contenir des
> > renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
> > destinataire de ce document, nous vous signalons qu'il est strictement
> > interdit de le diffuser, de le distribuer ou de le reproduire.
>
> -
>

Re: axis2-soapmonitor*.mar ?

yes now when I deploy

I get the same crashing bug as thomas bruckmayer

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it
from fulfilling this request.

exception

org.apache.jasper.JasperException: An exception occurred processing JSP page
/axis2-web/index.jsp at line 23
20: */
21:   %>
22:   
23: 
24: Axis 2 - Home
25: 
26:   

 
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:555)

Martin--
--- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message - 
From: "robert lazarski" <[EMAIL PROTECTED]>
To: ; "Martin Gainty" <[EMAIL PROTECTED]>
Sent: Tuesday, December 26, 2006 12:17 PM
Subject: Re: axis2-soapmonitor*.mar ?


Please file a jira. In the meantime, with a little help from google:

-inurl:htm -inurl:html -inurl:asp intitle:"index of" +(mar|zip) soapmonitor-1.1

That brings up:

http://www.ibiblio.org/maven/org.apache.axis2/mars/

HTH,
Robert

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
> 404 on each site listed at
> http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip
> (It appears that the distros never made it to the mirrors)
>
> Martin--
> ---
> This e-mail message (including attachments, if any) is intended for the use 
> of the individual or entity to which it is addressed and may contain 
> information that is privileged, proprietary , confidential and exempt from 
> disclosure. If you are not the intended recipient, you are notified that any 
> dissemination, distribution or copying of this communication is strictly 
> prohibited.
> ---
> Le présent message électronique (y compris les pièces qui y sont annexées, le 
> cas échéant) s'adresse au destinataire indiqué et peut contenir des 
> renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
> destinataire de ce document, nous vous signalons qu'il est strictement 
> interdit de le diffuser, de le distribuer ou de le reproduire.
> - Original Message -
> From: "robert lazarski" <[EMAIL PROTECTED]>
> To: ; "Martin Gainty" <[EMAIL PROTECTED]>
> Sent: Tuesday, December 26, 2006 11:46 AM
> Subject: Re: axis2-soapmonitor*.mar ?
>
>
> http://ws.apache.org/axis2/modules/index.html
>
> HTH,
> Robert
>
> On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
> >
> >
> > Morning All
> >
> > where is axis2-soapmonitor*.mar located?
> >
> > Thanks,
> > Martin--
> > ---
> > This e-mail message (including attachments, if any) is intended for the use
> > of the individual or entity to which it is addressed and may contain
> > information that is privileged, proprietary , confidential and exempt from
> > disclosure. If you are not the intended recipient, you are notified that any
> > dissemination, distribution or copying of this communication is strictly
> > prohibited.
> > ---
> > Le présent message électronique (y compris les pièces qui y sont annexées,
> > le cas échéant) s'adresse au destinataire indiqué et peut contenir des
> > renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
> > destinataire de ce document, nous vous signalons qu'il est strictement
> > interdit de le diffuser, de le distribuer ou de le reproduire.
>
> -
> 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]

Re: axis2-soapmonitor*.mar ?

2006-12-26 Thread robert lazarski


Please file a jira. In the meantime, with a little help from google:

-inurl:htm -inurl:html -inurl:asp intitle:"index of" +(mar|zip) soapmonitor-1.1

That brings up:

http://www.ibiblio.org/maven/org.apache.axis2/mars/

HTH,
Robert

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:

404 on each site listed at
http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip
(It appears that the distros never made it to the mirrors)

Martin--
---
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
---
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: "robert lazarski" <[EMAIL PROTECTED]>
To: ; "Martin Gainty" <[EMAIL PROTECTED]>
Sent: Tuesday, December 26, 2006 11:46 AM
Subject: Re: axis2-soapmonitor*.mar ?


http://ws.apache.org/axis2/modules/index.html

HTH,
Robert

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
>
>
> Morning All
>
> where is axis2-soapmonitor*.mar located?
>
> Thanks,
> Martin--
> ---
> This e-mail message (including attachments, if any) is intended for the use
> of the individual or entity to which it is addressed and may contain
> information that is privileged, proprietary , confidential and exempt from
> disclosure. If you are not the intended recipient, you are notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited.
> ---
> Le présent message électronique (y compris les pièces qui y sont annexées,
> le cas échéant) s'adresse au destinataire indiqué et peut contenir des
> renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
> destinataire de ce document, nous vous signalons qu'il est strictement
> interdit de le diffuser, de le distribuer ou de le reproduire.

-
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]

Re: axis2-soapmonitor*.mar ?

404 on each site listed at
http://www.apache.org/dyn/mirrors/mirrors.cgi/ws/axis2/modules/addressing/1_1/soapmonitor-1.1.zip
(It appears that the distros never made it to the mirrors)

Martin--
--- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message - 
From: "robert lazarski" <[EMAIL PROTECTED]>
To: ; "Martin Gainty" <[EMAIL PROTECTED]>
Sent: Tuesday, December 26, 2006 11:46 AM
Subject: Re: axis2-soapmonitor*.mar ?


http://ws.apache.org/axis2/modules/index.html

HTH,
Robert

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:
>
>
> Morning All
>
> where is axis2-soapmonitor*.mar located?
>
> Thanks,
> Martin--
> ---
> This e-mail message (including attachments, if any) is intended for the use
> of the individual or entity to which it is addressed and may contain
> information that is privileged, proprietary , confidential and exempt from
> disclosure. If you are not the intended recipient, you are notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited.
> ---
> Le présent message électronique (y compris les pièces qui y sont annexées,
> le cas échéant) s'adresse au destinataire indiqué et peut contenir des
> renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
> destinataire de ce document, nous vous signalons qu'il est strictement
> interdit de le diffuser, de le distribuer ou de le reproduire.

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

Re: axis2-soapmonitor*.mar ?

2006-12-26 Thread robert lazarski


http://ws.apache.org/axis2/modules/index.html

HTH,
Robert

On 12/26/06, Martin Gainty <[EMAIL PROTECTED]> wrote:



Morning All

where is axis2-soapmonitor*.mar located?

Thanks,
Martin--
---
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that any
dissemination, distribution or copying of this communication is strictly
prohibited.
---
Le présent message électronique (y compris les pièces qui y sont annexées,
le cas échéant) s'adresse au destinataire indiqué et peut contenir des
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
destinataire de ce document, nous vous signalons qu'il est strictement
interdit de le diffuser, de le distribuer ou de le reproduire.


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

axis2-soapmonitor*.mar ?