[
https://issues.apache.org/jira/browse/AXIS2-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-1928.
-
Resolution: Fixed
fixed the issue. use the getType method to reso
Hi All,
I am coding MTOM Policy assertion mentioned in
http://blogs.cocoondev.org/dims/archives/003534.html
I coded a builder and the relevant model for the policy assertion. The
problem is where to put the implementation? To which project should
this belong to?
We can put this in "Axis2" or "
[
https://issues.apache.org/jira/browse/AXIS2-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462443
]
Deepal Jayasinghe commented on AXIS2-1937:
--
As I can see its a problem in OMSerializerUtil , changing serial
[
https://issues.apache.org/jira/browse/AXIS2-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462444
]
Deepal Jayasinghe commented on AXIS2-1937:
--
Oh , I forget to tell that , this issue is due to recent woodsto
[
https://issues.apache.org/jira/browse/AXIS2-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462446
]
Amila Chinthaka Suriarachchi commented on AXIS2-1931:
-
can you test with 1.1.1-RC. I generated th
Hi Dimuthu ;
If it is Axis2 specific then , it should go to Axis2 .o.w to Neethi
Thanks
Deepal
> Hi All,
>
> I am coding MTOM Policy assertion mentioned in
> http://blogs.cocoondev.org/dims/archives/003534.html
>
>
> I coded a builder and the relevant model for the policy assertion. The
> pro
Hi Deepal,
We can argue both ways.
This policy assertion will be mainly used by Axis2 to optimize binary
data. So it should go to Axis2.
It is also used for optimizing encrypted attachments. So should it go
to Neethi, because it is used both by Rampart and Axis2.
Thanks,
Dimuthu.
On 1/5/07, De
IMO If it doesn't depend on axis2 classes it should go into neethi. If
it does it should go in Axis2.
David
On 05/01/07, Dimuthu Leelaratne <[EMAIL PROTECTED]> wrote:
Hi Deepal,
We can argue both ways.
This policy assertion will be mainly used by Axis2 to optimize binary
data. So it should go
[
https://issues.apache.org/jira/browse/AXIS2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michele Mazzucco reopened AXIS2-1182:
-
> service name clash for callback operation
> -
>
>
fireAndForget and Thread.sleep
--
Key: AXIS2-1940
URL: https://issues.apache.org/jira/browse/AXIS2-1940
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: client-api
Environment: java
It deosn't depend on Axis2.
-Dimuthu
On 1/5/07, David Illsley <[EMAIL PROTECTED]> wrote:
IMO If it doesn't depend on axis2 classes it should go into neethi. If
it does it should go in Axis2.
David
On 05/01/07, Dimuthu Leelaratne <[EMAIL PROTECTED]> wrote:
> Hi Deepal,
> We can argue both ways
[
https://issues.apache.org/jira/browse/AXIS2-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurent CHARTIER updated AXIS2-1930:
Component/s: (was: wsdl)
codegen
> WSDL2Java - ParameterOrder
> --
AFAIK Neethi is the policy framework.. The concrete implementations
like these stay in the relevant locations.. Ex: sec policy resides in
Axis2 & will get moved with security..
IMHO this needs to go in to Axis2.
It is also used for optimizing encrypted attachments. So should it go
to Neethi, be
Then put it in neethi :) If we see a need later, then we can move it.
-- dims
On 1/5/07, Dimuthu Leelaratne <[EMAIL PROTECTED]> wrote:
It deosn't depend on Axis2.
-Dimuthu
On 1/5/07, David Illsley <[EMAIL PROTECTED]> wrote:
> IMO If it doesn't depend on axis2 classes it should go into neethi.
I guess, i defer to thilina's judgement on this one. plz scratch prev comment.
-- dims
On 1/5/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Then put it in neethi :) If we see a need later, then we can move it.
-- dims
On 1/5/07, Dimuthu Leelaratne <[EMAIL PROTECTED]> wrote:
> It deosn't dep
[
https://issues.apache.org/jira/browse/AXIS2-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe updated AXIS2-1939:
-
Priority: Blocker (was: Major)
marking as a blocker , and need to fix Axiom to overcome
Amila,
*TYPO ALERT* :) RoboustInOnly -> RobustInOnly
-- dims
On 1/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: amilas
Date: Fri Jan 5 01:49:11 2007
New Revision: 492953
URL: http://svn.apache.org/viewvc?view=rev&rev=492953
Log:
same suffix has used to inonly and roubust inonly
Please please please write javadoc!
---
Key: AXIS2-1941
URL: https://issues.apache.org/jira/browse/AXIS2-1941
Project: Apache Axis 2.0 (Axis2)
Issue Type: Wish
Components: databinding, documentation,
Memory-Usage increasing with every Service-execution
Key: AXIS2-1942
URL: https://issues.apache.org/jira/browse/AXIS2-1942
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Affects Vers
[
https://issues.apache.org/jira/browse/AXIS2-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Ernst updated AXIS2-1942:
--
Attachment: services.xml
HomeControlService.wsdl
HomeControlServ
[
https://issues.apache.org/jira/browse/AXIS2-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Ernst updated AXIS2-1942:
--
Attachment: HomeControlServiceMessageReceiverInOut.java
> Memory-Usage increasing with every Se
[
https://issues.apache.org/jira/browse/AXIS2-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Gunarathne updated AXIS2-1869:
--
Priority: Critical (was: Blocker)
reducing the priority..
> LICENSE and NOTICE files
Hi all,
We had to postpone the Axis2 1.1.1 release which was scheduled for
today due to a issue reported in the namespace serialization of
Axiom[1].. This relates to Axis2-1937 & axis2-1939.
New plan is to do a AXIOM release early next week, which will be
followed by the Axis2 1.1.1 release...
RPC Message receivers does not validate the request against the schema
Key: AXIS2-1943
URL: https://issues.apache.org/jira/browse/AXIS2-1943
Project: Apache Axis 2.0 (Axis2)
Hi Thilina ;
We need to start a vote in commons dev as well.
Thanks
Deepal
> Hi all,
> We had to postpone the Axis2 1.1.1 release which was scheduled for
> today due to a issue reported in the namespace serialization of
> Axiom[1].. This relates to Axis2-1937 & axis2-1939.
>
> New plan is to d
Modify OMXMLSecurity and Rampart to use the log mechanism available in axis2
Key: AXIS2-1944
URL: https://issues.apache.org/jira/browse/AXIS2-1944
Project: Apache Axis 2.0 (A
[
https://issues.apache.org/jira/browse/AXIS2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462474
]
Malinda Kaushalye Kapuruge commented on AXIS2-1944:
---
Please close this issue. Wrong project.
> Mod
[
https://issues.apache.org/jira/browse/AXIS2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruchith Udayanga Fernando closed AXIS2-1944.
Resolution: Invalid
> Modify OMXMLSecurity and Rampart to use the log mecha
Hi Brennan
Thank you.I could create the WSDL but when I try to
invoke the web service , I am getting the following
exception: We are using WebSphere 5.1 test server with
JRE 1.4.2 and axis2-1.1
The soap mesasge for response looks as follows:
(Unexpected subelement request)
--
http://schem
[
https://issues.apache.org/jira/browse/AXIS2-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Shiell updated AXIS2-1889:
Attachment: sample-j2se14.java
> WSDL with relative imports fails with FileNotFoundException.
> ---
[
https://issues.apache.org/jira/browse/AXIS2-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462507
]
James Shiell commented on AXIS2-1889:
-
I've attached a J2SE 1.4 file.
To regenerate the issue, use a pre-define
[
https://issues.apache.org/jira/browse/AXIS2-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Shiell updated AXIS2-1889:
Attachment: wsdl.zip
> WSDL with relative imports fails with FileNotFoundException.
> -
On Tue, 2007-01-02 at 15:28 -0800, Bill Nagy wrote:
> OK, here's my $0.02:
>
> (1)I would argue that reliable delivery of messages is an integral part
> of a web services stack and therefore deserves special treatment in the
> core where necessary so long as it does not adversely affect processing
[
https://issues.apache.org/jira/browse/AXIS2-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle reassigned AXIS2-1945:
-
Assignee: Rich Scheuerle
> JAX-WS NS->Package Conversion Error
>
JAX-WS NS->Package Conversion Error
---
Key: AXIS2-1945
URL: https://issues.apache.org/jira/browse/AXIS2-1945
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Reporter:
I'm not giving up, and I want to argue some more 8-].
>From a pure Axis context perspective, I agree (without having looked
through the code in detail) that your assertion about there not being
any private state is correct. From the perspective of the state as a
whole, I don't agree -- in our use
[
https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462593
]
Bjorn Townsend commented on AXIS2-1940:
---
Michele,
The example you're looking at (I assume it's
http://ws.apac
PackageSetBuilder throws NPE when class uses un-named package
-
Key: AXIS2-1946
URL: https://issues.apache.org/jira/browse/AXIS2-1946
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bu
[
https://issues.apache.org/jira/browse/AXIS2-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker updated AXIS2-1946:
-
Attachment: JIRA_1946_packagesetbuilder.txt
> PackageSetBuilder throws NPE when class uses un-nam
[
https://issues.apache.org/jira/browse/AXIS2-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker resolved AXIS2-1946.
--
Resolution: Fixed
JIRA AXIS2-1946 Commited.
> PackageSetBuilder throws NPE when class uses un-
[
https://issues.apache.org/jira/browse/AXIS2-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker closed AXIS2-1946.
> PackageSetBuilder throws NPE when class uses un-named package
> -
[
https://issues.apache.org/jira/browse/AXIS2-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462623
]
Harinee commented on AXIS2-744:
---
I am running into this exact same issue. It's been a while since I worked with
web ser
[
https://issues.apache.org/jira/browse/AXIS2-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harinee updated AXIS2-744:
--
Attachment: wirelessportal-httpexport-1.3-wsdl.tar.gz
> WSDL2Java error: src-resolve: type '[EMAIL
> PROTECTED]
[
https://issues.apache.org/jira/browse/AXIS2-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harinee updated AXIS2-744:
--
Affects Version/s: (was: 1.0)
1.1
> WSDL2Java error: src-resolve: type '[EMAIL
> PRO
org.apache.xmlbeans.XmlException: error: src-resolve: type '[EMAIL
PROTECTED]://com.czncorp.ibus/WirelessPortal' not found.
Key: AXIS2-1947
[
https://issues.apache.org/jira/browse/AXIS2-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harinee updated AXIS2-1947:
---
I meant to link to the other as a clone of AXIS2-744, not a blocker. I can't
seem to edit it now.
> org.apache
[
https://issues.apache.org/jira/browse/AXIS2-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harinee updated AXIS2-1947:
---
Attachment: wirelessportal-httpexport-1.3-wsdl.tar.gz
> org.apache.xmlbeans.XmlException: error: src-resolve:
[
https://issues.apache.org/jira/browse/AXIS2-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harinee updated AXIS2-1947:
---
I got past this issue with the suggestion given in AXIS2-744 - to have the
namespace the same in the service wsd
[
https://issues.apache.org/jira/browse/AXIS2-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas reassigned AXIS2-1917:
---
Assignee: David Illsley
David,
would you like to take this one? :)
-- dims
> quick
The major-minor version error is an easy one...you are running JRE 1.4 but
the jaxb-api jar is compiled with JSE 5. JAXB-RI (v.2) requires JSE 5, so
you are out of luck if you are trying to run on WebSphere 5.x, which doesn't
support JSE 5 (you'll need version 6.1 to do this...). If you stick with
50 matches
Mail list logo
