Apache Rampart team is pleased to announce the 1.5 release of Apache Rampart
module.
Apache Rampart is the the security module of Axis2 which provides
implementations of the WS-Sec* specifications for Apache Axis2. Apache
Rampart 1.5 release is compatible with Axis2 1.5 / 1.5.1 releases. Please
r
Hi Mark,
I don't think the packs will go through any or significant changes.
And I called the vote today [1] and if everything goes well, we will be able
to release it after 3 days. And this is about the voting process [2], if
want to know about it.
thanks,
Nandana
[1] - http://markmail.o
Hi Mark,
I temporary uploaded the files [1], but I still have to run all the
samples and do the final checks. I will call the vote as soon as these
finals checks are done.
thanks,
Nandana
[1] - http://people.apache.org/~nandana/rampart-1.5/dist/
On Mon, Jan 4, 2010 at 12:25 PM, macima wrote
Hi Aihua,
I am planning to call the vote for Rampart 1.5 around 26th
of December. If everything goes well, it will be released 3 days after
that.
regards,
Nandana
On Wed, Dec 23, 2009 at 3:41 AM, Su AiHua wrote:
>
> All:
>
> Anyone know the release plan of Apache Rampart 1.5?
> I use Axis
Hi Siva,
According to your error, it seems that Rampart can't find the key for
the alias you defined in Rampart configuration. It seems you are using
parameter based security, can you share the outFlowSecurity parameter of
your client.
regards,
Nandana
On Tue, Nov 24, 2009 at 8:23 AM, Siva
Hi Dave,
Rampart "org.apache.rampart:rampart-integration" module has a dependency
to "org.apache.axis2:axis2-transport-tcp" module from commons transport and
we are waiting for transports 1.0 release [1] which will happen soon. I will
call the vote as soon as transports 1.0 is out.
thanks,
Nan
[
https://issues.apache.org/jira/browse/AXIS2-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-4054.
---
Resolution: Fixed
Impl and test cases are committed in the trunk
Hi Siva,
This policy [1] will suit you requirements. This is one of the
policies we used for Microsoft interops. But to modify this policy to suit
your exact requirements, you need to provide some more information.
1.) Does both client and the server have their own public-private key pairs
Hi Glen
Nandana/all, can you check what I did in Rampart and let me know if you
> foresee any problems with it? I'm going to respin Axis2 1.5.1 with this
> and
> one other fix, and we should respin Rampart 1.5 as well.
>
+1 for re-spining both Axis2 1.5.1 and Rampart 1.5. I checked the change in
+1
regards,
Nandana
On Wed, Oct 7, 2009 at 5:17 PM, Amila Suriarachchi <
amilasuriarach...@gmail.com> wrote:
> +1, for release. lets finish with 1.5 :)
>
> Regarding your change,
> I think same thing can be done with the existing code in the trunk or
> earlier code in the branch by setting a fo
Hi Eran,
Thanks for pointing out. I fixed the stuff mentioned in the mail. I will
go through the two web sites again to see whether I have missed anything.
On Thu, Sep 3, 2009 at 6:20 PM, Eran Chinthaka wrote:.
> 1. Almost all the links within Axis2 web site to rampart is dead. For
> example,
Hi All,
Apache Rampart 1.5 (Rampart version for Axis2 1.5) Release Candidate is
available here.
http://people.apache.org/~nandana/rampart-1.5/RC1/dist/
And the M2 repository can be found here.
http://people.apache.org/~nandana/rampart-1.5/RC1/m2_repo/
Please test and report any issues you m
have option) other than commenting out the mentioned
> portion of module.xml?
> Chinmoy
>
>
>
> On Sat, Aug 1, 2009 at 8:19 AM, Nandana Mihindukulasooriya <
> nandana@gmail.com> wrote:
>
>> Hi Chinmoy,
>> If you comment out this part, the out going F
Hi Chinmoy,
If you comment out this part, the out going Fault messages will not
be secured. Segment of the module.xml you have attached is the one which
places Rampart handlers in the Out Fault Flow. It will not effect the normal
flow. I didn't see any active development in parameter based
On Thu, Jul 23, 2009 at 10:19 PM, Dennis Sosnoski wrote:
> Glen Daniels wrote:
>
>> Hi Dennis:
>>
>> Dennis Sosnoski wrote:
>>
>>
>>> Whether officially led by WSO2 or not, certainly most of the direction
>>> of the project has come from people associated with WSO2 and/or the Sri
>>> Lanka univer
+1 for Charith
thanks,
Nandana
On Mon, Jul 20, 2009 at 3:43 PM, Amila Suriarachchi <
amilasuriarach...@gmail.com> wrote:
> hi,
>
> Charith is currently active in SMS transport module for ws commons
> transport and he has done a lot of
> contributions for both Axis2 and ws commons project in add
; exact security header that I need to inject in SOAP messages so as the
> authentication succeeds.
>
> If any of you have any sample implementation or some pointers related to
> this issue, please do let me know.
>
>
>
> Thanks to all in advance for their help.
>
>
>
&
to this in the past, but I assumed
> > it'd been corrected. I don't see anything in Jira that looks relevant.
> > Is this a known issue?
> >
> > - Dennis
> >
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
> http://deepal.org
>
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
+1
Thanks,
Nandana
On Sun, May 17, 2009 at 10:16 PM, Glen Daniels wrote:
> Hi Axis Developers:
>
> The 1.5 release candidate has been stable for a couple of weeks now, and
> thus
> I'd like to kick off a VOTE to officially release 1.5. The usual 72 hour
> window applies.
>
> You can find the di
Hi Devs,
I need to need to set some implementation specific properties which
should be available in both outbound message and inbound message. These
properties should be should be available for Axis2 handlers in both out path
and in path. I tried setting the property in the RequestContext and
> Turns out there were a few other issues with the 1.5 RC, so we're going
>> to do
>> > another one anyway. As such, please do go ahead and apply your fixes to
>> the
>> > branch if you're confident they're solid. I was hoping to roll out
>> an
First build the following modules and then try to build at the root level.
modules/tool/axis2-mar-maven-plugin
modules/tool/axis2-aar-maven-plugin
thanks,
Nandana
On Tue, Apr 21, 2009 at 11:50 AM, Dennis Sosnoski wrote:
> I'm trying to build from the 1.5 branch ('mvn clean install'), and
> con
Hi Dobri,
Sorry I was on vacation, just noticed the mail. It seems we have some
improvements in the trunk which are not there in the 1.5 branch. I created
an issue and attached the patch that is needed to bring those improvements
to Axis2 1.5 branch.But as this is the last minute change, I thi
[
https://issues.apache.org/jira/browse/AXIS2-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya updated AXIS2-4313:
--
Attachment: MTOMPolicy.patch
The changes required to Axis2 1.5 branch
)
Issue Type: Improvement
Components: mtompolicy
Environment: Axis2 1.5 RC
Reporter: Nandana Mihindukulasooriya
Assignee: Glen Daniels
Fix For: 1.5
Some of the improvements done on the Axis2 trunk after branching are not
merged to Axis2 1.5
Hi Dennis,
Rampart SNAPSHOTs can be downloaded from here for testing.
http://builder.wso2.org/browse/RAMPART-NIGHTLY/latest/artifact
thanks,
Nandana
On Fri, Mar 13, 2009 at 8:04 PM, Nandana Mihindukulasooriya <
nandana@gmail.com> wrote:
> I can host a build from the trunk
I can host a build from the trunk which can be used for testing with Axis2
1.5 but it won't be a RC. I am planning to work on some issues in Rampart
but they are not that affected by changes in Axis2. So policy / dispatching
related issues, we can test that build against Axis2 1.5. I will host a
bu
[
https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681628#action_12681628
]
Nandana Mihindukulasooriya commented on AXIS2-4233:
---
Hi Al
Big +1
thanks,
nandana
On 2/10/09, Amila Suriarachchi wrote:
> hi all,
>
> Dobri Kitipov has been active in the axis2 dev[1] and rampart dev [2] recent
> time
> and he has submit patches for various issues.
>
> So I would like to propose him as a committer and here is my +1.
>
> thanks,
> Amila.
[
https://issues.apache.org/jira/browse/AXIS2-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670359#action_12670359
]
Nandana Mihindukulasooriya commented on AXIS2-3300:
---
Hi C
[
https://issues.apache.org/jira/browse/AXIS2-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-4220.
---
Resolution: Fixed
Fix Version/s: nightly
Committed in
Did you copy rampart and all the dependency jars to lib directory ?
thanks,
nandana
On Tue, Feb 3, 2009 at 4:26 AM, Iyengar, Kumar wrote:
>
>
> Hi all,
>
>
>
> I was trying to setup UsernameToken with Axis2 1.4.1 and Rampart 1.4 and
> get the following error below. I checked and found the follow
[
https://issues.apache.org/jira/browse/AXIS2-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya updated AXIS2-3412:
--
Attachment: AXIS2-3412.patch
Tested this with Axis2 1.4.1 and worked
Hi Jose,
Can u please try building the axis2-mar-maven-plugin module under
/modules/tool/axis2-mar-maven-plugin first and then try building at
the root level. There seems to have a cyclic dependency. Once the
artifacts are in the maven repo this problem will solved.
thanks,
nandana
On Thu, D
[
https://issues.apache.org/jira/browse/AXIS2-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya updated AXIS2-4179:
--
Attachment: AXIS2-4179.patch
Proposed Solution :
Use a
Reporter: Nandana Mihindukulasooriya
Assignee: Nandana Mihindukulasooriya
Each AxisDescription instance (AxisService, AxisOperation, etc.) has a
"PolicySubject" field containing the policy components (policy, policy
reference) attached at that subject. The problem is
[
https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-4114.
---
Resolution: Fixed
> Problem to retrieve the effective policy f
[
https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655239#action_12655239
]
Nandana Mihindukulasooriya commented on AXIS2-4114:
---
Hi Det
[
https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654760#action_12654760
]
Nandana Mihindukulasooriya commented on AXIS2-4114:
---
Hi Det
[
https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reopened AXIS2-4114:
---
NPE is thrown in the case of axisOperation is null
> Problem
> both places
>
>
> I suppose that this is a bug.
>
> Regards, Dobri
>
>
>
>
>
>
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
che.ws.axis-cvs
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
Mary,
Yes, I applied the patch [1] and resolved the issue and it is in the
trunk. It seems we need to include some null checks in to the problematic
operation.
thanks,
nandana
[1] -
http://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.ext.subversion:subversion-commit
Hi Nafran,
It seems that web app copies the modules (addressing, etc. ) from
the target folder of axis2 modules. Do a maven build at the root level and
those modules will be available.
thanks,
nandana
On Mon, Nov 17, 2008 at 6:25 PM, nafran shiraz <[EMAIL PROTECTED]> wrote:
> Hi,I down
[
https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-4114.
---
Resolution: Fixed
> Problem to retrieve the effective policy f
Hi Detelin,
applyPolicy(..) method is used in code generated stubs. If you
look at the constructor you can see _service.applyPolicy() which recursively
calls the child descriptions. So automatic module engagement works in the
client side as mentioned here [1]. But doesn't see this being
[
https://issues.apache.org/jira/browse/AXIS2-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya closed AXIS2-4105.
-
Resolution: Fixed
> Typos in site documentat
[
https://issues.apache.org/jira/browse/AXIS2-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645142#action_12645142
]
nandana.cse edited comment on AXIS2-4104 at 11/4/08 7:25 PM:
[
https://issues.apache.org/jira/browse/AXIS2-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya closed AXIS2-4104.
-
Resolution: Fixed
This fixed in the trunk. Thanks Luis for pointing out
[
https://issues.apache.org/jira/browse/AXIS2-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-4114:
-
Assignee: Nandana Mihindukulasooriya
> Problem to retrieve
[
https://issues.apache.org/jira/browse/AXIS2-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644239#action_12644239
]
Nandana Mihindukulasooriya commented on AXIS2-4109:
---
Yes, the
ivePolicy() returns null and I can not get the Policy I
> need.
> I saw that I need something like the AxisDescription.getApplicablePolicy in
> order to locate the real Policy of a given PolicyReference.
> Is that the correct behavior?
>
> Can you please give me some more information how should I get the policy
> attached at the binding level in my handler?
>
>
> Thank you in advance,
> Dobri
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
Axis2)
Issue Type: Bug
Reporter: Nandana Mihindukulasooriya
JSONOMBuidler doesn't set the namespace of the top element correctly and the
serialization fails due to this reason.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to
[
https://issues.apache.org/jira/browse/AXIS2-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641748#action_12641748
]
Nandana Mihindukulasooriya commented on AXIS2-3784:
---
Hi B
[
https://issues.apache.org/jira/browse/AXIS2-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-4066.
---
Resolution: Fixed
Applied the patch in revision 706902.
> Add
[
https://issues.apache.org/jira/browse/AXIS2-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-4048.
---
Resolution: Fixed
Applied the patch in revision 706902, thanks
[
https://issues.apache.org/jira/browse/AXIS2-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641434#action_12641434
]
Nandana Mihindukulasooriya commented on AXIS2-3784:
---
Boris,
Dims,
My bad and thank for pointing out. Fixed.
thanks,
nandana
On Mon, Oct 20, 2008 at 8:34 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nandana,
>
> Please review before commit :)
>
> "import com.sun.corba.se.impl.javax.rmi.CORBA.Uti
Hi Shawn,
I think performance graphs of Rampart2 was quite good compared to
Rampart/WSS4J/Xmlsec and IFAIK, all the four scenarios you tested are
possible with Rampart2 at the moment and the configuration is almost
similar to Apache Rampart. One thing you can do is to run the benchmark
ag
[
https://issues.apache.org/jira/browse/AXIS2-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-4068.
---
Resolution: Fixed
Fixed this in the JIRA.
> 1.4.1 is listed un
[
https://issues.apache.org/jira/browse/AXIS2-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-4068:
-
Assignee: Nandana Mihindukulasooriya
> 1.4.1 is listed un
[
https://issues.apache.org/jira/browse/AXIS2-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya updated AXIS2-4066:
--
Attachment: AXIS2-4066.patch
The patch to support WS
: Nandana Mihindukulasooriya
Assignee: Nandana Mihindukulasooriya
WS-AddressingAndIdentity[1] specification allows us to WS-Addressing's endpoint
reference by providing identity information about the endpoint. This mechanism
can be used to provide the public key information of the se
[
https://issues.apache.org/jira/browse/AXIS2-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636340#action_12636340
]
Nandana Mihindukulasooriya commented on AXIS2-4054:
---
Commits relate
: Improvement
Components: mtompolicy
Reporter: Nandana Mihindukulasooriya
Assignee: Nandana Mihindukulasooriya
MTOM Serialization Policy Assertion 1.1
(http://www.w3.org/TR/soap12-mtom-policy/) is not supported in Apache Axis2.
--
This message is automatically
[
https://issues.apache.org/jira/browse/AXIS2-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-4048:
-
Assignee: Nandana Mihindukulasooriya
> AxisService2WSD
ze of the binary when MTOM
>>>>> to
>>>>> be activated etc.
>>>>> I want to ask and if there are any plans to support the WS-MTOMPolicy.
>>>>> Is there any willing/steps into the community to support this in the near
>>>>> future.
>>>>>
>>>>>
>>>>> Regards, Dobri
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Thilina Gunarathne - http://thilinag.blogspot.com
>>>
>>> <http://www.wso2.org>
>>
>
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
[
https://issues.apache.org/jira/browse/AXIS2-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-4046.
---
Resolution: Fixed
Fixed the MTOMAssertion builder and added a test
: Bug
Components: mtompolicy
Reporter: Nandana Mihindukulasooriya
Assignee: Nandana Mihindukulasooriya
MTOMAssertionBuilder doesn't parse wsp:Optional attribute
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to
d Karma in the WS project to help continue this work
>>
>> asankha
>>
>>
>>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
nableMTOM=true. For example it will be
>>> nice to specify a threshold that defines the size of the binary when MTOM to
>>> be activated etc.
>>> I want to ask and if there are any plans to support the WS-MTOMPolicy. Is
>>> there any willing/steps into the community
hot-builds-tp19492383p19492383.html
> Sent from the Axis - Dev mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
[
https://issues.apache.org/jira/browse/AXIS2-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628696#action_12628696
]
Nandana Mihindukulasooriya commented on AXIS2-3784:
---
Hi Juan,
[
https://issues.apache.org/jira/browse/AXIS2-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628640#action_12628640
]
Nandana Mihindukulasooriya commented on AXIS2-3784:
---
Juan,
Nop
[
https://issues.apache.org/jira/browse/AXIS2-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627757#action_12627757
]
Nandana Mihindukulasooriya commented on AXIS2-3999:
---
Hi Th
[
https://issues.apache.org/jira/browse/AXIS2-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627703#action_12627703
]
Nandana Mihindukulasooriya commented on AXIS2-3999:
---
Hi Th
[
https://issues.apache.org/jira/browse/AXIS2-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627690#action_12627690
]
Nandana Mihindukulasooriya commented on AXIS2-3996:
---
Hi Th
[
https://issues.apache.org/jira/browse/AXIS2-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-3968.
---
Resolution: Fixed
Resolving as this is fixed.
> Fails to bu
[
https://issues.apache.org/jira/browse/AXIS2-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-3973.
---
Resolution: Fixed
Axis2 1.4.1 was released on August 25 2008 and ADB
[
https://issues.apache.org/jira/browse/AXIS2-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627679#action_12627679
]
Nandana Mihindukulasooriya commented on AXIS2-3997:
---
Hi Thomas,
Hi Devs,
Updated the site to point to archives. Now do we have to delete
previous releases from "/www/www.apache.org/dist/ws/axis2" ?
thanks,
nandana
On Wed, Aug 27, 2008 at 9:18 PM, Eran Chinthaka <[EMAIL PROTECTED]>wrote:
> Ok, sorry I didn't know that. I can remember me copying that e
[
https://issues.apache.org/jira/browse/AXIS2-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-3997:
-
Assignee: Nandana Mihindukulasooriya
> Generic Error in
[
https://issues.apache.org/jira/browse/AXIS2-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-3996:
-
Assignee: Nandana Mihindukulasooriya
> WS-Security/Rampart: M
[
https://issues.apache.org/jira/browse/AXIS2-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-3995:
-
Assignee: Nandana Mihindukulasooriya
> AXIOM-based re-generat
[
https://issues.apache.org/jira/browse/AXIS2-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-3999:
-
Assignee: Nandana Mihindukulasooriya
> InvalidSecurity (us
[
https://issues.apache.org/jira/browse/AXIS2-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-4000:
-
Assignee: Nandana Mihindukulasooriya
> Error in extract
[
https://issues.apache.org/jira/browse/AXIS2-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627373#action_12627373
]
Nandana Mihindukulasooriya commented on AXIS2-3989:
---
Hi Th
Hi Deepal,
Why haven't you archived previous releases before Axis2 1.1.1 release.
> Hmm ,as I remember correct archiving is automatically happen and you do
> not need to do anything. But one thing we should do is when we do a
> release we need to update the web site correctly. As you have mentione
.
>> http://blogs.deepal.org/
>>
>>
>> -----
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> With Mettha,
> Eran Chinthaka
>
>
> Health is the greatest gift; contentment is the greatest wealth; trusting
> is the best relationship; nirvana is the highest joy. - Dhammapada
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
> http://people.apache.org/~samisa/ <http://people.apache.org/%7Esamisa/>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Axis2 team is proud to announce the release of Apache Axis2 version
1.4.1. Apache Axis2 1.4.1 fixes a security vulnerability present in
Apache Axis2 1.4 policy processing.
Downloads are available at:
http://ws.apache.org/axis2/download.cgi
The Maven2
[
https://issues.apache.org/jira/browse/AXIS2-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-3797:
-
Assignee: Amila Chinthaka Suriarachchi (was: Deepal Jayasinghe
[
https://issues.apache.org/jira/browse/AXIS2-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625212#action_12625212
]
Nandana Mihindukulasooriya commented on AXIS2-3337:
---
I fixed the i
[
https://issues.apache.org/jira/browse/AXIS2-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya resolved AXIS2-3974.
---
Resolution: Fixed
Applied Detelin's patch with some minor chang
Hi,
Thanks for the feedback. Charitha checked the source distribution and he
came across these two issues which are reported in the JIRA [1]. We solved
the second issue and as we have a work around [2] for the first issue , we
didn't fix it in 1.4.1. We decided to use the 1_4 branch instead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am calling fresh a vote again for Axis2 1.4.1 and only the source
distribution is changed. Only change is removing some binaries that were
accidentally included.
New source distribution can be found here. Please review.
http://people.apache.org/~nan
B in 1.4) due to the inclusion of
> documentation..
>
> thanks,
> Thilina
> [1]
> http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.1/release_artifacts
>
>
> On Wed, Aug 20, 2008 at 4:46 AM, Michele Mazzucco <
> [EMAIL PROTECTED]> wrote:
>
>> +1 for me.
>
MB in 1.4) due to the inclusion of
>>> documentation..
>>>
>>> thanks,
>>> Thilina
>>> [1]
>>> http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.1/release_artifacts
>>>
>>>
>>> On Wed, Aug 20, 2008 at 4:46 AM
[
https://issues.apache.org/jira/browse/AXIS2-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandana Mihindukulasooriya reassigned AXIS2-3825:
-
Assignee: Amila Chinthaka Suriarachchi
> Object's prop
t to be increased quite a bit in the
>> 1.4
>> > release too (6.9 MB in 1.3, 12 MB in 1.4) due to the inclusion of
>> > documentation..
>> >
>> > thanks,
>> > Thilina
>> > [1]
>> http://wiki.apache.org/ws/FrontPage/Axis2/rele
1 - 100 of 226 matches
Mail list logo