Connection refused

2010-02-02 Thread Moritz Mädler
Hello List!

after setting up my axis2 1.5.1 and loading up my service,
i created a client stub using the eclipse WT built-in Web Service Client 
creator.
I passed the WSDL-Address and it successfully created the service stub.
When i make a testcall (login) to my service using the service-stub, I get the 
following
exception:
--
org.apache.axis2.AxisFault: Connection refused
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at 
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at 
de.tamundo.serviceclient.TamundoServiceStub.login(TamundoServiceStub.java:2063)
at 
de.tamundo.serviceclient.TamundoServiceClient.login(TamundoServiceClient.java:101)
at 
de.tamundo.serviceclient.TamundoServiceClient.main(TamundoServiceClient.java:25)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
at java.net.Socket.connect(Socket.java:525)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.commons.httpclient.protocol.ReflectionSocketFactory.createSocket(ReflectionSocketFactory.java:140)
at 
org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:125)
at 
org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at 
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at 
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:542)
at 
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:189)
... 10 more
--

After that call Catalina seems to shut down:
(taken from catalina.log)
--
Feb 2, 2010 2:34:35 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Feb 2, 2010 2:34:36 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Feb 2, 2010 2:34:36 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
Feb 2, 2010 2:34:37 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
Feb 2, 2010 2:34:39 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
Feb 2, 2010 2:34:39 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
--

As I did it the same way on to other systems without problems, I think it could 
not be the Stub or sth. alike.

Do you have an idea, why catalina shuts down upon request?

Thanks alot!




Use autocreated WSDL as original WSDL

2009-12-21 Thread Moritz Mädler
Hello!

to use my service with the correct endpoint-address, i need to change the 
Endpoint-Addresses manually.
Up to now I used the autocreation feature of Axis2 to generate my WSDL from 
AAR. As I just need to
change the Endpointaddress I downloaded the auto WSDL and changed. Then I added 
the WSDL to
my AAR, set the parameters useOriginalwsdl and modifyUserWSDLPortAddress and 
deployed the 
service again.
After deployment no parameters are accepted from my freshly generated client 
stub. Do I have to
change sth. else in the WSDL before deployment? 

Thanks alot and a peaceful x-mas! 

Re: Configuring Axis2 using SSL

2009-11-24 Thread Moritz Mädler
Hi Andreas!

Thanks for your quick reply. 

Is it fixed in the 1.5.1 release, too? 

If we discard the unsecured address and only provide the https-address is there 
a way to set it "by hand"?

Thanks alot!




> This is probably yet another instance of the issue described in
> AXIS2-4465 (which is fixed in trunk).
> 
> Andreas
> 
> On Tue, Nov 24, 2009 at 10:12, Moritz Mädler  wrote:
>> Hi,
>> 
>> we want to provide our service also via SSL.
>> Our Axis 1.5 runs as an application in Tomcat 6 which we already configured 
>> for listening for SSL-Connections.
>> When I call the WSDL using SSL Axis2 sets the wsdl-port-address as 
>> https://serviceurl:80/SERVICE. This is not
>> working as the Port 80 is added misleadingly.
>> I don't know how to fix that and especially keep both transports http and 
>> https as we want to use the old clients
>> were we could not change the address to the new https one.
>> 
>> I hope you can help!?
>> 
>> 
>> Thanks alot!
>> 
>> Moritz



Configuring Axis2 using SSL

2009-11-24 Thread Moritz Mädler
Hi,

we want to provide our service also via SSL. 
Our Axis 1.5 runs as an application in Tomcat 6 which we already configured for 
listening for SSL-Connections.
When I call the WSDL using SSL Axis2 sets the wsdl-port-address as 
https://serviceurl:80/SERVICE. This is not 
working as the Port 80 is added misleadingly. 
I don't know how to fix that and especially keep both transports http and https 
as we want to use the old clients 
were we could not change the address to the new https one.

I hope you can help!?


Thanks alot!

Moritz

Re: Axis2 1.5 returns wrong DateTime

2009-09-02 Thread Moritz Mädler
I managed to fix the dates. Now Axis converts the Calendar-Objects to  
GMT which is rather inconvenient

in my case. Is there a possibility to change that?

Thanks alot!


Am 02.09.2009 um 11:00 schrieb Moritz Mädler:


Hello,

after changing the Datefields in my WSDL to datetime (using POJO- 
Class with java.util.Calendar)

Axis2 somehow returns the wrong date/time.
For example the Date/Time the POJO-Class logs is
-
java.util.GregorianCalendar[time=1251829037000,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="GMT",offset=0,dstSavings=0,useDaylight=false,transitions=0,lastRule=null],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2009,MONTH=8,WEEK_OF_YEAR=36,WEEK_OF_MONTH=1,DAY_OF_MONTH=1,DAY_OF_YEAR=244,DAY_OF_WEEK=3,DAY_OF_WEEK_IN_MONTH=1,AM_PM=1,HOUR=6,HOUR_OF_DAY=18,MINUTE=17,SECOND=17,MILLISECOND=0,ZONE_OFFSET=0,DST_OFFSET=0]

The logged date was 2009-09-01 20:17:17.0
When I call the Webservice it returns:
2009-09-07T22:00:00.000Z
what is completely illogical.

The Code that sets this date_posted is
-
Calendar cPosted = Calendar.getInstance();
cPosted.setTimeZone(TimeZone.getTimeZone("CEST"));
Date dPosted = rs.getTimestamp("date_posted");
cPosted.setTime(dPosted);
ac.setDate_posted(cPosted);// Container that carries the  
Calendar-Object

-

I already searched the web for solutions, but did not find anything.





Axis2 1.5 returns wrong DateTime

2009-09-02 Thread Moritz Mädler

Hello,

after changing the Datefields in my WSDL to datetime (using POJO-Class  
with java.util.Calendar)

Axis2 somehow returns the wrong date/time.
For example the Date/Time the POJO-Class logs is
-
java.util.GregorianCalendar[time=1251829037000,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="GMT",offset=0,dstSavings=0,useDaylight=false,transitions=0,lastRule=null],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2009,MONTH=8,WEEK_OF_YEAR=36,WEEK_OF_MONTH=1,DAY_OF_MONTH=1,DAY_OF_YEAR=244,DAY_OF_WEEK=3,DAY_OF_WEEK_IN_MONTH=1,AM_PM=1,HOUR=6,HOUR_OF_DAY=18,MINUTE=17,SECOND=17,MILLISECOND=0,ZONE_OFFSET=0,DST_OFFSET=0]

The logged date was 2009-09-01 20:17:17.0
When I call the Webservice it returns:
2009-09-07T22:00:00.000Z
what is completely illogical.

The Code that sets this date_posted is
-
Calendar cPosted = Calendar.getInstance();
cPosted.setTimeZone(TimeZone.getTimeZone("CEST"));
Date dPosted = rs.getTimestamp("date_posted");
cPosted.setTime(dPosted);
ac.setDate_posted(cPosted);// Container that carries the Calendar- 
Object

-

I already searched the web for solutions, but did not find anything.




Re: Securing Axis2-Admin

2009-08-24 Thread Moritz Mädler
Thanks! I added the following lines to the /axis2/WEB-INF/classes/ 
log4j.properties:


de.tamundo.security=WARN, CONSOLE
de 
.tamundo.security.appender.CONSOLE.layout=org.apache.log4j.PatternLayout

de.tamundo.security.appender.CONSOLE.layout.ConversionPattern=[%p] %m%n


I still get the same error.


Am 24.08.2009 um 14:30 schrieb Martin Gainty:

#log4j.properties should contain a statement which associates your  
package to Level e.g.

#package=LEVEL, NameOfAppender

#BEGIN CONSOLE APPENDER (stdout)
#first:type of appender (fully qualified class name) note all stdout  
goes to ConsoleAppender

log4j.appender.stdout=org.apache.log4j.ConsoleAppender
#Many appenders require a layout.
log4j.appender.stdout.layout=org.apache.log4j.SimpleLayout

#  additionally, some layouts can take additional information --
#like the ConversionPattern for the PatternLayout.
# log4j.appender.stdout.layout.ConversionPattern=%d %-5p %-17c{2}  
(%30F:%L) %3x

- %m%n

# BEGIN Rolling APPENDER: (rolling)
#  first:type of appender (fully qualified class name)
log4j.appender.rolling=org.apache.log4j.RollingFileAppender
#  second: Any configuration information needed for that appender.
#Many appenders require a layout.
log4j.appender.rolling.File=example.log

# max file size of rolling appender will be 100kb
log4j.appender.rolling.MaxFileSize=100KB
#  Keep one backup file
log4j.appender.rolling.MaxBackupIndex=1

#pattern of the logfile
log4j.appender.rolling.layout=org.apache.log4j.PatternLayout
log4j.appender.rolling.layout.ConversionPattern=%p %t %c - %m%n

//default rootCategory for level is debug with output directed to  
stdout or //RollingFileAppender as in

log4j.rootCategory=debug,stdout,rolling

//you want to assign your package=LEVEL,Appender1,Appender2 as  
defined here

de.tamundo.security=warn,stdout,rolling

valid levels are
debug, info, warn, error, fatal and log.

appenders are
console, files, GUI components, remote socket servers, JMS, NT Event  
Loggers, and remote UNIX Syslog daemons


http://logging.apache.org/log4j/1.2/manual.html

HTH
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de  
confidentialité


Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene  
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede  
unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig.  
Diese Nachricht dient lediglich dem Austausch von Informationen und  
entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten  
Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den  
Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes  
pas le destinataire prévu, nous te demandons avec bonté que pour  
satisfaire informez l'expéditeur. N'importe quelle diffusion non  
autorisée ou la copie de ceci est interdite. Ce message sert à  
l'information seulement et n'aura pas n'importe quel effet  
légalement obligatoire. Étant donné que les email peuvent facilement  
être sujets à la manipulation, nous ne pouvons accepter aucune  
responsabilité pour le contenu fourni.






From: m...@moritz-maedler.de
To: axis-user@ws.apache.org
Subject: Securing Axis2-Admin
Date: Mon, 24 Aug 2009 14:11:58 +0200

Hello,

I'm using axis2 1.5 as a tomcat6 servlet. As it runs in production,  
I want to secure the axis2 admin frontend

by restricting the access to a specifig (e.g. local) IP-range.
How can this be implemented? I tried to integrate a filter which  
sends a 403-error upon access with wrong

IP-address. This leaded to following exception when restarting tomcat:
-
Aug 24, 2009 12:47:30 PM org.apache.catalina.core.StandardContext  
processTlds

SEVERE: Error reading tld listeners java.lang.NullPointerException
java.lang.NullPointerException
at org.apache.log4j.Category.isEnabledFor(Category.java:749)
	at  
org 
.apache 
.commons.logging.impl.Log4JLogger.isTraceEnabled(Log4JLogger.java:333)
	at  
org 
.apache 
.catalina.startup.TldConfig.tldScanResourcePaths(TldConfig.java:581)

at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:282)
	at  
org 
.apache 
.catalina.core.StandardContext.processTlds(StandardContext.java:4307)
	at  
org.apache.catalina.core.StandardContext.start(StandardContext.java: 
4144)
	at  
org 
.apache 
.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
	at  
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java: 
740)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java: 
544)
	at  
org 
.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java: 
626)
	at  
org 
.apache 
.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
	at  
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)

at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
	at  
org 
.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java: 
31

Securing Axis2-Admin

2009-08-24 Thread Moritz Mädler

Hello,

I'm using axis2 1.5 as a tomcat6 servlet. As it runs in production, I  
want to secure the axis2 admin frontend

by restricting the access to a specifig (e.g. local) IP-range.
How can this be implemented? I tried to integrate a filter which sends  
a 403-error upon access with wrong

IP-address. This leaded to following exception when restarting tomcat:
-
Aug 24, 2009 12:47:30 PM org.apache.catalina.core.StandardContext  
processTlds

SEVERE: Error reading tld listeners java.lang.NullPointerException
java.lang.NullPointerException
at org.apache.log4j.Category.isEnabledFor(Category.java:749)
	at  
org 
.apache 
.commons.logging.impl.Log4JLogger.isTraceEnabled(Log4JLogger.java:333)
	at  
org 
.apache.catalina.startup.TldConfig.tldScanResourcePaths(TldConfig.java: 
581)

at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:282)
	at  
org 
.apache.catalina.core.StandardContext.processTlds(StandardContext.java: 
4307)
	at  
org.apache.catalina.core.StandardContext.start(StandardContext.java: 
4144)
	at  
org 
.apache 
.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java: 
740)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java: 
544)
	at  
org 
.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java: 
626)
	at  
org 
.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java: 
553)
	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java: 
488)

at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
	at  
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java: 
311)
	at  
org 
.apache 
.catalina 
.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java: 
1022)

at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java: 
1014)
	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java: 
443)
	at  
org.apache.catalina.core.StandardService.start(StandardService.java:448)
	at org.apache.catalina.core.StandardServer.start(StandardServer.java: 
700)

at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at  
sun 
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 
39)
	at  
sun 
.reflect 
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 
25)

at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at  
sun 
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 
39)
	at  
sun 
.reflect 
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 
25)

at java.lang.reflect.Method.invoke(Method.java:597)
	at  
org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java: 
177)
Aug 24, 2009 12:47:31 PM org.apache.catalina.core.StandardContext  
processTlds



The filter-config looks like web.xml looks like

[AXIS-CONF]




IPFilter
IPFilter
de.tamundo.security.IPFilter


IPFilter
/IPFilter



I copied the filterclass under /axis2/WEB-INF/de/tamundo/security.

Is there another possibility to secure the Axis2-Admin?

Thanks alot!

Moritz




Re: Making service directly accessible

2009-08-17 Thread Moritz Mädler

I configured my stuff as follows:

In the http-Host on port 80 I added the following RewriteRules:
RewriteRule services/(.*)$ http://HOST:8080/axis2/services/$1 [L]
RewriteRule (.*)$ http://HOST:8080/axis2/$1

In the WEB-INF/axis2.xml I changed
http:/HOST

In the WSDL I changed the Endpoint-URLs to HOST and in the WEB-INF/ 
service.xml in the

service-aar I added the following params:
true
false

When I generate my ServiceClient and make a servicecall afterwards I  
get the following exception:


[INFO] Unable to sendViaPost to url[http://HOST/services/Service.ServiceHttpSoap12Endpoint/ 
]

org.apache.axis2.AxisFault: Transport error: 302 Error: Found
	at  
org 
.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java: 
296)
	at  
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java: 
190)

at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
	at  
org 
.apache 
.axis2 
.transport 
.http 
.CommonsHTTPTransportSender 
.writeMessageWithCommons(CommonsHTTPTransportSender.java:371)
	at  
org 
.apache 
.axis2 
.transport 
.http 
.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)

at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
	at  
org 
.apache 
.axis2 
.description.OutInAxisOperationClient.send(OutInAxisOperation.java:401)
	at  
org 
.apache 
.axis2 
.description 
.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
	at  
org.apache.axis2.client.OperationClient.execute(OperationClient.java: 
163)

at de.tamundo.serviceclient.ServiceStub.login(ServiceStub.java:2244)
at de.tamundo.serviceclient.ServiceClient.login(ServiceClient.java:102)
at de.tamundo.serviceclient.ServiceClient.main(ServiceClient.java:34)

Is there anything else I need to change?

Thanks alot!


Am 12.08.2009 um 14:13 schrieb Moritz Mädler:

We are currently using Apache httpd and Tomcat without mod_jk. Is it  
possible to use the mod_rewrite although?

Thanks alot!



Am 05.08.2009 um 12:00 schrieb Yves Glodt:


On Wednesday 05 August 2009 11:34:20 Moritz Mädler wrote:

Hello!

thanks alot for your answer. Do you mean I should use the  
mod_rewrite

of the apache httpd and rewrite any requests to the tomcat servlet
which is running on another port?


This is a possibility...

But you can also avoid using a separate Apache httpd.

Use UrlRewrite:
http://tuckey.org/urlrewrite/

Is it basically mod_rewrite for tomcat. I used it in 2 projects so  
far, with

great success.

HTH,
Yves



Am 05.08.2009 um 11:15 schrieb Giuseppe Gortan:

Try using Apache and mod rewrite to rewrite your url,
Than change wsdl:port address in your wsdl and set in services.xml
true




On Wed, Aug 5, 2009 at 11:04 AM, Moritz Mädler wrote:

Hi,

I'm still looking for a solution. Could anybody help me please?

Thanks alot!

Am 31.07.2009 um 20:12 schrieb Moritz Mädler:

Hello!

I have a service running in my Axis 1.4.1 which itself runs as a
servlet
in a tomcat 5.5.

Is it possible to configure Tomcat that I can access the Service
directly
by entering only the Domain (like
http://domainofservice.com/ServiceName instead of
http://domainofservice.com/axis2/services/ServiceName)?

BTW have you already made some experiences with upgrading from
Axis2 1.4.1
to 1.5? Is there anything I must pay attention to?

Thanks a lot and have a nice weekend!

Moritz




Re: Making service directly accessible

2009-08-12 Thread Moritz Mädler
We are currently using Apache httpd and Tomcat without mod_jk. Is it  
possible to use the mod_rewrite although?

Thanks alot!



Am 05.08.2009 um 12:00 schrieb Yves Glodt:


On Wednesday 05 August 2009 11:34:20 Moritz Mädler wrote:

Hello!

thanks alot for your answer. Do you mean I should use the mod_rewrite
of the apache httpd and rewrite any requests to the tomcat servlet
which is running on another port?


This is a possibility...

But you can also avoid using a separate Apache httpd.

Use UrlRewrite:
http://tuckey.org/urlrewrite/

Is it basically mod_rewrite for tomcat. I used it in 2 projects so  
far, with

great success.

HTH,
Yves



Am 05.08.2009 um 11:15 schrieb Giuseppe Gortan:

Try using Apache and mod rewrite to rewrite your url,
Than change wsdl:port address in your wsdl and set in services.xml
true




On Wed, Aug 5, 2009 at 11:04 AM, Moritz Mädler wrote:

Hi,

I'm still looking for a solution. Could anybody help me please?

Thanks alot!

Am 31.07.2009 um 20:12 schrieb Moritz Mädler:

Hello!

I have a service running in my Axis 1.4.1 which itself runs as a
servlet
in a tomcat 5.5.

Is it possible to configure Tomcat that I can access the Service
directly
by entering only the Domain (like
http://domainofservice.com/ServiceName instead of
http://domainofservice.com/axis2/services/ServiceName)?

BTW have you already made some experiences with upgrading from
Axis2 1.4.1
to 1.5? Is there anything I must pay attention to?

Thanks a lot and have a nice weekend!

Moritz




Re: Making service directly accessible

2009-08-05 Thread Moritz Mädler

OK. Thanks alot. I will try that.



Am 05.08.2009 um 11:47 schrieb Giuseppe Gortan:


Yes.  For example if your webservice points, for example, to
http://domainofservice.com:8080/axis2/services/ServiceName, write a
rule to rewrite url in something like
http://domainofservice.com/ServiceName

The wsdl:port address will be http://domainofservice.com/ServiceName
instead of http://domainofservice.com:8080/axis2/services/ServiceName




On Wed, Aug 5, 2009 at 11:34 AM, Moritz Mädlermaedler.de> wrote:

Hello!

thanks alot for your answer. Do you mean I should use the  
mod_rewrite of the

apache httpd and rewrite any requests to the tomcat servlet which is
running on another port?




Am 05.08.2009 um 11:15 schrieb Giuseppe Gortan:


Try using Apache and mod rewrite to rewrite your url,
Than change wsdl:port address in your wsdl and set in services.xml
true




On Wed, Aug 5, 2009 at 11:04 AM, Moritz Mädler>

wrote:


Hi,

I'm still looking for a solution. Could anybody help me please?

Thanks alot!



Am 31.07.2009 um 20:12 schrieb Moritz Mädler:


Hello!

I have a service running in my Axis 1.4.1 which itself runs as a  
servlet

in a tomcat 5.5.

Is it possible to configure Tomcat that I can access the Service
directly
by entering only the Domain (like
http://domainofservice.com/ServiceName instead of
http://domainofservice.com/axis2/services/ServiceName)?

BTW have you already made some experiences with upgrading from  
Axis2

1.4.1
to 1.5? Is there anything I must pay attention to?

Thanks a lot and have a nice weekend!

Moritz







--
«The phonograph has no commercial value at all.»
Thomas Edison, American inventor, 1880s.







--
«The phonograph has no commercial value at all.»
Thomas Edison, American inventor, 1880s.




Re: Making service directly accessible

2009-08-05 Thread Moritz Mädler

Hello!

thanks alot for your answer. Do you mean I should use the mod_rewrite  
of the apache httpd and rewrite any requests to the tomcat servlet  
which is

running on another port?




Am 05.08.2009 um 11:15 schrieb Giuseppe Gortan:


Try using Apache and mod rewrite to rewrite your url,
Than change wsdl:port address in your wsdl and set in services.xml
true




On Wed, Aug 5, 2009 at 11:04 AM, Moritz Mädlermaedler.de> wrote:

Hi,

I'm still looking for a solution. Could anybody help me please?

Thanks alot!



Am 31.07.2009 um 20:12 schrieb Moritz Mädler:


Hello!

I have a service running in my Axis 1.4.1 which itself runs as a  
servlet

in a tomcat 5.5.

Is it possible to configure Tomcat that I can access the Service  
directly

by entering only the Domain (like
http://domainofservice.com/ServiceName instead of
http://domainofservice.com/axis2/services/ServiceName)?

BTW have you already made some experiences with upgrading from  
Axis2 1.4.1

to 1.5? Is there anything I must pay attention to?

Thanks a lot and have a nice weekend!

Moritz







--
«The phonograph has no commercial value at all.»
Thomas Edison, American inventor, 1880s.




Re: Making service directly accessible

2009-08-05 Thread Moritz Mädler

Hi,

I'm still looking for a solution. Could anybody help me please?

Thanks alot!



Am 31.07.2009 um 20:12 schrieb Moritz Mädler:


Hello!

I have a service running in my Axis 1.4.1 which itself runs as a  
servlet in a tomcat 5.5.


Is it possible to configure Tomcat that I can access the Service  
directly by entering only the Domain (like http://domainofservice.com/ServiceName 
 instead of http://domainofservice.com/axis2/services/ServiceName)?


BTW have you already made some experiences with upgrading from Axis2  
1.4.1 to 1.5? Is there anything I must pay attention to?


Thanks a lot and have a nice weekend!

Moritz




Making service directly accessible

2009-07-31 Thread Moritz Mädler

Hello!

I have a service running in my Axis 1.4.1 which itself runs as a  
servlet in a tomcat 5.5.


Is it possible to configure Tomcat that I can access the Service  
directly by entering only the Domain (like http://domainofservice.com/ServiceName 
 instead of http://domainofservice.com/axis2/services/ServiceName)?


BTW have you already made some experiences with upgrading from Axis2  
1.4.1 to 1.5? Is there anything I must pay attention to?


Thanks a lot and have a nice weekend!

Moritz


Re: [axis-2:file upload]

2009-07-08 Thread Moritz Mädler
We implemented that with a method returning/reveiving  
javax.activation.DataHandler on the java-service-side.
Axis converts that to a base64binary-field what you can use with every  
Client. The important thing is, that you deactivate

SwA and enable MTOM in the axis2.xml.

Regards,

moritz



Am 08.07.2009 um 06:30 schrieb Rajneesh Kumar:


Hi All,

Can any one please tell me how to send file as attachment  
(description is given below) in SOAP request using C# (.Net) client  
to apache axis2 java web service?


Thanks & Regards,
Rajneesh Kumar

From: Rajneesh Kumar [mailto:rajneesh.ku...@otssolutions.com]
Sent: Thursday, July 02, 2009 12:33 PM
To: axis-user@ws.apache.org
Subject: [axis-2:file upload]

HI All,

My client application (developed in c# .Net) will have to read file  
(doc/pdf/tiff) from local drive and send the file data to axis-2  
(running on a java based server somewhere else) as SOAP attachment,  
then the web method will create file with that data and store it on  
the server.


Now I want to know how to accomplish this. I mean how my .Net client  
app will send that attachment and axis-2 web service will be able to  
process the file.


Please provide some help.

Thanx in Advance…
-Rajneesh




= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
==
Private, Confidential and Privileged. This e-mail and any files and  
attachments transmitted with it are confidential and/or privileged.  
They are intended solely for the use of the intended recipient. The  
content of this e-mail and any file or attachment transmitted with  
it may have been changed or altered without the consent of the  
author. If you are not the intended recipient, please note that any  
review, dissemination, disclosure, alteration, printing, circulation  
or Transmission of this e-mail and/or any file or attachment  
transmitted with it, is prohibited and may be unlawful. If you have  
received this e-mail or any file or attachment transmitted with it  
in error please notify OTS Solutions at i...@otssolutions.com
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
==


= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
==
Private, Confidential and Privileged. This e-mail and any files and  
attachments transmitted with it are confidential and/or privileged.  
They are intended solely for the use of the intended recipient. The  
content of this e-mail and any file or attachment transmitted with  
it may have been changed or altered without the consent of the  
author. If you are not the intended recipient, please note that any  
review, dissemination, disclosure, alteration, printing, circulation  
or Transmission of this e-mail and/or any file or attachment  
transmitted with it, is prohibited and may be unlawful. If you have  
received this e-mail or any file or attachment transmitted with it  
in error please notify OTS Solutions at i...@otssolutions.com
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
==


= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
==
Private, Confidential and Privileged. This e-mail and any files and  
attachments transmitted with it are confidential and/or privileged.  
They are intended solely for the use of the intended recipient. The  
content of this e-mail and any file or attachment transmitted with  
it may have been changed or altered without the consent of the  
author. If you are not the intended recipient, please note that any  
review, dissemination, disclosure, alteration, printing, circulation  
or Transmission of this e-mail and/or any file or attachment  
transmitted with it, is prohibited and may be unlawful. If you have  
received this e-mail or any file or attachment transmitted with it  
in error please notify OTS Solutions at i...@otssolutions.com
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
= 
==




Could not throw SOAPFault

2009-07-06 Thread Moritz Mädler

Hello,

i want to return SOAPFaults to inform the client in the case sth. went  
wrong on the service side.

To return a SOAPFault I created the following method in my serviceclass:
--
protected void throwSOAPFault(String text) throws AxisFault{
		MessageContext messageContext =  
MessageContext.getCurrentMessageContext();

Exception t = new Exception(text);

SOAPFactory soapFactory = OMAbstractFactory.getSOAP11Factory();

SOAPFaultCode soapFaultCode = soapFactory.createSOAPFaultCode();
soapFaultCode.declareNamespace("http://someurl";, "m");

SOAPFaultValue soapFaultValue = 
soapFactory.createSOAPFaultValue();
soapFaultValue.setText("m:FaulException");
		 
messageContext.setProperty(SOAP12Constants.SOAP_FAULT_CODE_LOCAL_NAME,  
soapFaultCode);


SOAPFaultReason soapFaultReason = 
soapFactory.createSOAPFaultReason();
		SOAPFaultText soapFaultText =  
soapFactory.createSOAPFaultText(soapFaultReason);

soapFaultText.setText(text);
		 
messageContext 
.setProperty(SOAP12Constants.SOAP_FAULT_REASON_LOCAL_NAME,  
soapFaultReason);


SOAPFaultDetail soapFaultDetail = 
soapFactory.createSOAPFaultDetail();
QName qName = new QName("http://someurl";, "FaultException");
OMElement detail = soapFactory.createOMElement(qName, null);
Throwable e = t;
while (e != null){
OMElement exception = 
soapFactory.createOMElement(qName, null);
exception.setText(t.getMessage());
detail.addChild(exception);
e = e.getCause();
}
		 
messageContext 
.setProperty(SOAP12Constants.SOAP_FAULT_DETAIL_LOCAL_NAME,  
soapFaultDetail);

throw new AxisFault(text);
}
-
But if i trigger an error through an obviously wrong request, I only  
see the AxisFault in service logfile.


What do I have to do for sending SOAPFaults to the client?

Thanks a lot in advance!

Moritz




Re: [axis2:uploading file]

2009-07-02 Thread Moritz Mädler

Hello,

you can find information here:
- http://wso2.org/library/3860

and within the axis2 binary dist. you can find a sample-service for SwA.

Greetings!

Moritz



AW: R: php5 client and axis message-style services

2009-06-30 Thread Moritz Mädler
Sorry. Of course I meant NOT.



- Ursprüngliche Nachricht -
Von: Marcello Marangio 
Gesendet: Dienstag, 30. Juni 2009 17:34
An: axis-user@ws.apache.org
Betreff: R: php5 client and axis message-style services

Hi
You mean "...could NOT get functions that expected Parameters to work..."

> -Messaggio originale-
> Da: Moritz Mädler [mailto:m...@moritz-maedler.de]
> Inviato: martedì 30 giugno 2009 17.10
> A: axis-user@ws.apache.org
> Oggetto: Re: php5 client and axis message-style services
> 
> Hello!
> 
> i tried w/ the PHP-onboard-Extension to access my Axis2-Service. I
> don't know if i made something wrong, but I could get
> Functions that expected Parameters to work.
> 
> Thus, i switched to nuSOAP. There is also another C-Libary for PHP
> from wso2 which can be found here: http://wso2.com/products/create/wso2-
> web-services-framework/
> 
> 
> 
> Checked by AVG - www.avg.com
> Version: 8.5.375 / Virus Database: 270.13.0/2210 - Release Date: 06/30/09
> 06:10:00



Re: php5 client and axis message-style services

2009-06-30 Thread Moritz Mädler

Hello!

i tried w/ the PHP-onboard-Extension to access my Axis2-Service. I  
don't know if i made something wrong, but I could get

Functions that expected Parameters to work.

Thus, i switched to nuSOAP. There is also another C-Libary for PHP  
from wso2 which can be found here: http://wso2.com/products/create/wso2-web-services-framework/





Re: Error while uploading File using DataHandler

2009-06-25 Thread Moritz Mädler

Hello!

i posted the code snippet in my first post. If this isn't enough, pls  
tell me which part you need.


Greetings!


Re: Error while uploading File using DataHandler

2009-06-24 Thread Moritz Mädler

Ok, i found the bug: just forgot to set one argument - damn me.

I've got another question: As you can see, i request the filetye from  
the DataHandler.getName() using  
String.substring(String.lastindexof(".")).
When i test the POJO-Class locally, i get the correct extension. When  
i use it as the mentioned serviceclass i get a "ByteArrayDataSource"

as file-extension, which is completely useless.

How do i extract the correct file-extension out of my DataHandler?

Thanks alot!



Error while uploading File using DataHandler

2009-06-24 Thread Moritz Mädler

Hello!

I work with Axis 1.4.1 and Tomcat 5.5.
In the service there is a method which is used to upload image-data to  
the server using javax.activation.DataHandler.
I generated a ClientStub using the eclipse-built-in "Create new  
Webservice-Client" and communicate successfully with

other methods from the service.
When I want to upload an image i get the following Exception on the  
serverside:


ERROR 2009-06-24 17:37:34,491 [http-8180-Processor25]  
(RPCMessageReceiver.java:160) -

java.lang.IllegalArgumentException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at  
sun 
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 
39)
	at  
sun 
.reflect 
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 
25)

at java.lang.reflect.Method.invoke(Method.java:597)
	at  
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java: 
194)
	at  
org 
.apache 
.axis2 
.rpc 
.receivers 
.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:102)
	at  
org 
.apache 
.axis2 
.receivers 
.AbstractInOutMessageReceiver 
.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
	at  
org 
.apache 
.axis2 
.receivers 
.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
	at  
org 
.apache 
.axis2 
.transport 
.http 
.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
	at  
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	at  
org 
.apache 
.catalina 
.core 
.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java: 
269)
	at  
org 
.apache 
.catalina 
.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
	at  
org 
.apache 
.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java: 
213)
	at  
org 
.apache 
.catalina.core.StandardContextValve.invoke(StandardContextValve.java: 
172)
	at  
org 
.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java: 
127)
	at  
org 
.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java: 
117)
	at  
org 
.apache 
.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
	at  
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java: 
151)
	at  
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java: 
874)
	at org.apache.coyote.http11.Http11BaseProtocol 
$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
	at  
org 
.apache 
.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
	at  
org 
.apache 
.tomcat 
.util 
.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java: 
81)
	at org.apache.tomcat.util.threads.ThreadPool 
$ControlRunnable.run(ThreadPool.java:689)

at java.lang.Thread.run(Thread.java:619)
ERROR 2009-06-24 17:37:34,496 [http-8180-Processor25] (AxisEngine.java: 
212) -

org.apache.axis2.AxisFault
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
	at  
org 
.apache 
.axis2 
.rpc 
.receivers 
.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:161)
	at  
org 
.apache 
.axis2 
.receivers 
.AbstractInOutMessageReceiver 
.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
	at  
org 
.apache 
.axis2 
.receivers 
.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
	at  
org 
.apache 
.axis2 
.transport 
.http 
.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
	at  
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	at  
org 
.apache 
.catalina 
.core 
.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java: 
269)
	at  
org 
.apache 
.catalina 
.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
	at  
org 
.apache 
.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java: 
213)
	at  
org 
.apache 
.catalina.core.StandardContextValve.invoke(StandardContextValve.java: 
172)
	at  
org 
.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java: 
127)
	at  
org 
.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java: 
117)
	at  
org 
.apache 
.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
	at  
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java: 
151)
	at  
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java: 
874)
	at org.apache.coyote.http11.Http11BaseProtocol 
$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
	at  
org 
.apache 
.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpE