Hi Carlos,
Glad you like the archetype and my spring-boot-starter ☺
But be aware of changes to BlazeDS I just committed today … I’ll post the
changes in a new thread.
Chris
Am 17.02.17, 15:21 schrieb "carlos.rov...@gmail.com im Auftrag von Carlos
Rovira" <carlos.rov...@gmail.com im Auftrag von carlos.rov...@codeoscopic.com>:
Hi Chris, just report that Archetype is working good and is a breeze to
generate a basic java blazeds project with that. Very useful!
I can now concentrate in make some AMF work and see if I can get some
communication between FlexJS and BlazeDS :)
Thanks!
2017-02-17 10:14 GMT+01:00 Carlos Rovira <carlos.rov...@codeoscopic.com>:
> Great Chris!
>
> I'll try to take a look at this today as I get some times here and there.
>
> Thanks! :)
>
> Carlos
>
> 2017-02-17 10:03 GMT+01:00 Christofer Dutz <christofer.d...@c-ware.de>:
>
>> Hi guys …
>>
>> So, the archetype is done …
>>
>> Now all you must do to generate a new BlazeDS application is execute this
>> on the command line:
>>
>> mvn archetype:generate -DarchetypeGroupId=org.apache.flex.blazeds
>> -DarchetypeArtifactId=blazeds-spring-boot-example-archetype
>> -DarchetypeVersion=4.7.3-SNAPSHOT
>>
>> To run the application, you need to do this:
>>
>> mvn spring-boot:run
>>
>> Have fun … now I’m back to cleaning up ;-)
>>
>> Chris
>>
>>
>>
>> Am 17.02.17, 09:11 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>:
>>
>> Hi Carlos,
>>
>> The thing is that BlazeDS was in a strange state when it was donated
>> to Apache. It looked as if there was an Ant build, but the core was built
>> with maven.
>> I invested quite a lot of work into cleaning up the maven build but
>> outside of the parts Adobe initially built with maven were Ant builds I
>> couldn’t get to work and when I tried converting the surrounding parts to
>> Maven this required a lot of dependencies we didn’t have in any Maven
repo
>> I could find.
>>
>> The apps were a special case, but as I remember them they were based
>> on really really old versions of things and I didn’t see any good in
>> porting them. So we just left them in there for quite some time. None was
>> complaining about them not being built anymore or not being released
>> anymore so we discussed things here on the list and it was consensus to
>> remove the stuff that was no longer used … the apps were part of that.
>>
>> Now if you want to setup a BlazeDS Server as a quickstart, I
>> implemented the blazeds-spring-boot-starter, which makes it super-easy to
>> setup a BlazeDS application with Spring-Boot.
>>
>> I just noticed that things would be even easier, if I added an
>> archetype for that to BlazeDS … would that be ok for you? I started
working
>> on BlazeDS a few days ago and was planning on giving it a little code and
>> security polish … could just slip that in.
>>
>> Chris
>>
>>
>>
>> Am 16.02.17, 23:33 schrieb "carlos.rov...@gmail.com im Auftrag von
>> Carlos Rovira" <carlos.rov...@gmail.com im Auftrag von
>> carlosrov...@apache.org>:
>>
>> Hi,
>>
>> As I'm to start working on AMF library for FlexJS, I want to use
>> apache
>> flex blazeds version and build with maven.
>> I use develop branch, and could build without problems
>> But see that in master there's an "apps" folder with some war
>> examples. I
>> want to start from that in order to create examples that we could
>> share in
>> the future with ease if we use the ones in the blazeds git folder
>> and
>> people doesn't need to create additional things.
>>
>> But don't understand
>>
>> 1.- why that folder is not in develop and only in master?
>>
>> 2.- snapshot from develop is 4.7.3, is the recomended version?
>>
>> 3.- could I build one of the apps? should I build from master all
>> (blazeds
>> jars and examples) instead from develop? or maybe from a tag?
>>
>> thanks
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>>
>>
>>
>
>
> --
>
> Carlos Rovira
> Director General
> M: +34 607 22 60 05 <607%2022%2060%2005>
> http://www.codeoscopic.com
> http://www.avant2.es
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
>
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> comunicamos que sus datos forman parte de un fichero cuyo responsable es
> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la
> prestación del servicio o información solicitados, teniendo usted derecho
> de acceso, rectificación, cancelación y oposición de sus datos
dirigiéndose
> a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la
> documentación necesaria.
>
>
--
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.
