After my commits today to remove the proxy module and clean up some things, I
think we're pretty much ready to go for a new BlazeDS release. I don't have any
further time to work on it this month, but I can make it happen in February.
- Josh
On 2023/01/10 07:22:22 Yishay Weiss wrote:
> Tha
Just documenting some of my findings about the BlazeDS proxy module.
The HTTProxyService class is compiled into flex-messaging-proxy.jar. BlazeDS
may be configured to use HTTProxyService in services-config.xml, like this:
If flex-messaging-proxy.jar is missing, and an HTTPProxyService is
che.org>
> Sent: Tuesday, January 10, 2023 2:03 AM
> To: dev@flex.apache.org<mailto:dev@flex.apache.org>
> Subject: Re: BlazeDS release
>
> Okay, some updates on my progress with BlazeDS.
>
> - I made the necessary changes to remove the vulnerable xalan dependency.
>
and releasing the maven artifacts.
From: Josh Tynjala<mailto:joshtynj...@apache.org>
Sent: Tuesday, January 10, 2023 2:03 AM
To: dev@flex.apache.org<mailto:dev@flex.apache.org>
Subject: Re: BlazeDS release
Okay, some updates on my progress with BlazeDS.
- I made the necessary changes to remove th
Okay, some updates on my progress with BlazeDS.
- I made the necessary changes to remove the vulnerable xalan dependency.
- I looked at the proxy module issue, where we need to replace the obsolete
commons-httpclient 3.x with its successor, httpcomponents-httpclient 4.x. It
seems to be
Sounds good to me.
> On Jan 5, 2023, at 11:06 PM, Josh Tynjala wrote:
>
> I figured out the necessary the changes on my local computer, tests are
> passing, and it seems to be successfully exchanging messages with clients, so
> I'm ready to commit. As I mentioned, I just need to know the
I figured out the necessary the changes on my local computer, tests are
passing, and it seems to be successfully exchanging messages with clients, so
I'm ready to commit. As I mentioned, I just need to know the expected branch.
I'm leaning toward security-updates, but I'm not sure.
- Josh
On
I'd like to spend some time this month finishing up the recent BlazeDS
stuff so that we can get it released.
Can someone confirm that the changes listed here are still what should be
done? It looks straightforward enough.
https://lists.apache.org/thread/9h7th05wc57399jp7l7mj11c45nq8jbn
And
ever, this seems to be a pretty new vulnerability, as I wasn’t
> >>> getting it when I started the branch. So, I would advise to look, if a
> >>> newer version is available and simply switch to that. If you need help
> with
> >>> that … give me a ping. Should b
: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com]
Sent: Tuesday, August 30, 2022 9:57 AM
To: dev@flex.apache.org
Subject: Re: [EXTERNAL] BlazeDS release
Maybe there is some replacement for both of that ? What do you think ?
pt., 26 sie 2022 o 12:53 Piotr Zarzycki
napisał(a):
> Hi g
>>> getting it when I started the branch. So, I would advise to look, if a
>>> newer version is available and simply switch to that. If you need help with
>>> that … give me a ping. Should be a matter of 5 minutes.
>>>
>>> Chris
>>>
gt; From: Tom Chiverton
>> Date: Tuesday, 16 August 2022 at 12:20
>> To: dev@flex.apache.org , Brian Raymes <
>> brian.ray...@teotech.com>
>> Subject: Re: [EXTERNAL] BlazeDS release
>> The issue there is when processing malicious XSLT.
>>
>> We don'
ex.apache.org , Brian Raymes <
> brian.ray...@teotech.com>
> Subject: Re: [EXTERNAL] BlazeDS release
> The issue there is when processing malicious XSLT.
>
> We don't pass untrusted XSLT to it ?
>
> Tom
>
> On 15/08/2022 22:36, Brian Raymes wrote:
> > Seems lik
To: dev@flex.apache.org , Brian Raymes
Subject: Re: [EXTERNAL] BlazeDS release
The issue there is when processing malicious XSLT.
We don't pass untrusted XSLT to it ?
Tom
On 15/08/2022 22:36, Brian Raymes wrote:
> Seems like those dependencies need to be replaced due to vulnerabilit
-9339-86wc-4qgf
-Original Message-
From: Piotr Zarzycki
Sent: Sunday, August 14, 2022 3:26 AM
To: dev@flex.apache.org
Subject: [EXTERNAL] BlazeDS release
Hi All,
In this thread I will be reporting updates related to release of BlazeDS. I
looked into Chris's branch and I would like
: [EXTERNAL] BlazeDS release
Hi All,
In this thread I will be reporting updates related to release of BlazeDS. I
looked into Chris's branch and I would like to exclude Proxy module from
upcoming release. Please let me know in this thread whether you have anything
against it.
Meanwhile I have
Hi All,
In this thread I will be reporting updates related to release of BlazeDS. I
looked into Chris's branch and I would like to exclude Proxy module from
upcoming release. Please let me know in this thread whether you have
anything against it.
Meanwhile I have following error on the console
Hi Justin ... thanks for the kind reminder ... I'll hopefully whip up the mail
this evening.
Chris
-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Gesendet: Montag, 16. März 2015 04:51
An: dev@flex.apache.org
Betreff: Re: [RESULT] [VOTE] [BlazeDS] Release
-ware.de]
Gesendet: Dienstag, 17. März 2015 18:47
An: dev@flex.apache.org
Betreff: AW: [RESULT] [VOTE] [BlazeDS] Release of Apache BlazeDS 4.7.0 RC2
Ok ... announce message is out ...
Think our website now needs a little love :-)
- Latest releases (right at the bottom should now reference our release
Ok .. and I had to do it again as it had to be send from an @apache.org email
;-)
-Ursprüngliche Nachricht-
Von: Christofer Dutz [mailto:christofer.d...@c-ware.de]
Gesendet: Dienstag, 17. März 2015 18:47
An: dev@flex.apache.org
Betreff: AW: [RESULT] [VOTE] [BlazeDS] Release of Apache
the Website for years ... don't want to break things ;-)
Chrsi
-Ursprüngliche Nachricht-
Von: Christofer Dutz [mailto:christofer.d...@c-ware.de]
Gesendet: Dienstag, 17. März 2015 07:43
An: dev@flex.apache.org
Betreff: AW: [RESULT] [VOTE] [BlazeDS] Release of Apache BlazeDS 4.7.0 RC2
Hi
Hi,
- Publish the files to https://dist.apache.org/repos/dist/release/flex/ (via
SVN) [1]
This has been done and propagated. [1]
- Update web site with release info
- Mark this version as released and add a new version tag in JIRA.
And of course send out announcement email. Can anyone
Hi,
I'll set the staging repo to release right away. What else do I have to do
now?
- Publish the files to https://dist.apache.org/repos/dist/release/flex/ (via
SVN) [1]
- Update web site with release info
- Wait 24 hours (for mirrors to catchup) then make an official announcement
- Mark
please tell
me how to do the last? I never done that and would like to do it myself.
Chris
Von: Alex Harui aha...@adobe.com
Gesendet: Montag, 2. März 2015 22:11
An: dev@flex.apache.org
Betreff: Re: [VOTE] [BlazeDS] Release of Apache BlazeDS 4.7.0 RC2
+1
+1
Package
https://repository.apache.org/content/repositories/orgapacheflex-1005/org/a
pache/flex/blazeds/blazeds/4.7.0/blazeds-4.7.0-source-release.tar.gz
Java 1.7
OS: Mac OS X x86_64 10.9.5
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok:
No objections from my side.
Chris
Gesendet mit meinem HTC
- Reply message -
Von: Justin Mclean jus...@classsoftware.com
An: dev@flex.apache.org dev@flex.apache.org
Betreff: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1
Datum: Mo., Mär. 2, 2015 08:22
Hi,
If it’s making you
HI,
+1 (binding) everything checks out
I checked:
- signatures and hashes correct
- LICENCE and NOTICE correct
- all files have Apache header
- no binary files in release
- can compile from source
- all tests pass
Minor issues (not blockers/can be done next release):
- Signed by non apache
Hi,
- I tagged the release RC1 cause it was the RC1 and I remember having trouble
deleting and re-adding a tag. If it's not a problem to delete a tag, I'd be
glad to change this.
No issue with the tag in git, it's the fact that it part of the release that's
an issue. The pom.xml in the
...@classsoftware.com]
Gesendet: Sonntag, 1. März 2015 08:13
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1
Hi,
One thing I did noticed about the code is the large number of @author tags.
This is generally frowned on in Apache. [1][2] Should we remove them?
Thanks
-tools-api we also didnt append the apache ... what do the others
think?
Chris
-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Gesendet: Sonntag, 1. März 2015 11:09
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1
Hi,
Thinking about it again I think we don't need the apache in front of the
artifact as it's allready part of the groupId.
I was referring to the name of the of the source zip file. Having apache in the
name gives a little more legal protection, but it's not a requirement.
Justin
On 2/28/15, 11:12 PM, Justin Mclean jus...@classsoftware.com wrote:
Hi,
One thing I did noticed about the code is the large number of @author
tags. This is generally frowned on in Apache. [1][2] Should we remove
them?
If it’s making you itch, go ahead and scratch it.
-Alex
Hi,
If it’s making you itch, go ahead and scratch it.
Anyone else have any objections to removing them? If not and once I have time
I'll remove them.
Thanks,
Justin
Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Gesendet: Sonntag, 1. März 2015 15:20
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1
Hi,
Thinking about it again I think we don't need the apache in front of the
artifact as it's
I just deployed an RC2 ... will start a new thread.
Chris
-Ursprüngliche Nachricht-
Von: Justin Mclean [mailto:jus...@classsoftware.com]
Gesendet: Sonntag, 1. März 2015 07:47
An: dev@flex.apache.org
Betreff: Re: [VOTE] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1
Hi,
+0 binding
Hi guys,
As I won't have time to do so in the next few days, I decided to spin a new RC
today. I just staged the second RC for BlazeDS 4.7.0. It is available at:
https://repository.apache.org/content/repositories/orgapacheflex-1005/
This version is a parity release to Adobe BlazeDS
This is the new discussion thread for RC2 of BlazeDS
Chris
HI,
I taken a look and there's possibly an issue, while very minor, may require
another RC being made. :-(
The pom file containing a tag containing RC1. This is included in the release
artefact and can't be change without changing the hashes/resigning etc
tagblazeds-4.7.0.0-RC1/tag
Thanks,
Hi,
When reviewing I also noticed these two files:
./proxy/src/flex/messaging/services/http/httpclient/EasySSLProtocolSocketFactory.java
./proxy/src/flex/messaging/services/http/httpclient/EasyX509TrustManager.java
I believe both are form the Apache Jakarta project so there no issue re
Hi,
+0 binding for now (because pom issue - see discuss thread)
I checked:
- signatures and hashes correct
- LICENCE and NOTICE correct
- all files have Apache header
- no binary files in release
- can compile from source
- all tests pass
May be an issue with tag in the pom.xml. Should this
Hi,
One thing I did noticed about the code is the large number of @author tags.
This is generally frowned on in Apache. [1][2] Should we remove them?
Thanks,
Justin
1.
http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_09_22.txt
(read 7F)
2
@flex.apache.org
Betreff: Re: [DISCUSS] [BlazeDS] Release of Apache BlazeDS 4.7.0.0 RC1
Are there any quick and easy example projects to test it with ?
Tom
On 27/02/15 09:24, Christofer Dutz wrote:
Hi,
this is the discussion thread to the matching vote. Please place any
discussions here
Hi,
this is the discussion thread to the matching vote. Please place any
discussions here.
Chris
?Hi guys,
I just staged the first RC for BlazeDS 4.7.0.0. It is available at:
https://repository.apache.org/content/repositories/orgapacheflex-1004/
The source-zip artifact is available at
Are there any quick and easy example projects to test it with ?
Tom
On 27/02/15 09:24, Christofer Dutz wrote:
Hi,
this is the discussion thread to the matching vote. Please place any
discussions here.
Chris
__
This email
-INF directory, but that's about
all that would be different.
Chris
-Ursprüngliche Nachricht-
Von: Nicholas Kwiatkowski [mailto:nicho...@spoon.as]
Gesendet: Samstag, 13. Dezember 2014 17:24
An: dev@flex.apache.org
Betreff: Re: [BlazeDS] First Apache Flex BlazeDS Release: (was Re: AW
On 12/13/14, 4:31 AM, Christofer Dutz christofer.d...@c-ware.de wrote:
So if you guys haven't got any objections, I would try starting the
release process.
But I would initiate the Maven release and not use the Ant stuff.
No objections from me, and I don’t think it matters to me whether you
Shouldn't we make it as easy as possible for folks get BlazeDS, if we want
them to use it? If so, then it would sure help to have everything in one
zip, along with examples.
On Sat, Dec 13, 2014 at 11:31 AM, Alex Harui aha...@adobe.com wrote:
On 12/13/14, 4:31 AM, Christofer Dutz
Maybe we offer it via a Mavel release for those that want to build from
source, and offer a binary download. That should take care of both major
use cases, I think.
-Nick
On Sat, Dec 13, 2014 at 10:31 AM, Alex Harui aha...@adobe.com wrote:
On 12/13/14, 4:31 AM, Christofer Dutz
49 matches
Mail list logo
