+1
On Wed, Dec 5, 2018 at 7:17 AM Freeman Fang wrote:
> +1
>
> Thanks!
> －
> Freeman(Yue) Fang
>
> Red Hat, Inc.
>
>
>
>
>
> On Dec 4, 2018, at 7:56 PM, Colm O hEigeartaigh
> wrote:
>
> This is a vote to release Apache XML Schema 2.2.4.
>
> Issues fixed:
>
+1
On Sun, Jul 21, 2019 at 10:39 PM Daniel Kulp wrote:
> +1.
>
> Dan
>
>
> On Jul 20, 2019, at 7:28 AM, Colm O hEigeartaigh
> wrote:
>
> This is a vote to release Apache WSS4J 2.2.4.
>
> Issues fixed:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310063=12345343
> SVN
+1
On Sat, Mar 14, 2020 at 12:27 AM Colm O hEigeartaigh
wrote:
> This is a vote to release Apache WSS4J 2.2.5.
>
> Issues fixed:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310063=12345960
> Git tag: https://github.com/apache/ws-wss4j/tree/wss4j-2.2.5
> Artifacts:
>
+1
On Wed, Sep 15, 2021 at 2:56 AM Daniel Kulp wrote:
> +1
>
> Dan
>
>
> On Sep 14, 2021, at 5:38 AM, Colm O hEigeartaigh
> wrote:
>
> This is a vote to release Apache WSS4J 2.2.7. It contains a few
> trivial code changes as well as updates to fix CVE issues in a few
> dependencies. This is
+1
On Wed, Sep 15, 2021 at 2:53 AM robertlazarski
wrote:
> +1
>
> On Tue, Sep 14, 2021 at 8:47 AM Daniel Kulp wrote:
>
>> This is a vote to release Neethi 3.2.0. Updates include:
>>
>>
>> 1) Support Java 7 has been dropped, but support for Java 17 has been
>> added. 3.1.0 now required Java8
+1
On Wed, Sep 15, 2021 at 3:02 AM robertlazarski
wrote:
> +1
>
> On Tue, Sep 14, 2021 at 8:49 AM Daniel Kulp wrote:
>
>> The primary change in this release is adding support for Java 17 and
>> dropping support for Java 7. It also contains a few bug fixes:
>>
>> [XMLSCHEMA-57] Fix namespace
+1
On Wed, Sep 15, 2021 at 2:49 AM Daniel Kulp wrote:
> +1
>
> Dan
>
>
> On Sep 14, 2021, at 5:19 AM, Colm O hEigeartaigh
> wrote:
>
> This is a vote to release Apache WSS4J 2.3.3. It contains a few
> trivial code changes as well as updates to fix CVE issues in a few
> dependencies.
>
>
ree with you, Colm. Thanks for the check.
>
> Colm.
>
> On Mon, May 30, 2022 at 7:22 AM Jim Ma wrote:
> >
> > Hi Colm,
> > I searched the javax namespace classes which are used in opensaml 4.2.0
> and I got this list :
> > https://paste.apache.org/lhks
Hi Colm,
I searched the javax namespace classes which are used in opensaml 4.2.0 and
I got this list :
https://paste.apache.org/lhks3
Now wss4j 3.0.0 jakart version already includes opensaml 4.2.0, is javax
imported class in opensaml a problem for wss4j ?
Thanks,
Jim
ks. I also want to review some
> outstanding CXF issues to see if there's anything that needs to go
> into WSS4J before the release.
>
> I'm hoping to get WSS4J 3.0.0 out in about a month or so.
>
> Colm.
>
> On Mon, Aug 29, 2022 at 3:25 AM Jim Ma wrote:
> >
> > Thanks
pository.apache.org/content/repositories/snapshots/org/apache/wss4j/wss4j-ws-security-dom/3.0.0-SNAPSHOT/>
>
> Keep me apprised !
> m~
> --
> *From:* Jim Ma
> *Sent:* Friday, August 19, 2022 7:45 AM
> *To:* dev@ws.apache.org
> *Subject:* WSS4j
Is it close to a WSS4j 3.0.0 release , and any plan date ? Are there some
issues left we need to address for this major release ?
Thanks,
Jim
+1
On Thu, Oct 6, 2022 at 4:39 PM Alessio Soldano wrote:
> +1
>
> Thanks!
>
> On Tue, Oct 4, 2022 at 2:33 PM Colm O hEigeartaigh
> wrote:
>
>> This is a vote to release Apache WSS4J 3.0.0. This is a new major
>> release which has transitioned to the jakarta namespace, and contains
>> new major
+1
On Wed, Jul 12, 2023 at 11:55 PM Colm O hEigeartaigh
wrote:
> This is a vote to release Apache WSS4J 3.0.1, 2.4.2, 2.3.4.
>
> 3.0.1:
>
> - Issues fixed:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310063=12352384
> - Git tag:
+1
Jim
On Thu, Feb 22, 2024 at 10:25 PM Colm O hEigeartaigh
wrote:
> This is a vote to release Apache WSS4J 3.0.3. It contains an update to
> use XML Security for Java 3.0.4 and functionality to support key
> agreement using ECDH-ES.
>
> Release notes:
>
Can anyone shed some light on this ?
On 12/8/06, jim ma [EMAIL PROTECTED] wrote:
Hi all ,
I think this is a bug maybe introduced by jakarta-httpcore-4.0-alpha2.
When enable the chunk mode for StringEntity , client will read 28 bytes each
time . Client will read many times when a large payload
-1024
---count -638
buffersize is 1024*2 , The output is :
---count -27
---count -1667
buffersize is 1024*3 ,output will be :
---count -32
---count -1662
Regards
Jim
On 12/12/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
On Tue, 2006-12-12 at 11:55 +0800, jim ma
Hi Oleg,
It's JDK's issue . I will modify my code to use Commons HttpClient.
Thanks
Jim
On 12/13/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
On Wed, 2006-12-13 at 16:31 +0800, jim ma wrote:
Oleg,
Thank you for your quick reply.
You can use following steps to reproduce this issue
Hi , all
Just tried woden and I have two qustions about it :
[1] Will Woden1.0 support parsing and validating WSDL 1.1 documents ?
[2] Does Woden intend to do the validation inculde ws-i basic profile conformance ?
Thanks
Jim
Hi all,
I just took a quick look at Woden M6's API . I can not find the api to parse
the wsdl11 directly to wsdl20 description . Will Woden provide a common api
to parse the wsdl11 and wsdl20 to description element?
Thanks
Jim
Jim Ma created WSS-435:
--
Summary: Add
Key: WSS-435
URL: https://issues.apache.org/jira/browse/WSS-435
Project: WSS4J
Issue Type: Bug
Reporter: Jim Ma
Assignee: Colm O
[
https://issues.apache.org/jira/browse/WSS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Ma closed WSS-435.
--
Resolution: Invalid
accidently create one issue, and I don't have permission to delete it.
Add
Jim Ma created WSS-553:
--
Summary: wsu:Expires and wsu:created doesn't use UTC time format
Key: WSS-553
URL: https://issues.apache.org/jira/browse/WSS-553
Project: WSS4J
Issue Type: Bug
[
https://issues.apache.org/jira/browse/WSS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Ma updated WSS-553:
---
Summary: and elements not use UTC time format
(was: wsu:Expires and wsu:created doesn't use UTC time format
[
https://issues.apache.org/jira/browse/WSS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740116#comment-14740116
]
Jim Ma commented on WSS-553:
PR for this issue: https://github.com/apache/wss4j/pull/2
> and elements not
Jim Ma created WSS-654:
--
Summary: WSSecurityUtil throws NPE when security manager is enabled
Key: WSS-654
URL: https://issues.apache.org/jira/browse/WSS-654
Project: WSS4J
Issue Type: Bug
[
https://issues.apache.org/jira/browse/WSS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925345#comment-16925345
]
Jim Ma commented on WSS-654:
[~coheigea] Please review the attached patch.
> WSSecurityUtil throws NPE w
[
https://issues.apache.org/jira/browse/WSS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Ma updated WSS-654:
---
Fix Version/s: (was: 2.2.5)
Affects Version/s: (was: 2.2.4)
> WSSecurityUtil throws NPE when secur
[
https://issues.apache.org/jira/browse/WSS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930515#comment-16930515
]
Jim Ma commented on WSS-654:
It looks this issue is already fixed by [~coheigea] in wss4j 2.2.4. Sorry
[
https://issues.apache.org/jira/browse/WSS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Ma closed WSS-654.
--
Resolution: Not A Problem
> WSSecurityUtil throws NPE when security manager is enab
Jim Ma created WSS-665:
--
Summary: Add cryptacular dependency and upgrade to 1.2.4 to fix
CVE-2020-7226
Key: WSS-665
URL: https://issues.apache.org/jira/browse/WSS-665
Project: WSS4J
Issue Type: Task
Jim Ma created WSS-696:
--
Summary: Upgrade ehcache to 3.10.0 with jakarta classfier
Key: WSS-696
URL: https://issues.apache.org/jira/browse/WSS-696
Project: WSS4J
Issue Type: Task
Components
32 matches
Mail list logo
