Re: [RESULT] Re: [VOTE] Release Apache Flex BlazeDS 4.7.3

2017-04-01 Thread Christofer Dutz 
Done … but strangely I only have ZIP this time … will look into this that the 
next release procudes the TAR again.

Chris

Am 01.04.17, 08:19 schrieb "Alex Harui" :

Hi Christofer,

Thanks for making it happen.  It would be nice to place the source on the
mirrors as well.  See:
https://dist.apache.org/repos/dist/release/flex/BlazeDS/

Thanks,
-Alex


On 3/31/17, 6:38 AM, "Christofer Dutz"  wrote:

>Ok … so the vote passes with
>
>4 +1 (Alex, Tom, Christofer, Josh)
>no 0
>no -1
>
>I’ll switch the repo to “release” and tomorrow the artifacts should be
>available at Maven-Central.
>
>Where should I copy the release zip to?
>
>Thanks (
>
>Chris
>
>Am 30.03.17, 21:12 schrieb "Alex Harui" :
>
>+1.  Good enough for now.
>
>-Alex
>
>On 3/30/17, 5:12 AM, "Christofer Dutz" 
>wrote:
>
>>+1 (Just noticed I didn’t actually vote ;-) )
>>
>>I agree with Tom … next release will have it fixed anyway.
>>
>>Chris
>>
>>
>>
>>Am 30.03.17, 13:45 schrieb "Tom Chiverton" :
>>
>>+1 - the headers is not a serious enough issue to hold up the
>release.
>>
>>Tom
>>
>>
>>On 27/03/17 22:13, Christofer Dutz wrote:
>>> Hi,
>>>
>>> This is Apache Flex BlazeDS 4.7.3 release candidate 1.
>>>
>>> RELEASE NOTES:
>>>
>>> Apache Flex BlazeDS 4.7.3 is an update to 4.7.2 which adds a
>new
>>> blazeds-spring-boot-starter module for easily setting up a
>BlazeDS
>>server with
>>> Spring Boot. It also provides Maven archetypes for easily
>creating
>>new spring-boot
>>> project that make use of BlazeDS. We also did quite a lot of
>>fine-tuning of the
>>> security default settings to make BlazeDS more secure.
>>>
>>> Starting with 4.7.3 BlazeDS Deserialization of XML is disabled
>>completely per default
>>> but can easily be enabled in your services-config.xml:
>>>
>>>  
>>>  >class="mx.messaging.channels.AMFChannel">
>>>  
>>url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf;
>>>
>>class="flex.messaging.endpoints.AMFEndpoint"/>
>>>  
>>>  
>>>  true
>>>  
>>>  
>>>  
>>>  
>>>
>>> Also we now enable the ClassDeserializationValidator per
>default to
>>only allow
>>> deserialization of whitelisted classes. BlazeDS internally
>comes
>>with the following
>>> whitelist:
>>>
>>>  flex.messaging.io.amf.ASObject
>>>  flex.messaging.io.amf.SerializedObject
>>>  flex.messaging.io.ArrayCollection
>>>  flex.messaging.io.ArrayList
>>>  flex.messaging.messages.AcknowledgeMessage
>>>  flex.messaging.messages.AcknowledgeMessageExt
>>>  flex.messaging.messages.AsyncMessage
>>>  flex.messaging.messages.AsyncMessageExt
>>>  flex.messaging.messages.CommandMessage
>>>  flex.messaging.messages.CommandMessageExt
>>>  flex.messaging.messages.ErrorMessage
>>>  flex.messaging.messages.HTTPMessage
>>>  flex.messaging.messages.RemotingMessage
>>>  flex.messaging.messages.SOAPMessage
>>>  java.lang.Boolean
>>>  java.lang.Byte
>>>  java.lang.Character
>>>  java.lang.Double
>>>  java.lang.Float
>>>  java.lang.Integer
>>>  java.lang.Long
>>>  java.lang.Object
>>>  java.lang.Short
>>>  java.lang.String
>>>  java.util.ArrayList
>>>  java.util.Date
>>>  java.util.HashMap
>>>  org.w3c.dom.Document
>>>
>>> If you need to deserialize any other classes, be sure to
>register
>>them in your
>>> services-config.xml:
>>>
>>>  
>>>  >class="flex.messaging.validators.ClassDeserializationValidator">
>>>  
>>>  
>>>  
>>>

Re: [FlexJS] MDL Help Needed

2017-04-01 Thread Peter Ent 
Thanks. I will try this as soon as I can. 

Peter 


> On Apr 1, 2017, at 1:54 PM, piotrz  wrote:
> 
> Peter,
> 
> I got it! :) After 3 hours of fight I was able to expose problem. I've
> prepared simple application where you can reproduce it [1]. 
> 
> In general for some reason compiler is not generating second span:
> 
> 
> - this span will be missing in HTML.
> 
> 
> If you launch even simpler application than my example [2] you will see in
> the HTML DOM that second span is missing:
> 
> 
>  
> 
> [1] 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2F1drv.ms%2Fu%2Fs!ApVpLyjpHDC2zQBWadDWCpbMMBKM=02%7C01%7C%7Ce4cd079979434e380a9d08d479283621%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63620989299044=%2BTzTxfZpu9sHw3x4gZfMliboJRM70Hubh9QA0tHxCBY%3D=0
> [2] 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F7ImM=02%7C01%7C%7Ce4cd079979434e380a9d08d479283621%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63620989309056=yo6gCdGzzUvYYy%2BcxBjgnhODWW7RhB44ijWLmaEgR7U%3D=0
> 
> Piotr
> 
> 
> 
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.247.n4.nabble.com%2FFlexJS-MDL-Help-Needed-tp60946p60950.html=02%7C01%7C%7Ce4cd079979434e380a9d08d479283621%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63620989309056=FDbFl1ZyQ25CZ1b1f%2BWqpms4RwUx0B9Q2lk1ry7y%2FAQ%3D=0
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] MDL Help Needed

2017-04-01 Thread piotrz 
Peter,

I got it! :) After 3 hours of fight I was able to expose problem. I've
prepared simple application where you can reproduce it [1]. 

In general for some reason compiler is not generating second span:


 - this span will be missing in HTML.


If you launch even simpler application than my example [2] you will see in
the HTML DOM that second span is missing:


 

[1] https://1drv.ms/u/s!ApVpLyjpHDC2zQBWadDWCpbMMBKM
[2] https://paste.apache.org/7ImM

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Help-Needed-tp60946p60950.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [RESULT] Re: [VOTE] Release Apache Flex BlazeDS 4.7.3

2017-04-01 Thread Alex Harui 
Hi Christofer,

Thanks for making it happen.  It would be nice to place the source on the
mirrors as well.  See:
https://dist.apache.org/repos/dist/release/flex/BlazeDS/

Thanks,
-Alex


On 3/31/17, 6:38 AM, "Christofer Dutz"  wrote:

>Ok … so the vote passes with
>
>4 +1 (Alex, Tom, Christofer, Josh)
>no 0
>no -1
>
>I’ll switch the repo to “release” and tomorrow the artifacts should be
>available at Maven-Central.
>
>Where should I copy the release zip to?
>
>Thanks (
>
>Chris
>
>Am 30.03.17, 21:12 schrieb "Alex Harui" :
>
>+1.  Good enough for now.
>
>-Alex
>
>On 3/30/17, 5:12 AM, "Christofer Dutz" 
>wrote:
>
>>+1 (Just noticed I didn’t actually vote ;-) )
>>
>>I agree with Tom … next release will have it fixed anyway.
>>
>>Chris
>>
>>
>>
>>Am 30.03.17, 13:45 schrieb "Tom Chiverton" :
>>
>>+1 - the headers is not a serious enough issue to hold up the
>release.
>>
>>Tom
>>
>>
>>On 27/03/17 22:13, Christofer Dutz wrote:
>>> Hi,
>>>
>>> This is Apache Flex BlazeDS 4.7.3 release candidate 1.
>>>
>>> RELEASE NOTES:
>>>
>>> Apache Flex BlazeDS 4.7.3 is an update to 4.7.2 which adds a
>new
>>> blazeds-spring-boot-starter module for easily setting up a
>BlazeDS
>>server with
>>> Spring Boot. It also provides Maven archetypes for easily
>creating
>>new spring-boot
>>> project that make use of BlazeDS. We also did quite a lot of
>>fine-tuning of the
>>> security default settings to make BlazeDS more secure.
>>>
>>> Starting with 4.7.3 BlazeDS Deserialization of XML is disabled
>>completely per default
>>> but can easily be enabled in your services-config.xml:
>>>
>>>  
>>>  >class="mx.messaging.channels.AMFChannel">
>>>  
>>url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf;
>>>
>>class="flex.messaging.endpoints.AMFEndpoint"/>
>>>  
>>>  
>>>  true
>>>  
>>>  
>>>  
>>>  
>>>
>>> Also we now enable the ClassDeserializationValidator per
>default to
>>only allow
>>> deserialization of whitelisted classes. BlazeDS internally
>comes
>>with the following
>>> whitelist:
>>>
>>>  flex.messaging.io.amf.ASObject
>>>  flex.messaging.io.amf.SerializedObject
>>>  flex.messaging.io.ArrayCollection
>>>  flex.messaging.io.ArrayList
>>>  flex.messaging.messages.AcknowledgeMessage
>>>  flex.messaging.messages.AcknowledgeMessageExt
>>>  flex.messaging.messages.AsyncMessage
>>>  flex.messaging.messages.AsyncMessageExt
>>>  flex.messaging.messages.CommandMessage
>>>  flex.messaging.messages.CommandMessageExt
>>>  flex.messaging.messages.ErrorMessage
>>>  flex.messaging.messages.HTTPMessage
>>>  flex.messaging.messages.RemotingMessage
>>>  flex.messaging.messages.SOAPMessage
>>>  java.lang.Boolean
>>>  java.lang.Byte
>>>  java.lang.Character
>>>  java.lang.Double
>>>  java.lang.Float
>>>  java.lang.Integer
>>>  java.lang.Long
>>>  java.lang.Object
>>>  java.lang.Short
>>>  java.lang.String
>>>  java.util.ArrayList
>>>  java.util.Date
>>>  java.util.HashMap
>>>  org.w3c.dom.Document
>>>
>>> If you need to deserialize any other classes, be sure to
>register
>>them in your
>>> services-config.xml:
>>>
>>>  
>>>  >class="flex.messaging.validators.ClassDeserializationValidator">
>>>  
>>>  
>>>  
>>>  
>>>  name="flex.messaging.io.amf.ASObject"/>
>>>  
>>>  
>>>  
>>>  
>>>
>>> (Beware, by manually providing a whitelist the default
>whitelist is
>>disabled)
>>>
>>> Known Issues
>>> _
>>> FLEX-34648 Memory Leak occurred in AsyncMessage when sending a
>lot
>>of messages
>>>
>>> 
>
>>-
>>-
>>-
>>>
>>> The release candidate can be found here:
>>> 
>
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freposito
>>r
>