please post the patch in JIRA as well.

-- dims

On 9/13/06, Punnoose, Roshan <[EMAIL PROTECTED]> wrote:
Well, I didn't get a reply back, so I posted a JIRA for it. Hope that's ok. I 
have a patch for it, if you want me to post that also. It sort of cleans up the 
code there and fixes another bug too with the file caching.

Roshan


-----Original Message-----
From: Punnoose, Roshan [mailto:[EMAIL PROTECTED]
Sent: Tue 9/12/2006 2:28 PM
To: [email protected]
Subject: RE: Axis2 OMText to File

Ok, maybe I'm not looking at this right, but I think I see a bug in
TransportUtils.selectBuilderForMIME(...):

                Object cacheAttachmentProperty = msgContext
.getProperty(Constants.Configuration.CACHE_ATTACHMENTS);
                String cacheAttachmentString = null;
                boolean fileCacheForAttachments;

                if (cacheAttachmentProperty != null) {
                        cacheAttachmentProperty =
cacheAttachmentProperty;
                        fileCacheForAttachments = (Constants.VALUE_TRUE
                                        .equals(cacheAttachmentString));

The cacheAttachmentString is always going to be null right? Then, the
client will never actually cache the attachment in the temp directory if
the properties have been set. Right? Am I going crazy?

Roshan Punnoose
Phone: 301-497-6039

-----Original Message-----
From: Punnoose, Roshan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2006 12:17 PM
To: [email protected]
Subject: Axis2 OMText to File

Hi,

I am trying to take my OMText element and put the contents in a file,
but I keep going OutOfMemory.

Here is the server code:
                OMElement data = fac.createOMElement("mtomSample",
omNs);
                OMElement file = fac.createOMElement("file", omNs);

                FileDataSource fileDataSource = new FileDataSource(
                                "C:/temp/local_cert.txt");
                DataHandler dataHandler = new
DataHandler(fileDataSource);

                OMText textData = fac.createOMText(dataHandler, true);
                file.addChild(textData);
                data.addChild(file);

Client code (this goes out of memory):

        OMText binaryNode = (OMText) _imageElement.getFirstOMChild();

        FileOutputStream fileOutputStream = new
FileOutputStream("C:/temp/returnFile.txt");
        binaryNode.serialize(fileOutputStream);

Any ideas?

Roshan Punnoose
Phone: 301-497-6039

-----Original Message-----
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2006 10:47 AM
To: [email protected]
Subject: Re: [Axis2] eager service initialization

Its part of the nightlies under the Service.startUp() interface ...
just have your service implement it .

Robert

On 9/12/06, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> some time ago somebody raised an issue about eager service
> initialization (i.e. at system startup). Is there any news about it?
>
> Thanks,
> Michele
>
> ---------------------------------------------------------------------
> 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]



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




--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

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

Reply via email to