RE: [EXTERNAL] BlazeDS release
Hi , This library used by 4 classes ( only the org.apache.xpath.CachedXPathAPI); 1. flex.messaging.config.ApacheXPathClientConfigurationParser.java (common). 2. flex.messaging.config.ApacheXPathServerConfigurationParser.java (core). 3. flex.messaging.io.amf.MessageGenerator.java (core-test) 4. flex.messaging.io.amfx.DeserializationConfirmation.java (core-test) The 1 and 2 classes add support to xml for java JRE 1.4 you can see the: flex.messaging.config.ServicesDependencies.java (common) line 219 -236 function static ConfigurationParser getConfigurationParser(String className) for first. And flex.messaging.config.FlexConfigurationManager.java (core) line 105-118 function private ConfigurationParser getConfigurationParser(ServletConfig servletConfig) for the classes 3 and 4 (test) : the class flex.messaging.config.XPathServerConfigurationParser.java (common) is a guide to modify the code My suggestion : -Remove support for JRE 1.4 -too old -delete classes 1,2 -modify classes 3,4 , Optionally modify classes :flex.messaging.config.ServicesDependencies.java and flex.messaging.config.FlexConfigurationManager.java Spiros -Original Message- From: 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 guys, > > Unfortunately both version of these plugins doesn't have newer versions. > The latest one are serializer-2.7.2and xalan-2.7.2 and we are using it. > Any suggestions? > > Thanks, > Piotr > > pon., 22 sie 2022 o 10:44 Piotr Zarzycki > napisał(a): > >> Hi Chris and All, >> >> I will try to upgrade dependencies myself this week. I will let you know >> here how it goes. >> >> Thanks, >> Piotr >> >> wt., 16 sie 2022 o 14:46 Christofer Dutz >> napisał(a): >> >>> Well … >>> >>> you might not, but a malicious attacker might. >>> I think the last few releases of BlazeDS, that I did in the past were >>> reacting to CVEs reported in the XML processing part of BlazeDS. Here, for >>> example, a malicious attacker could embed xml using xml-entities that >>> referenced protected resources on the server and the BlazeDS server just >>> resolved them exposing this protected information. >>> >>> However, I think I remember I turned off the xml processing of external >>> resources per default. I probably this problem would not apply in very many >>> cases. >>> >>> However, 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 be a matter of 5 minutes. >>> >>> Chris >>> >>> >>> 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'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 >>> vulnerabilities, as the Apache Xalan project has been retired: >>> > >>> > https://github.com/advisories/GHSA-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 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 during build - Anyone >>> know what that means ? >>> > >>> > One or more dependencies were identified with known vulnerabilities in >>> > flex-messaging-common: >>> > >>> > >>> > serializer-2.7.2.jar (pkg:maven/xalan/serializer@2.7.2, >>> > cpe:2.3:a:apache:xalan-java:2.7.2:*:*:*:*:*:*:*) : CVE-2022
RE: Flex BlazeDS Missing War and
Hello, I would like to ask if there is any interest in using BlazeDS combined with Lucee (www.lucee.org ) I have already made the equivalent gateway " and I can share the code and configuration scripts. spiros -Original Message- From: Josh Tynjala [mailto:joshtynj...@bowlerhat.dev] Sent: Wednesday, July 12, 2023 10:24 PM To: dev@flex.apache.org Subject: Re: Flex BlazeDS Missing War and Apache's version of BlazeDS doesn't offer an equivalent to Adobe's turnkey bundle. Currently, the closest thing is our "binary release", which includes the BlazeDS .jar files, but we don't bundle Tomcat or any samples in there at this time. If all goes well with my efforts to reintroduce updated samples, the next binary release should include a samples.war (and source code, of course) that can be dropped into Tomcat (but you'll need to download Tomcat separately; Tomcat won't be bundled). I actually found Adobe's old version of the BlazeDS turnkey bundle on the Internet Archive recently, and I mirrored it on my Github account, just in case anyone might want it. I included instructions for updating Tomcat and BlazeDS in the bundle. https://github.com/joshtynjala/blazeds-turnkey-archive https://github.com/joshtynjala/blazeds-turnkey-archive/releases/tag/v4.0.0.14931 -- Josh Tynjala Bowler Hat LLC <https://bowlerhat.dev> On Wed, Jul 12, 2023 at 11:45 AM Abhay Singh wrote: > i see, thanks for the clarification. > > I actually referred few URL which talks about "turnkey versions of blazeds > which contains ready to use version f Tomcat (version 6.0.14) in which the > the BlazeDS WAR file has already been deployed and configured along with a > variety sample applications.The turnkey allows you to get up and running > with BlazeDS in a matter of minutes." > > since the poc was on similar lines i was looking to use that turnkey zip > file and use the war file to get started. > > Hope it clarifies. > > On Wed, Jul 12, 2023 at 8:55 PM Josh Tynjala > wrote: > > > As I understand it, BlazeDS doesn't have its own .war file. I don't think > > it would make much sense, since BlazeDS isn't an application on its own. > > It's a library that you can use as part of building an application. In > > other words, you need to build your own .war that contains your custom > Java > > application logic, with the BlazeDS .jar files included as a dependency. > > > > I'm actually working on restoring the BlazeDS samples project that was > > included with the old Adobe version. It was donated to Apache with the > rest > > of BlazeDS, but no one seems to have kept it up to date. I happened to > find > > it in the repository history recently, and I've been working on adding > new > > Royale frontends to replace the original Flex/Flash frontends, and making > > sure everything can be built with Maven. This samples project will show > how > > to build a .war file that you can deploy to Tomcat. > > > > -- > > Josh Tynjala > > Bowler Hat LLC <https://bowlerhat.dev> > > > > > > On Wed, Jul 12, 2023 at 4:23 AM Abhay Singh > wrote: > > > > > Hello Team, > > > > > > While doing a POC for replacement of Coldfusion came across BlazeDS. > > > > > > Reason for change being newer version of coldfusion don't support AMF > > > anymore. > > > > > > BlazeDS would be a good choice as it supports push messages, hibernate > > etc. > > > > > > However , we are stuck with setting up BlazeDS with Tomcat as he is > > unable > > > to build war and set it up on tomcat. > > > > > > Referred Link: > > > > > > https://flex.apache.org/download-blazeds.html > > > > > > Furthe , also tried looking for the war files or turnkey version as > > > mentioned in below URL: > > > > > > https://lists.apache.org/list.html?dev@%3Cusers.flex%2eapache%2eorg%3E > > > > > > However, i am not able to find the older versions as well. > > > > > > > > > > > > Please suggest. > > > > > >
RE: Translation needed
for greek - πίσω -Original Message- From: Neil Madsen [mailto:li...@cranialinteractive.com] Sent: Thursday, October 23, 2014 4:52 PM To: dev@flex.apache.org Subject: Translation needed Could I get people that know the translations to take a look at what I have and let me know if it's correct or not. It's for the word 'BACK'. If you could just post with the 'proper' translation or if there's a different word for a particular language. Here's what I have. french - arrière / retour spanish - espalda / retroceder / retroceso / anterior polish - wstecz greek - πίσω / ΕΠΙΣΤΡΟΦΗ korean - 다시 nederlands - terug deutsch - zurück portuguese - de volta / retorno / avesso zh_CN - 后面 zh_TW - 后面 Neil
[jira] [Commented] (FLEX-33427) Missing translation for postcode components
[ https://issues.apache.org/jira/browse/FLEX-33427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606202#comment-13606202 ] spiros aggelopoulos commented on FLEX-33427: greek or el_GR translation invalidCharPostcodeError=Ο ταχυδρομικός κώδικας περιέχει μη έγκυρους χαρακτήρες. wrongLengthPostcodeError=Ο ταχυδρομικός κώδικας έχει λανθασμένο μήκος. wrongFormatPostcodeError=Ο ταχυδρομικός κώδικας έχει λάθος μορφή.. incorrectFormatPostcodeError=Η συμβολοσειρά μορφοποίησης ταχυδρομικού κώδικα είναι λάθος. > Missing translation for postcode components > --- > > Key: FLEX-33427 > URL: https://issues.apache.org/jira/browse/FLEX-33427 > Project: Apache Flex > Issue Type: Bug >Affects Versions: Apache Flex 4.9.0 >Reporter: Justin Mclean >Priority: Trivial > > Missing translation of error messages for the postcode componets. > In English they are: > invalidCharPostcodeError=The postcode contains invalid characters. > wrongLengthPostcodeError=The postcode is the wrong length. > wrongFormatPostcodeError=The postcode is the wrong format. > incorrectFormatPostcodeError=The postcode format string is incorrect. > Can someone provide translation for this in the following languages: > da_DK - Danish > el_GR - Greek > ko_KR - Korean > nb_NO - Norwegian > sw_SE - Swedish > zh_CN - Chinese > zh_TW - Chinese > Done: > de_DE - German > pt_PT - Portuguese (Portugal) > pt_BR - Portuguese (Brazil) > ja_JP - Japanese > ru_RU - Russian > fi_FL - Finnish > nl_NL - Dutch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
