I got it to work by changing the getRealPath to specifically point to
the server-config.wsdd. But when I run 

java org.apache.axis.client.AdminClient deploy.wsdd
-lhttp://localhost:7001/axis/services/AdminService

it will deploy it but I still get a NullPointerException:
Servlet failed with Exception
java.lang.NullPointerException
        at
weblogic.servlet.internal.ChunkOutput.clearBuffer(ChunkOutput.java:231)
...
...
...
at
org.apache.axis.trasport.http.AxisServlet.doPort(AxisServlet.java:536)

I get the same thing on the server when I run the Client class, I get
the expected return 'but' it throws that exception.

any ideas?

Thanks

Gus

On Sun, 2002-03-03 at 20:32, herve attia wrote:

Adam is right.

Concerning the issue to write to the server-config.wsdd file.

I have found that the problem is the use of
ServletContext.getRealPath with weblogic .

If you have deployed Axis as a WAR file, Weblogic will return null when
ServletContext.getRealPath is called : 

If you take a look to the getEngine method of
org.apache.axis.transport.http.AdminServlet

the error will occur from 

FileProvider provider =

new FileProvider(getServletContext().getRealPath("/WEB-INF"),

Constants.SERVER_CONFIG_FILE);

.
This behavior persists even if the application is exploded onto disk -
WL6.1still treats it the same as a war file 


The conclusion is to do like Adam did....subclass AdminServlet and
override getEngine method

herve






********************************* 
Herve Attia 
Cell (650) 922-1973 
Home (650) 992-3997 
http://www.chez.com/attia/resume/ 
>From: "Adam.Leggett" 
>Reply-To: [EMAIL PROTECTED] 
>To: "'[EMAIL PROTECTED]'" 
>Subject: RE: Axis/BEA WL 6.1 still issue... 
>Date: Fri, 1 Mar 2002 09:45:24 -0000 
> 
>Using Weblogic 6.1 SP2 and Axis alpha 3 we have solved this in a
slightly 
>different way. 
> 
>We used our own custom ConfigurationProvider implementation which looks
for 
>a System property to specify a resource name, 
>so we can load our config from within the war in weblogic (Maybe the
latest 
>build gives you this). Then we extended AxisServlet and provided our
own 
>implementation of getEngine() to put this into the enviroment Map. 
> 
>We are taking the approach that we do not need to write out to our wsdd
>while the engine is up, ie dynamic deployment. 
> 
>As I said, the nightly build may already provide for all this, but we
are 
>sticking with alpha3 for now. 
> 
>Cheers 
> 
>Adam 
> 
>-----Original Message----- 
>From: Glyn Normington [mailto:[EMAIL PROTECTED]] 
>Sent: Friday, March 01, 2002 9:03 AM 
>To: [EMAIL PROTECTED] 
>Subject: Re: Axis/BEA WL 6.1 still issue... 
> 
> 
> 
> >I added "-Daxis.ServerConfigFile=E:\temp\server-config.wsdd" to the
BEA 
>startup command line. 
> 
>I wonder if file access is somehow restricted to the /WEB-INF
directory? I'd 
>guess others are not using -Daxis.ServerConfigFile as it's relatively
new 
>(and undocumented). 
> 
>Glyn 

________________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com.;

-- 
Gus Delgado
Consultant
NetQuotient Consulting Group
e-mail: [EMAIL PROTECTED]
cell:   512-587-6986

Reply via email to