[jira] Updated: (AXIS2-3969) JAXWS end-to-end test clean-up
[ https://issues.apache.org/jira/browse/AXIS2-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3969: Attachment: patch1.txt patch > JAXWS end-to-end test clean-up > --- > > Key: AXIS2-3969 > URL: https://issues.apache.org/jira/browse/AXIS2-3969 > Project: Axis 2.0 (Axis2) > Issue Type: Test > Components: jaxws > Environment: windows >Reporter: Samuel Isokpunwu > Attachments: patch1.txt > > > "Class already define" compilation errors in jaxws-integration and metadata > packages. > The duplications of test artifacts classes with identical package names > across these packages are causing compilation errors when deployed into > eclipse IDE. > Adjusted some of the test package structure of jaxws-integration and metadata > test package to resolve these errors. > Also updated pom.xml of jaxws-integration package to reflect some of this > package updates. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3969) JAXWS end-to-end test clean-up
JAXWS end-to-end test clean-up --- Key: AXIS2-3969 URL: https://issues.apache.org/jira/browse/AXIS2-3969 Project: Axis 2.0 (Axis2) Issue Type: Test Components: jaxws Environment: windows Reporter: Samuel Isokpunwu "Class already define" compilation errors in jaxws-integration and metadata packages. The duplications of test artifacts classes with identical package names across these packages are causing compilation errors when deployed into eclipse IDE. Adjusted some of the test package structure of jaxws-integration and metadata test package to resolve these errors. Also updated pom.xml of jaxws-integration package to reflect some of this package updates. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3963) Null DataHandler objects as MIME attachments
[ https://issues.apache.org/jira/browse/AXIS2-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3963: Attachment: patch3.txt updated patch. > Null DataHandler objects as MIME attachments > > > Key: AXIS2-3963 > URL: https://issues.apache.org/jira/browse/AXIS2-3963 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: windows >Reporter: Samuel Isokpunwu >Assignee: Rich Scheuerle > Attachments: patch3.txt > > > Using SWA- raw MIME attachments, it is desireable to be able specify a null > DataHandler object as a method parameter > when there is no attachment to be returned. (For example, in a document > retrieval service when the document image is > not found).Both client and server threw NPE's when this happened. > This change allows this to work. > The resulting soap message message is a mime type message with only one part, > the soap envelope. This is allowable > per WS-I.Attachment Profile 1.0 clause R2917. > Code description and implementation was originally done by Bruce > Tiffany/Austin/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3963) Null DataHandler objects as MIME attachments
[ https://issues.apache.org/jira/browse/AXIS2-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3963: Attachment: (was: patch1.txt) > Null DataHandler objects as MIME attachments > > > Key: AXIS2-3963 > URL: https://issues.apache.org/jira/browse/AXIS2-3963 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: windows >Reporter: Samuel Isokpunwu >Assignee: Rich Scheuerle > > Using SWA- raw MIME attachments, it is desireable to be able specify a null > DataHandler object as a method parameter > when there is no attachment to be returned. (For example, in a document > retrieval service when the document image is > not found).Both client and server threw NPE's when this happened. > This change allows this to work. > The resulting soap message message is a mime type message with only one part, > the soap envelope. This is allowable > per WS-I.Attachment Profile 1.0 clause R2917. > Code description and implementation was originally done by Bruce > Tiffany/Austin/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3963) Null DataHandler objects as MIME attachments
[ https://issues.apache.org/jira/browse/AXIS2-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3963: Attachment: patch1.txt Patch > Null DataHandler objects as MIME attachments > > > Key: AXIS2-3963 > URL: https://issues.apache.org/jira/browse/AXIS2-3963 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: windows >Reporter: Samuel Isokpunwu > Attachments: patch1.txt > > > Using SWA- raw MIME attachments, it is desireable to be able specify a null > DataHandler object as a method parameter > when there is no attachment to be returned. (For example, in a document > retrieval service when the document image is > not found).Both client and server threw NPE's when this happened. > This change allows this to work. > The resulting soap message message is a mime type message with only one part, > the soap envelope. This is allowable > per WS-I.Attachment Profile 1.0 clause R2917. > Code description and implementation was originally done by Bruce > Tiffany/Austin/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3963) Null DataHandler objects as MIME attachments
Null DataHandler objects as MIME attachments Key: AXIS2-3963 URL: https://issues.apache.org/jira/browse/AXIS2-3963 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Environment: windows Reporter: Samuel Isokpunwu Using SWA- raw MIME attachments, it is desireable to be able specify a null DataHandler object as a method parameter when there is no attachment to be returned. (For example, in a document retrieval service when the document image is not found).Both client and server threw NPE's when this happened. This change allows this to work. The resulting soap message message is a mime type message with only one part, the soap envelope. This is allowable per WS-I.Attachment Profile 1.0 clause R2917. Code description and implementation was originally done by Bruce Tiffany/Austin/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3904) Remove limitation of Maintain Session value to String type.
[ https://issues.apache.org/jira/browse/AXIS2-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3904: Attachment: patch.txt > Remove limitation of Maintain Session value to String type. > --- > > Key: AXIS2-3904 > URL: https://issues.apache.org/jira/browse/AXIS2-3904 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: windows >Reporter: Samuel Isokpunwu > Attachments: patch.txt > > Original Estimate: 0h > Remaining Estimate: 0h > > Updated a method in BindingProvider.java in jaxws client side to return an > object type instead of casting the object to a String type. > This was done to accommodate applications that may return maintain session > value as any object type other than String. > Prior code: > --- > . > String sessionValue = null; > . > sessionValue = (String)properties.get(sessionKey); > . > requestContext.put(HTTPConstants.COOKIE_STRING, sessionValue); > Current changes: > --- > . > Object sessionValue = null; > . > sessionValue = properties.get(sessionKey); > . > requestContext.put(HTTPConstants.COOKIE_STRING, sessionValue); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3904) Remove limitation of Maintain Session value to String type.
Remove limitation of Maintain Session value to String type. --- Key: AXIS2-3904 URL: https://issues.apache.org/jira/browse/AXIS2-3904 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Environment: windows Reporter: Samuel Isokpunwu Updated a method in BindingProvider.java in jaxws client side to return an object type instead of casting the object to a String type. This was done to accommodate applications that may return maintain session value as any object type other than String. Prior code: --- . String sessionValue = null; . sessionValue = (String)properties.get(sessionKey); . requestContext.put(HTTPConstants.COOKIE_STRING, sessionValue); Current changes: --- . Object sessionValue = null; . sessionValue = properties.get(sessionKey); . requestContext.put(HTTPConstants.COOKIE_STRING, sessionValue); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3358) Scrub jaxws module for NLS
[ https://issues.apache.org/jira/browse/AXIS2-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3358: Attachment: jpatch.txt patch for jaxws module scrub for NLS > Scrub jaxws module for NLS > --- > > Key: AXIS2-3358 > URL: https://issues.apache.org/jira/browse/AXIS2-3358 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: win >Reporter: Samuel Isokpunwu > Attachments: jpatch.txt > > > Scrubbed the axis2 jaxws module to insure that hard coded message strings > param to Exception classes are removed and are placed in the proper NLS file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3358) Scrub jaxws module for NLS
Scrub jaxws module for NLS --- Key: AXIS2-3358 URL: https://issues.apache.org/jira/browse/AXIS2-3358 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Environment: win Reporter: Samuel Isokpunwu Scrubbed the axis2 jaxws module to insure that hard coded message strings param to Exception classes are removed and are placed in the proper NLS file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3261) Scrub metadata module for NLS
[ https://issues.apache.org/jira/browse/AXIS2-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3261: Attachment: patch.txt patch for updated files. > Scrub metadata module for NLS > -- > > Key: AXIS2-3261 > URL: https://issues.apache.org/jira/browse/AXIS2-3261 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: modules > Environment: Win >Reporter: Samuel Isokpunwu >Priority: Minor > Attachments: patch.txt > > > Scrubbed the axis2 metadata module to insure that hard coded message strings > are removed and are placed in the proper NLS file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3261) Scrub metadata module for NLS
Scrub metadata module for NLS -- Key: AXIS2-3261 URL: https://issues.apache.org/jira/browse/AXIS2-3261 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: modules Environment: Win Reporter: Samuel Isokpunwu Priority: Minor Scrubbed the axis2 metadata module to insure that hard coded message strings are removed and are placed in the proper NLS file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3254) Add log statements to jaxws msg util classes
[ https://issues.apache.org/jira/browse/AXIS2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3254: Attachment: patch.txt A patch > Add log statements to jaxws msg util classes > > > Key: AXIS2-3254 > URL: https://issues.apache.org/jira/browse/AXIS2-3254 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: Win >Reporter: Samuel Isokpunwu >Priority: Minor > Attachments: patch.txt > > > Added some trace statements to jaxws message util class to get a more > meaningful trace information during problem determination. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3254) Add log statements to jaxws msg util classes
Add log statements to jaxws msg util classes Key: AXIS2-3254 URL: https://issues.apache.org/jira/browse/AXIS2-3254 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Environment: Win Reporter: Samuel Isokpunwu Priority: Minor Added some trace statements to jaxws message util class to get a more meaningful trace information during problem determination. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3127) Null pointer exception in Axis2
[ https://issues.apache.org/jira/browse/AXIS2-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3127: Attachment: hpatch.txt A patch to fix the problem > Null pointer exception in Axis2 > --- > > Key: AXIS2-3127 > URL: https://issues.apache.org/jira/browse/AXIS2-3127 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel > Environment: win >Reporter: Samuel Isokpunwu > Attachments: hpatch.txt > > > Added a null check to a method in org.apache.axis2.engine.Handler.java to > prevent client apps from getting a NPE > if the engine fails to successfully handle a given message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3127) Null pointer exception in Axis2
Null pointer exception in Axis2 --- Key: AXIS2-3127 URL: https://issues.apache.org/jira/browse/AXIS2-3127 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Environment: win Reporter: Samuel Isokpunwu Added a null check to a method in org.apache.axis2.engine.Handler.java to prevent client apps from getting a NPE if the engine fails to successfully handle a given message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3126) NPE when parsing Async resonse in jaxws client side
[ https://issues.apache.org/jira/browse/AXIS2-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3126: Attachment: a69541patch.txt A patch to resolve problem > NPE when parsing Async resonse in jaxws client side > > > Key: AXIS2-3126 > URL: https://issues.apache.org/jira/browse/AXIS2-3126 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws > Environment: Win >Reporter: Samuel Isokpunwu >Assignee: Rich Scheuerle > Attachments: a69541patch.txt > > > Trying to push Mike Rheinheimer's fix, with few modifications, to the apache > community source. > The webcontainer tries to clean up its threads as fast as possible, which can > mean that once it "drops off" the async response, and the JAXWS layer takes > its time processing that response, the inputstream object under it can get > nulled out, resulting in an NPE in the parser. > AsyncResponse now processes the response right away in onComplete() or > onError() rather than waiting until a poll comes through to call get() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3126) NPE when parsing Async resonse in jaxws client side
NPE when parsing Async resonse in jaxws client side Key: AXIS2-3126 URL: https://issues.apache.org/jira/browse/AXIS2-3126 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Environment: Win Reporter: Samuel Isokpunwu Trying to push Mike Rheinheimer's fix, with few modifications, to the apache community source. The webcontainer tries to clean up its threads as fast as possible, which can mean that once it "drops off" the async response, and the JAXWS layer takes its time processing that response, the inputstream object under it can get nulled out, resulting in an NPE in the parser. AsyncResponse now processes the response right away in onComplete() or onError() rather than waiting until a poll comes through to call get() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-3012) Invalid param in content-Type with multipart/related value
[ https://issues.apache.org/jira/browse/AXIS2-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515305 ] Samuel Isokpunwu commented on AXIS2-3012: - Thilina. I do not have a committer status. You or someone with committer status have to commit the patch > Invalid param in content-Type with multipart/related value > -- > > Key: AXIS2-3012 > URL: https://issues.apache.org/jira/browse/AXIS2-3012 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: transports >Reporter: Samuel Isokpunwu >Assignee: Thilina Gunarathne > Attachments: bt68092patch.txt > > > Per RFC2387, A content-Type header field with a "multipart/related" value > must not include any encoding as > a parameter. Current implementation is including charset=UTF-8 parameter in > the content-type header field. > Will be providing a patch to resolve this defect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-3012) Invalid param in content-Type with multipart/related value
[ https://issues.apache.org/jira/browse/AXIS2-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-3012: Attachment: bt68092patch.txt A patch to resolve code defect. > Invalid param in content-Type with multipart/related value > -- > > Key: AXIS2-3012 > URL: https://issues.apache.org/jira/browse/AXIS2-3012 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: transports >Reporter: Samuel Isokpunwu > Attachments: bt68092patch.txt > > > Per RFC2387, A content-Type header field with a "multipart/related" value > must not include any encoding as > a parameter. Current implementation is including charset=UTF-8 parameter in > the content-type header field. > Will be providing a patch to resolve this defect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-3012) Invalid param in content-Type with multipart/related value
Invalid param in content-Type with multipart/related value -- Key: AXIS2-3012 URL: https://issues.apache.org/jira/browse/AXIS2-3012 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Reporter: Samuel Isokpunwu Per RFC2387, A content-Type header field with a "multipart/related" value must not include any encoding as a parameter. Current implementation is including charset=UTF-8 parameter in the content-type header field. Will be providing a patch to resolve this defect. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2596) Clean up cached attachment files
[ https://issues.apache.org/jira/browse/AXIS2-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-2596: Attachment: bt66899patch.txt A patch for the code changes > Clean up cached attachment files > > > Key: AXIS2-2596 > URL: https://issues.apache.org/jira/browse/AXIS2-2596 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: transports > Environment: Win XP >Reporter: Samuel Isokpunwu >Assignee: Thilina Gunarathne > Attachments: bt66899patch.txt > > > Added some code to clean up cached attachement files after use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (AXIS2-2596) Clean up cached attachment files
[ https://issues.apache.org/jira/browse/AXIS2-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu reopened AXIS2-2596: - With attachment caching to the disk enabled, cached attachment file created is not deleted after use. This will lead to an out of space condition especially with large attachment files. Added a method to org.apache.axis2.transport.TransportUtils.java and org.apache.axis2.jaxws.message.attachments.AttachmentUtils.java to delete server and client side cached attachment files after use respectively. Initially, The cache attachment file deletion seem to be a simple problem to resolve by adding a line of code to the org.apache.axiom.attachments.PartOnFile.java constructor to execute deleteOnExit() method call on the cached attachment file as soon as the file is created. With this approach, the cached file created on the client side after processing the client response message is deleted after use but the one created on the server side after processing the request message is not deleted after use. Was Not able to determine the reasons for failure within the time spent on debugging but suspected that the file object may still be held in memory after use. Also tried to create a CachedFile.java wrapper that implements object.finalize() method to delete the cached attachment file once the GC is executed by the JVM. Apart from the inherent performance problem with this approach, some of the test scenario also failed perhalp due to JVM object reactivation policy for an object that was initially garbage collected. The best working solution, so far, to cover all known testcase scenarios and to avoid deleting the cached attachment file prematurely or before it is read, was to -- 1. Delete the server side cached attachment file after the server response message is processed. In the case of the Application Server I was working with, the cached attachment file delete was done within a finally block in the doPost() method of a servlet that extends the org.apache.axis2.transport.http.AxisServlet.java 2. Leaving the file.deleteOnExit() method call in org.apache.axiom.attachments.PartOnFile.java to take care of the client side cached attachment file deletion was causing data fragmentation that resulted in a significant performance degradation. To resolve the data fragementation problem, the deleteOnExit() method call was removed from PartOnFile.java and then add a method to jaxws client code to check response message for cached attachment file and if a cached file exist, execute the cached file object's deleteOnExit() method. Will include a patch to show all the file changes and for the patch to be committed if the changes are acceptable to the community. > Clean up cached attachment files > > > Key: AXIS2-2596 > URL: https://issues.apache.org/jira/browse/AXIS2-2596 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: transports > Environment: Win XP >Reporter: Samuel Isokpunwu >Assignee: Thilina Gunarathne > > Added some code to clean up cached attachement files after use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2978) Attachment optimization properties are not current in client request context
[
https://issues.apache.org/jira/browse/AXIS2-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Isokpunwu updated AXIS2-2978:
Attachment: bt66899patch.txt
A patch for the defect.
> Attachment optimization properties are not current in client request context
>
>
> Key: AXIS2-2978
> URL: https://issues.apache.org/jira/browse/AXIS2-2978
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
>Affects Versions: M2
>Reporter: Samuel Isokpunwu
> Attachments: bt66899patch.txt
>
>
> The client request context is not properly updated when mtom enablement state
> properties changes.
> Example test scenario:
>{
> -
> -
> SOAPBinding binding = (SOAPBinding)dispatch.getBinding();
> binding.setMTOMEnabled(true);
> -
> response = dispatch.invoke(request);
> -
> binding.setMTOMEnabled(false);
> -
> response = dispatch.invoke(request);
> -
> -
>}
> Since the client request context for a previous request is being cached and
> reused for a subsequent request, any attachment optimization properties
> changes, in the test scenario above, are ignored. Will be adding code to
> check and copy over any new properties updates.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2978) Attachment optimization properties are not current in client request context
Attachment optimization properties are not current in client request context
Key: AXIS2-2978
URL: https://issues.apache.org/jira/browse/AXIS2-2978
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Affects Versions: M2
Reporter: Samuel Isokpunwu
The client request context is not properly updated when mtom enablement state
properties changes.
Example test scenario:
{
-
-
SOAPBinding binding = (SOAPBinding)dispatch.getBinding();
binding.setMTOMEnabled(true);
-
response = dispatch.invoke(request);
-
binding.setMTOMEnabled(false);
-
response = dispatch.invoke(request);
-
-
}
Since the client request context for a previous request is being cached and
reused for a subsequent request, any attachment optimization properties
changes, in the test scenario above, are ignored. Will be adding code to check
and copy over any new properties updates.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2-2596) Clean up cached attachment files
[ https://issues.apache.org/jira/browse/AXIS2-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu closed AXIS2-2596. --- Resolution: Later Needed time to integrate fix into Apache CS. > Clean up cached attachment files > > > Key: AXIS2-2596 > URL: https://issues.apache.org/jira/browse/AXIS2-2596 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: transports > Environment: Win XP >Reporter: Samuel Isokpunwu >Assignee: Thilina Gunarathne > > Added some code to clean up cached attachement files after use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2648) Clean up cached attachment files
Clean up cached attachment files Key: AXIS2-2648 URL: https://issues.apache.org/jira/browse/AXIS2-2648 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Environment: Win XP Reporter: Samuel Isokpunwu Added seem code to jaxws client side implementation to check for attachment caching enablement. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2596) Clean up cached attachment files
Clean up cached attachment files Key: AXIS2-2596 URL: https://issues.apache.org/jira/browse/AXIS2-2596 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Environment: Win XP Reporter: Samuel Isokpunwu Added some code to clean up cached attachement files after use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2448) url rewrite not working when using policy set
url rewrite not working when using policy set - Key: AXIS2-2448 URL: https://issues.apache.org/jira/browse/AXIS2-2448 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Environment: Windows Reporter: Samuel Isokpunwu Will be adding some jaxws client code to check for Maintain Session enblement by the Transport layer when client application enable Maintain Session using Policy Set. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2092) Byte array attachments type
[ https://issues.apache.org/jira/browse/AXIS2-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470268 ] Samuel Isokpunwu commented on AXIS2-2092: - Initially I used ByteArrayDataSource for the implementation but was having problem with JAXB attachment marshaller in the server side response to the client application. >From further debugging, the JAXB Attachment marshaller uses MimePartDataSource >when marshalling the byte array DataHandler request from the client >application and hence for reasons I was not able to determine, the jaxws >attachment marshaller implementation using ByteArrayDataSource was failing on >the server side response message to the client application. Apart from the fact that JAXB attachment implementation uses MimePartDataSource, Also from reading the mime part APIs, It seem that the MimePartDataSource usage is the best approach for messages with mime headers and attachment. > Byte array attachments type > --- > > Key: AXIS2-2092 > URL: https://issues.apache.org/jira/browse/AXIS2-2092 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: Win XP >Reporter: Samuel Isokpunwu > Assigned To: Rich Scheuerle > Attachments: d417707patch.txt, patch.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2092) Byte array attachments type
[ https://issues.apache.org/jira/browse/AXIS2-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-2092: Attachment: d417707patch.txt A patch to fix the problem. > Byte array attachments type > --- > > Key: AXIS2-2092 > URL: https://issues.apache.org/jira/browse/AXIS2-2092 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws > Environment: Win XP >Reporter: Samuel Isokpunwu > Assigned To: Rich Scheuerle > Attachments: d417707patch.txt > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2092) Byte array attachments type
Byte array attachments type --- Key: AXIS2-2092 URL: https://issues.apache.org/jira/browse/AXIS2-2092 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Environment: Win XP Reporter: Samuel Isokpunwu Adding enhancement to the attachment optimization code to properly marshall a byte array attachment type. The current code work well when attachment type is a DataHandler. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2061) Wrong SOAPBinding API import
[ https://issues.apache.org/jira/browse/AXIS2-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-2061: Attachment: proxyClientpatch.txt A patch to fix the problem. > Wrong SOAPBinding API import > - > > Key: AXIS2-2061 > URL: https://issues.apache.org/jira/browse/AXIS2-2061 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws > Environment: Win XP >Reporter: Samuel Isokpunwu > Attachments: proxyClientpatch.txt > > > Wrong SOAPBinding API import causes the Poxy client side attachment > optimization code path to be skipped even when optimization is enabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2061) Wrong SOAPBinding API import
Wrong SOAPBinding API import - Key: AXIS2-2061 URL: https://issues.apache.org/jira/browse/AXIS2-2061 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Environment: Win XP Reporter: Samuel Isokpunwu Wrong SOAPBinding API import causes the Poxy client side attachment optimization code path to be skipped even when optimization is enabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2060) Compilation error in WSDL20ToAxisServiceBuilder.java
[ https://issues.apache.org/jira/browse/AXIS2-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-2060: Attachment: patch.txt Suggested patch for the compilation error. > Compilation error in WSDL20ToAxisServiceBuilder.java > > > Key: AXIS2-2060 > URL: https://issues.apache.org/jira/browse/AXIS2-2060 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel > Environment: Win XP >Reporter: Samuel Isokpunwu > Attachments: patch.txt > > > Getting compilation error in > org.apache.axis2.description.WSDL20ToAxisServiceBuilder.java trying to build > the latest Axis2 src extract. > There are type mismatch btw Description and DescriptionElements in three > diferent areas of the code in statements like: >Description description = wsdlReader.readWSDL(wsdlUri); > Not sure why there are statements like: > WSDLReader wsdlReader = WSDLFactory.newInstance().newWSDLReader(); > Description description = wsdlReader.readWSDL(wsdlUri); > DescriptionElement descriptionElement = description.toElement(); > Instead of: > WSDLReader wsdlReader = WSDLFactory.newInstance().newWSDLReader(); > DescriptionElement descriptionElement = wsdlReader.readWSDL(wsdlUri); > But if the right approach is to get DescriptionElement through > Description.toElement(), then to fix the compilation error will simply be by > type casting wsdlReader.readWSDL(wsdlUri) to Description. > Description description = (Description)wsdlReader.readWSDL(wsdlUri); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2060) Compilation error in WSDL20ToAxisServiceBuilder.java
Compilation error in WSDL20ToAxisServiceBuilder.java Key: AXIS2-2060 URL: https://issues.apache.org/jira/browse/AXIS2-2060 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: kernel Environment: Win XP Reporter: Samuel Isokpunwu Attachments: patch.txt Getting compilation error in org.apache.axis2.description.WSDL20ToAxisServiceBuilder.java trying to build the latest Axis2 src extract. There are type mismatch btw Description and DescriptionElements in three diferent areas of the code in statements like: Description description = wsdlReader.readWSDL(wsdlUri); Not sure why there are statements like: WSDLReader wsdlReader = WSDLFactory.newInstance().newWSDLReader(); Description description = wsdlReader.readWSDL(wsdlUri); DescriptionElement descriptionElement = description.toElement(); Instead of: WSDLReader wsdlReader = WSDLFactory.newInstance().newWSDLReader(); DescriptionElement descriptionElement = wsdlReader.readWSDL(wsdlUri); But if the right approach is to get DescriptionElement through Description.toElement(), then to fix the compilation error will simply be by type casting wsdlReader.readWSDL(wsdlUri) to Description. Description description = (Description)wsdlReader.readWSDL(wsdlUri); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2041) JAXB error when marshalling optimized attachment
[ https://issues.apache.org/jira/browse/AXIS2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-2041: Description: The marshalling of optimized attachment by JAXB sometimes results in an erroneous XML envelop. (was: The marshalling of optimized attachment by JAXB sometimes result in a erroneous XML envelop. ) > JAXB error when marshalling optimized attachment > > > Key: AXIS2-2041 > URL: https://issues.apache.org/jira/browse/AXIS2-2041 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: 1.1.1 > Environment: Win XP >Reporter: Samuel Isokpunwu > Attachments: d416103patch.txt > > > The marshalling of optimized attachment by JAXB sometimes results in an > erroneous XML envelop. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-2041) JAXB error when marshalling optimized attachment
[ https://issues.apache.org/jira/browse/AXIS2-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-2041: Attachment: d416103patch.txt A patch to fix the problem > JAXB error when marshalling optimized attachment > > > Key: AXIS2-2041 > URL: https://issues.apache.org/jira/browse/AXIS2-2041 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: 1.1.1 > Environment: Win XP >Reporter: Samuel Isokpunwu > Attachments: d416103patch.txt > > > The marshalling of optimized attachment by JAXB sometimes result in a > erroneous XML envelop. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-2041) JAXB error when marshalling optimized attachment
JAXB error when marshalling optimized attachment Key: AXIS2-2041 URL: https://issues.apache.org/jira/browse/AXIS2-2041 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.1.1 Environment: Win XP Reporter: Samuel Isokpunwu The marshalling of optimized attachment by JAXB sometimes result in a erroneous XML envelop. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1999) Jaxws Attachment optimization code is skipped
[ https://issues.apache.org/jira/browse/AXIS2-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Isokpunwu updated AXIS2-1999: Attachment: d414263patch.txt > Jaxws Attachment optimization code is skipped > - > > Key: AXIS2-1999 > URL: https://issues.apache.org/jira/browse/AXIS2-1999 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws > Environment: Win XP >Reporter: Samuel Isokpunwu > Attachments: d414263patch.txt > > > Due to some code rework in the message and attachments components of JAXWS, > the attachment optimization, using XOP processing, code path is always > skipped even when attachment optimization is enabled in either the client or > the server side of JAXWS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1999) Jaxws Attachment optimization code is skipped
Jaxws Attachment optimization code is skipped - Key: AXIS2-1999 URL: https://issues.apache.org/jira/browse/AXIS2-1999 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Environment: Win XP Reporter: Samuel Isokpunwu Due to some code rework in the message and attachments components of JAXWS, the attachment optimization, using XOP processing, code path is always skipped even when attachment optimization is enabled in either the client or the server side of JAXWS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1623) Attachment optimization using JAXWS SOAP Binding properties for MTOM
[ http://issues.apache.org/jira/browse/AXIS2-1623?page=all ]
Samuel Isokpunwu updated AXIS2-1623:
Attachment: d402093-patch.txt
A patch for the enhancement implementation code.
> Attachment optimization using JAXWS SOAP Binding properties for MTOM
>
>
> Key: AXIS2-1623
> URL: http://issues.apache.org/jira/browse/AXIS2-1623
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
>Affects Versions: 1.1
> Environment: Windows
>Reporter: Samuel Isokpunwu
>Priority: Critical
> Attachments: d402093-patch.txt
>
>
> Per current support, JAXWS client can only enable attachment optimization by
> setting the ENABLEMTOM variable to "true" using the setMTOMEnabled() method
> in the SOAPBinding API.
> This enhancement will give client an alternate way to enable optimization
> just by specifying the SOAP Binding properties for MTOM as the binding
> protocol.
> Currently, using Dispatch invocation for example, JAXWS client can only
> enable attachment optimization by doing the following--
> {
> --
> service.addPort(QNAME_PORT, SOAPBinding.SOAP11HTTP_BINDING,
> URL_ENDPOINT);
> ---
> ---
> SOAPBinding binding = (SOAPBinding) dispatch.getBinding();
> binding.setMTOMEnabled(true);
> }
> With this enhancement, JAXWS client can also enable optimization just by
> specifying the SOAP binding property for MTOM --
> {
> --
> service.addPort(QNAME_PORT, SOAPBinding.SOAP11HTTP_MTOM_BINDING,
> URL_ENDPOINT);
> ---
> ---
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1623) Attachment optimization using JAXWS SOAP Binding properties for MTOM
Attachment optimization using JAXWS SOAP Binding properties for MTOM
Key: AXIS2-1623
URL: http://issues.apache.org/jira/browse/AXIS2-1623
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: jaxws
Affects Versions: 1.1
Environment: Windows
Reporter: Samuel Isokpunwu
Priority: Critical
Per current support, JAXWS client can only enable attachment optimization by
setting the ENABLEMTOM variable to "true" using the setMTOMEnabled() method
in the SOAPBinding API.
This enhancement will give client an alternate way to enable optimization just
by specifying the SOAP Binding properties for MTOM as the binding protocol.
Currently, using Dispatch invocation for example, JAXWS client can only enable
attachment optimization by doing the following--
{
--
service.addPort(QNAME_PORT, SOAPBinding.SOAP11HTTP_BINDING, URL_ENDPOINT);
---
---
SOAPBinding binding = (SOAPBinding) dispatch.getBinding();
binding.setMTOMEnabled(true);
}
With this enhancement, JAXWS client can also enable optimization just by
specifying the SOAP binding property for MTOM --
{
--
service.addPort(QNAME_PORT, SOAPBinding.SOAP11HTTP_MTOM_BINDING,
URL_ENDPOINT);
---
---
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1554) Session Management Support
Session Management Support -- Key: AXIS2-1554 URL: http://issues.apache.org/jira/browse/AXIS2-1554 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Environment: Windows Reporter: Samuel Isokpunwu Adding support for Session Management per JAXWS Specification section 10.4.1.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1318) Basic Authentication support
[ http://issues.apache.org/jira/browse/AXIS2-1318?page=all ] Samuel Isokpunwu updated AXIS2-1318: Attachment: BasicAuthpatch.txt Source code and testcase for JAXWS Basic Authentication support. > Basic Authentication support > > > Key: AXIS2-1318 > URL: http://issues.apache.org/jira/browse/AXIS2-1318 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: jaxws >Affects Versions: 1.0 > Environment: Windows >Reporter: Samuel Isokpunwu >Priority: Critical > Attachments: BasicAuthpatch.txt > > > Working on providing HTTP Basic Authentication support per JAXWS > Specification, Section 10.4.1.3 -- Security. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1318) Basic Authentication support
Basic Authentication support Key: AXIS2-1318 URL: http://issues.apache.org/jira/browse/AXIS2-1318 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws Affects Versions: 1.0 Environment: Windows Reporter: Samuel Isokpunwu Priority: Critical Working on providing HTTP Basic Authentication support per JAXWS Specification, Section 10.4.1.3 -- Security. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1212) Dispatch invocations.
Dispatch invocations. - Key: AXIS2-1212 URL: http://issues.apache.org/jira/browse/AXIS2-1212 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Affects Versions: 1.0 Environment: Windows XP Reporter: Samuel Isokpunwu Enhancement update to Dispatch implementation class to validate invocation parameter values and to throw the appropriate WebServiceException when parameter values are invalid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-1184) Dispatch ClassCastException with DOMSource
[ http://issues.apache.org/jira/browse/AXIS2-1184?page=all ] Samuel Isokpunwu updated AXIS2-1184: Attachment: d383139a-patch.txt A patch to fix the ClassCastException. > Dispatch ClassCastException with DOMSource > -- > > Key: AXIS2-1184 > URL: http://issues.apache.org/jira/browse/AXIS2-1184 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: 1.0 >Reporter: Samuel Isokpunwu > Attachments: d383139a-patch.txt > > > Dispatch.invoke and Dispach.invokeOneWay throw ClassCastException. Here's > stack traces for invokes in > MESSAGE and PAYLOAD modes: > Dispatch.invoke and Dispach.invokeOneWay throw ClassCastException. Here's > stack traces for invokes in > MESSAGE and PAYLOAD modes: > Clientside Stack Trace when doing invoke in MESSAGE mode: > java.lang.ClassCastException: org.apache.xerces.dom.DeferredDocumentImpl > incompatible with org.w3c.dom.Element >at > org.apache.axis2.jaxws.message.databinding.impl.SourceBlockImpl._getReaderFromBO(SourceBlockImpl.java:139) >at > org.apache.axis2.jaxws.message.impl.BlockImpl.getXMLStreamReader(BlockImpl.java:180) >at > org.apache.axis2.jaxws.client.XMLDispatch.createMessageFromValue(XMLDispatch.java:109) >at > org.apache.axis2.jaxws.client.BaseDispatch.invoke(BaseDispatch.java:109) >at > jaxws.dispatch.wsfvt.test.DOMSourceTest.testTwoWay_MessageMode(DOMSourceTest.java:92) > Clientside Stack Trace when doing invoke in PAYLOAD mode: > java.lang.ClassCastException: org.apache.xerces.dom.DeferredDocumentImpl > incompatible with org.w3c.dom.Element >at > org.apache.axis2.jaxws.message.databinding.impl.SourceBlockImpl._getReaderFromBO(SourceBlockImpl.java:139) >at > org.apache.axis2.jaxws.message.impl.BlockImpl.getXMLStreamReader(BlockImpl.java:180) >at > org.apache.axis2.jaxws.message.impl.XMLStreamReaderForXMLSpine.pushBlocks(XMLStreamReaderForXMLSpine.java:158) >at > org.apache.axis2.jaxws.message.impl.XMLStreamReaderForXMLSpine.next(XMLStreamReaderForXMLSpine.java:96) >at > org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:929) >at > org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:74) >at > org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:59) >at > org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:490) >at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:792) >at > org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:177) >at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:811) >at > org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:378) >at > org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput(SOAPOverHTTPSender.java:169) >at > org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.writeRequest(SOAPOverHTTPSender.java:205) >at > org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) >at > org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973) >at > org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) >at > org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) >at > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) >at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) >at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) >at > org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:660) >at > org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:110) >at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:308) >at > org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206) >at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:666) >at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:349) >at > org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:280) >at > org.apache.axis2.jaxws.core.controller.AxisInvocationController.invoke(AxisInvocationController.java:130) >at > org.apache.axis2.jaxws.client.BaseDispatch.invoke(BaseDispat
[jira] Created: (AXIS2-1184) Dispatch ClassCastException with DOMSource
Dispatch ClassCastException with DOMSource -- Key: AXIS2-1184 URL: http://issues.apache.org/jira/browse/AXIS2-1184 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Affects Versions: 1.0 Reporter: Samuel Isokpunwu Dispatch.invoke and Dispach.invokeOneWay throw ClassCastException. Here's stack traces for invokes in MESSAGE and PAYLOAD modes: Dispatch.invoke and Dispach.invokeOneWay throw ClassCastException. Here's stack traces for invokes in MESSAGE and PAYLOAD modes: Clientside Stack Trace when doing invoke in MESSAGE mode: java.lang.ClassCastException: org.apache.xerces.dom.DeferredDocumentImpl incompatible with org.w3c.dom.Element at org.apache.axis2.jaxws.message.databinding.impl.SourceBlockImpl._getReaderFromBO(SourceBlockImpl.java:139) at org.apache.axis2.jaxws.message.impl.BlockImpl.getXMLStreamReader(BlockImpl.java:180) at org.apache.axis2.jaxws.client.XMLDispatch.createMessageFromValue(XMLDispatch.java:109) at org.apache.axis2.jaxws.client.BaseDispatch.invoke(BaseDispatch.java:109) at jaxws.dispatch.wsfvt.test.DOMSourceTest.testTwoWay_MessageMode(DOMSourceTest.java:92) Clientside Stack Trace when doing invoke in PAYLOAD mode: java.lang.ClassCastException: org.apache.xerces.dom.DeferredDocumentImpl incompatible with org.w3c.dom.Element at org.apache.axis2.jaxws.message.databinding.impl.SourceBlockImpl._getReaderFromBO(SourceBlockImpl.java:139) at org.apache.axis2.jaxws.message.impl.BlockImpl.getXMLStreamReader(BlockImpl.java:180) at org.apache.axis2.jaxws.message.impl.XMLStreamReaderForXMLSpine.pushBlocks(XMLStreamReaderForXMLSpine.java:158) at org.apache.axis2.jaxws.message.impl.XMLStreamReaderForXMLSpine.next(XMLStreamReaderForXMLSpine.java:96) at org.apache.axiom.om.impl.llom.OMStAXWrapper.next(OMStAXWrapper.java:929) at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serializeNode(StreamingOMSerializer.java:74) at org.apache.axiom.om.impl.serialize.StreamingOMSerializer.serialize(StreamingOMSerializer.java:59) at org.apache.axiom.om.impl.util.OMSerializerUtil.serializeByPullStream(OMSerializerUtil.java:490) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:792) at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:177) at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:811) at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:378) at org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.handleOMOutput(SOAPOverHTTPSender.java:169) at org.apache.axis2.transport.http.SOAPOverHTTPSender$AxisSOAPRequestEntity.writeRequest(SOAPOverHTTPSender.java:205) at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:660) at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:110) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:308) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:206) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:666) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:349) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:280) at org.apache.axis2.jaxws.core.controller.AxisInvocationController.invoke(AxisInvocationController.java:130) at org.apache.axis2.jaxws.client.BaseDispatch.invoke(BaseDispatch.java:116) at jaxws.dispatch.wsfvt.test.DOMSourceTest.testTwoWay_PayloadMode(DOMSourceTest.java:115) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --
[jira] Updated: (AXIS2-1013) Compilation error in adb-codegen module
[ http://issues.apache.org/jira/browse/AXIS2-1013?page=all ] Samuel Isokpunwu updated AXIS2-1013: Attachment: SchemaCompilerPatch.txt A patch to fix the syntax error. > Compilation error in adb-codegen module > --- > > Key: AXIS2-1013 > URL: http://issues.apache.org/jira/browse/AXIS2-1013 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: databinding >Affects Versions: 1.0 >Reporter: Samuel Isokpunwu > Attachments: SchemaCompilerPatch.txt > > > Syntax error while compiling org.apache.axis2.schema.SchemaCompiler. > Primitive token type "enum" is used a variable name in the following > expression -- > XmlSchemaEnumerationFacet enum = (XmlSchemaEnumerationFacet) obj; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-1013) Compilation error in adb-codegen module
Compilation error in adb-codegen module --- Key: AXIS2-1013 URL: http://issues.apache.org/jira/browse/AXIS2-1013 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: databinding Affects Versions: 1.0 Reporter: Samuel Isokpunwu Syntax error while compiling org.apache.axis2.schema.SchemaCompiler. Primitive token type "enum" is used a variable name in the following expression -- XmlSchemaEnumerationFacet enum = (XmlSchemaEnumerationFacet) obj; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-984) Sample testcase using JAXB generated artifacts.
[ http://issues.apache.org/jira/browse/AXIS2-984?page=all ] Samuel Isokpunwu updated AXIS2-984: --- Attachment: combinePatch.txt imagefile.jar This combinePatch.txt is an update to the patch earlier submitted. Also, the image file for the testcase could not be included in the patch hence the imagefile.jar. The image file itself (test.jpg) already existed within the Axis2 community source. The jar is mainly to give the resource location of the image file within the jaxws package structure. > Sample testcase using JAXB generated artifacts. > --- > > Key: AXIS2-984 > URL: http://issues.apache.org/jira/browse/AXIS2-984 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws >Affects Versions: 1.0 >Reporter: Samuel Isokpunwu > Assigned To: Rich Scheuerle > Attachments: combinePatch.txt, imagefile.jar, > JAXBProviderTestcasePatch.txt > > > These testcases uses a JAXB generated artifacts from a given XMLSchema to > send an image to a JAXWS Source Provider endpoint. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-984) Sample teatcase using JAXB generated artifacts.
[ http://issues.apache.org/jira/browse/AXIS2-984?page=all ] Samuel Isokpunwu updated AXIS2-984: --- Attachment: JAXBProviderTestcasePatch.txt Including a patch file for the testcase source code > Sample teatcase using JAXB generated artifacts. > --- > > Key: AXIS2-984 > URL: http://issues.apache.org/jira/browse/AXIS2-984 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: jaxws >Affects Versions: 1.0 >Reporter: Samuel Isokpunwu > Attachments: JAXBProviderTestcasePatch.txt > > > These testcases uses a JAXB generated artifacts from a given XMLSchema to > send an image to a JAXWS Source Provider endpoint. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-984) Sample teatcase using JAXB generated artifacts.
Sample teatcase using JAXB generated artifacts. --- Key: AXIS2-984 URL: http://issues.apache.org/jira/browse/AXIS2-984 Project: Apache Axis 2.0 (Axis2) Issue Type: Improvement Components: jaxws Affects Versions: 1.0 Reporter: Samuel Isokpunwu These testcases uses a JAXB generated artifacts from a given XMLSchema to send an image to a JAXWS Source Provider endpoint. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS2-905) An ExceptionFactory implementation
[ http://issues.apache.org/jira/browse/AXIS2-905?page=all ]
Samuel Isokpunwu updated AXIS2-905:
---
Attachment: ExceptionFactoryPatch.txt
Patch file for ExceptionFactory implementation code and testcase.
> An ExceptionFactory implementation
> --
>
> Key: AXIS2-905
> URL: http://issues.apache.org/jira/browse/AXIS2-905
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
>Affects Versions: 1.0
>Reporter: Samuel Isokpunwu
> Attachments: ExceptionFactoryPatch.txt
>
>
> Working on implementing an ExceptionFactory class that will wrap the JAXWS
> WebServiceException to eliminate any possible nested exception between
> WebServiceException and the root cause exception. The wrapper will also allow
> for easy addition of any useful information to facilitate traceability and
> serviceability.
> An example Usage:
>//implementing class example
>public class Foo{
> //Optional global initialization
> private ExceptionFactory ef [ = ExceptionFactory.instance(this,
> propertyFile) ];
>
> public Foo(){
> //Optionally, can choose to create or initialize the
> ExceptionFactory global variable from the
> //constructor
> ef = ExceptionFactory.instance(this, propertyFile);
> }
> ---
> ---
> public fooMethod(){
> try{
>throw ef.webServiceException([message | key]);
> }
> catch(Exception e){
>throw ef.webServiceException(e, [message | key]);
> }
> }
> ---
> ---
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-905) An ExceptionFactory implementation
An ExceptionFactory implementation
--
Key: AXIS2-905
URL: http://issues.apache.org/jira/browse/AXIS2-905
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: jaxws
Affects Versions: 1.0
Reporter: Samuel Isokpunwu
Working on implementing an ExceptionFactory class that will wrap the JAXWS
WebServiceException to eliminate any possible nested exception between
WebServiceException and the root cause exception. The wrapper will also allow
for easy addition of any useful information to facilitate traceability and
serviceability.
An example Usage:
//implementing class example
public class Foo{
//Optional global initialization
private ExceptionFactory ef [ = ExceptionFactory.instance(this,
propertyFile) ];
public Foo(){
//Optionally, can choose to create or initialize the
ExceptionFactory global variable from the
//constructor
ef = ExceptionFactory.instance(this, propertyFile);
}
---
---
public fooMethod(){
try{
throw ef.webServiceException([message | key]);
}
catch(Exception e){
throw ef.webServiceException(e, [message | key]);
}
}
---
---
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-882) Endpoint Controller framework
Endpoint Controller framework -- Key: AXIS2-882 URL: http://issues.apache.org/jira/browse/AXIS2-882 Project: Apache Axis 2.0 (Axis2) Type: New Feature Components: jaxws Versions: 1.0 Reporter: Samuel Isokpunwu Started work on cleaning up the JAXWSMessageReciever and the addition of an Endpoint Controller framework for easy service endpoints maintainability and to provide a reliable framework base for future service endpoint(s) enhancements per JAXWS specification. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-834) SocketTimeoutException when running attachment scenario.
SocketTimeoutException when running attachment scenario.
Key: AXIS2-834
URL: http://issues.apache.org/jira/browse/AXIS2-834
Project: Apache Axis 2.0 (Axis2)
Type: Test
Components: transports
Versions: 1.0
Environment: WIN OS
Reporter: Samuel Isokpunwu
I created a service class that will provide an image when given an image type
and a client that request for a given image type.
This test scenario is basically a reverse of one of the MTOM testcases, in the
sample package, to get an image instead of sending an image.
The service deployment was successful and I can trace the call up to the
service operation which successfully creates the response OMElement with the
requested image but I repeatedly get a timeout before the service response gets
to the client.
Could someone help review the test cases below and perhaps suggest what I may
have done wrong in the implementations.
My service impl method is this:
public OMElement imageDepot(OMElement element) throws Exception {
OMElement omeRequest = null;
for (Iterator iterator = element.getChildElements();
iterator.hasNext();) {
OMElement ome = (OMElement) iterator.next();
if (ome.getLocalName().equalsIgnoreCase("request")) {
omeRequest = ome;
}
}
if (omeRequest == null ) {
throw new AxisFault("Client request OMElement is
null");
}
if(omeRequest.getText().equalsIgnoreCase("jpeg")){
DataHandler expectedDH;
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs =
fac.createOMNamespace("urn://fakenamespace", "ns");
OMElement data = fac.createOMElement("response", omNs);
OMElement image = fac.createOMElement("image", omNs);
Image expectedImage = new ImageIO().loadImage(new
FileInputStream(new File("D:\\dev\\image\\test.jpg")));
ImageDataSource dataSource = new
ImageDataSource("test.jpg",expectedImage);
expectedDH = new DataHandler(dataSource);
OMText textData = fac.createOMText(expectedDH, true);
image.addChild(textData);
data.addChild(image);
return data;
}
The client implementation is this:
public void testGetImage() throws Exception{
OMElement result = getImage("jpeg");
OMElement omeImage = null;
for (Iterator _iterator = result.getChildElements();
_iterator.hasNext();) {
OMElement ome = (OMElement) _iterator.next();
if (ome.getLocalName().equalsIgnoreCase("image")) {
omeImage = ome;
}
}
if (omeImage == null ) {
throw new AxisFault("Image element content is null");
}
//Extract the image content and save it the data and saving
OMText imageReceived = (OMText) omeImage.getFirstOMChild();
DataHandler dh = (DataHandler) imageReceived.getDataHandler();
Image image = new
ImageIO().loadImage(dh.getDataSource().getInputStream());
FileOutputStream imageFOS = new FileOutputStream(ClientOutputFileName);
new ImageIO().saveImage(dh.getContentType(), image, imageFOS);
if(dh.getContentType().equalsIgnoreCase("image/jpeg")){
System.out.println("SUCESS");
}
public OMElement getImage(String imageType) throws Exception {
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace ns = fac.createOMNamespace("http://localhost/my";, "my");
OMElement operation = fac.createOMElement("imageDepot", ns);
OMElement request = fac.createOMElement("request", ns);
request.setText(imageType);
operation.addChild(request);
Options options = new Options();
options.setSoapVersionURI(SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI);
options.setTo(targetEPRName);
options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_FALSE);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
ServiceClient sender = new ServiceClient();
sender.setOptions(options);
return sender.sendReceive(operation);
}
The deployed service.xml is this:
This is a sample Web Service for illustrating MTOM based binary data
transfer.
sample.mtom.imagetransfer.service.MTOMService
urn:imageDepot
I continue to get the following socket timeout exception.
org.apache.axis2.AxisFault: Read timed out; nested exception is:
java.net
[jira] Updated: (AXIS2-806) Compilation errors in Axis2 tools package.
[ http://issues.apache.org/jira/browse/AXIS2-806?page=all ] Samuel Isokpunwu updated AXIS2-806: --- Attachment: WSDL2JavaGenerator-patch.txt This quick fix assume that the wsdlURI parameter points to a wsdl 1.1 verssion. A better fix should be to determine which builder to use based on the wsdl version. The current implementation of the wsdl builder classes did not allow for this. I will suggest that the determination of which builder to use should be done in the builder classes, preferably in the parent builder class accessable through a static reference to a method like getBuilderInstance(String wsdlURI) in the parent builder class or through a builder Abstract Factor or Abstract Factory methods. > Compilation errors in Axis2 tools package. > -- > > Key: AXIS2-806 > URL: http://issues.apache.org/jira/browse/AXIS2-806 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: Tools > Versions: 1.0 > Environment: Win XP > Reporter: Samuel Isokpunwu > Priority: Blocker > Attachments: WSDL2JavaGenerator-patch.txt > > > 1. The org.apache.axis2.tool.codegen.WSDL2JavaGenerator is referencing > org.apache.axis2.description.WSDL2AxisServiceBuilder builder class that no > longer exist in the current org.apache.axis2.description package. The > description package now contains WSDLToAxisServiceBuilder.java as parent > builder class with WSDL11ToAxisServiceBuilder and WSDL20ToAxisServiceBuilder > as subclasses. > 2. Also, the following line of code in > org.apache.axis2.tool.codegen.WSDL2JavaGenerator class -- > WSDL2AxisServiceBuilder builder = new > WSDL2AxisServiceBuilder(url.openConnection().getInputStream()); > will not only fail to compile because the class no longer exist in the Axis2 > description package, it will also fail to compile because the one-argument > Constructor that is being referenced in this line of code does not exist in > the newly created builder classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-806) Compilation errors in Axis2 tools package.
Compilation errors in Axis2 tools package. -- Key: AXIS2-806 URL: http://issues.apache.org/jira/browse/AXIS2-806 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: Tools Versions: 1.0 Environment: Win XP Reporter: Samuel Isokpunwu Priority: Blocker 1. The org.apache.axis2.tool.codegen.WSDL2JavaGenerator is referencing org.apache.axis2.description.WSDL2AxisServiceBuilder builder class that no longer exist in the current org.apache.axis2.description package. The description package now contains WSDLToAxisServiceBuilder.java as parent builder class with WSDL11ToAxisServiceBuilder and WSDL20ToAxisServiceBuilder as subclasses. 2. Also, the following line of code in org.apache.axis2.tool.codegen.WSDL2JavaGenerator class -- WSDL2AxisServiceBuilder builder = new WSDL2AxisServiceBuilder(url.openConnection().getInputStream()); will not only fail to compile because the class no longer exist in the Axis2 description package, it will also fail to compile because the one-argument Constructor that is being referenced in this line of code does not exist in the newly created builder classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
