Deepal,

This is *the* solution for the 1.1.1 release :) Yes, we need to do
something else about this problem for 1.2

-- dims

On 2/22/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi Dims;

That is not the solution , when I run the build it creates thousands of
such files in user/temp directory. So here we have the same problem.
Once we create temp file it seems to me that we are not cleaning them. I
hope we need to clean up the temp directory when we start Axis2.

Thanks
Deepal

Davanum Srinivas wrote:

> those are from the rampart mar. Please remove those jars from the mar
> and drop them into WEB-INF/lib
>
> thanks,
> dims
>
> On 2/21/07, Michael Nishizawa <[EMAIL PROTECTED]> wrote:
>
>> Here's the files that are generated when one call is made to the axis
>> service:
>> axis232881bcprov-jdk13-132.jar
>> axis232882commons-codec-1.3.jar
>> axis232883jaxen-1.1-beta-9.jar
>> axis232884opensaml-1.1.jar
>> axis232885wss4j-SNAPSHOT.jar
>> axis232886xercesImpl-2.7.1.jar
>> axis232887xml-apis-1.3.03.jar
>> axis232888xmlsec-1.3.0.jar
>> axis232889bcprov-jdk13-132.jar
>> axis232890commons-codec-1.3.jar
>> axis232891jaxen-1.1-beta-9.jar
>> axis232892opensaml-1.1.jar
>> axis232893wss4j-SNAPSHOT.jar
>> axis232894xercesImpl-2.7.1.jar
>> axis232895xml-apis-1.3.03.jar
>> axis232896xmlsec-1.3.0.jar
>> axis232897bcprov-jdk13-132.jar
>> axis232898commons-codec-1.3.jar
>> axis232899jaxen-1.1-beta-9.jar
>> axis232900opensaml-1.1.jar
>> axis232901wss4j-SNAPSHOT.jar
>> axis232902xercesImpl-2.7.1.jar
>> axis232903xml-apis-1.3.03.jar
>> axis232904xmlsec-1.3.0.jar
>>
>> These get generated again when I make another call.
>>
>>
>> On 2/21/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
>> >
>> > What are the names of the jars?
>> >
>> > -- dims
>> >
>> > On 2/21/07, Michael Nishizawa <[EMAIL PROTECTED]> wrote:
>> > > Environment:
>> > > Tomcat 5.5
>> > > JDK 1.5.0_06
>> > > Latest version of Axis2
>> > >
>> > > I have a bit of a problem.  It seems that the Tomcat temp
>> directory is
>> > > getting filled with the same jar files.  In the archives someone
>> had a
>> > > similar problem and turning off the hot-update/hot-deploy or
>> removing
>> jars
>> > > from the aar or mar files worked.  That had no affect on my
>> problem, the
>> > > jars that are being copied are in the classpath, not in any type of
>> > > deployable and the hot-update/deploy has been set to false.
>> > >
>> > > Any other ideas on why this may be happening?
>> > >
>> >
>> >
>> > --
>> > Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services
>> Developers
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
>>
>
>

--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"



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




--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

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

Reply via email to