RE: Flex BlazeDS Missing War and

2023-07-13 Thread spiros
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 


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 
> >
> >
> > 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: mxmlc target fails with jdk 1.8.0_291x64

2023-07-13 Thread Frost, Andrew
Hi

We've not got the Flex compiler set up for building/debugging .. but we'll 
probably need to do something here, we have another customer just report the 
same thing. It's a somewhat odd issue though, I wouldn't have thought any 
minor/build update to Java should affect things like this!

I've looked through the release notes, I can't see that the TLS changes (and 
removal of 1.0/1.1) would stop it from calling another jar file. But, I guess 
it depends how it makes the call, as there's also a change in ProcessBuilder 
quotes. I wonder if this is only an issue on Windows..!

Thanks for the pointers -> we'll take more of a look and see what we can find. 
Mostly I was just trying to see if anyone else had encountered this, whether it 
was a known issue/restriction etc.

Thanks

   Andrew


-Original Message-
From: Alex Harui  
Sent: Wednesday, July 12, 2023 7:55 AM
To: dev@flex.apache.org
Subject: [EXTERNAL] Re: mxmlc target fails with jdk 1.8.0_291x64

[EXTERNAL EMAIL]

Hi Andrew,

Can you repro?  If you can get it In the debugger there will probably be more 
info.

I think these are the release notes for JDK 1.8.0_291 
https://www.oracle.com/java/technologies/javase/8u291-relnotes.html

If I'm reading that right, lots of interesting changes in that release, like 
changes to TLS support, so maybe 291 can break something.

-Alex

On 7/10/23, 9:58 AM, "Frost, Andrew" mailto:andrew.fr...@harman.com.inva>LID> wrote:


EXTERNAL: Use caution when clicking on links or opening attachments.




Hi all


We have a customer with an odd issue and I wanted to check if anyone had found 
something similar already…


The odd part about this is that it works fine with Java 1.8.0 build 201 but 
fails with Java 1.8.0 build 291, both of them 64-bit.


The error is just when compiling an MXML file using Flex:




Loading configuration file C:\FlexSDK\frameworks\flex-config.xml


Error: null


We have managed to narrow it down to the use of CFF:


@font-face {


src: url("Roboto-Regular.ttf");


fontFamily: Roboto;


embedAsCFF: true;


}
Change the “true” to “false” and it compiles fine…




In terms of version:


>amxmlc.bat -version
Version 4.6.0 build 23201
Although they’ve also tried with 4.16.1, adding in the old jar files using “ant 
thirdparty-downloads” which apparently still works.


My thinking was that there’s an odd dependency upon the Adobe font embedding 
library, but I have never come across it working with one version of Java 1.8 
and failing with another version of 1.8…. (and of course anything later also 
fails so they can’t just update to Java 11 or 17..)




Does anyone have any hints or seen this sort of thing before?




Many thanks


Andrew