Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

[Carlos Rovira]

Hi Joe,

I'll leaving for a trip tomorrow and will come in a few days, and as much
I'm trying to finish a new jewel component before leaving (If I solve my
current problems in time! :)). Please try this weekend to call a simple
method sending a String and receiving a server string and report what you
get. I'll help you next week as I return and can invest time in it. In the
meanwhile, hope you could continue investigating what can be the issue, so
we can isolate the possible causes.

thanks!

Carlos



2018-08-10 17:07 GMT+02:00 JoeBoxer :

> Hello Carlos.
>
> The destinations for WebORB are defined in a different config file.  I'll
> upload that file for you too see.  I use the GenericDestination because its
> a wild card and doesn't require me to specify any namespaces.
>
> remoting-config.xml
>  remoting-config.xml>
>
>
> 
> *
> 
> 
>
> I'll take some time to test various settings in the remoting-config file
> and
> see if i get a different response.
>
> The initRemoting click event does call the following code
> protected function initRemoting():void
> {
>  remotingService.send("GetCountryList",[]);
>
> }
>
> Its a simple request that returns an array.  From what i can tell in the
> WebORB logs is that the request coming in from RemoteObject or
> SimpleRemoteObject is not being parsed correctly.  It doesn't matter what i
> put in for the source, destination properties it still results in...
>
> PM:cannot parse request. possible reasons: malformed request or protocol
> formatter is not registered
>
> Thank you for your continued attention with this issue.
>
> Regards
>
>
>
> --
> Sent from: http://apache-royale-users.20374.n8.nabble.com/
>



-- 
Carlos Rovira
http://about.me/carlosrovira

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

[Alex Harui]

I don’t know how difficult it will be to sync up.  I don’t want to stop to try 
right now.  Volunteers are welcome to try.

Thanks,
-Alex

From: Piotr Zarzycki 
Reply-To: "users@royale.apache.org" 
Date: Friday, August 10, 2018 at 12:37 AM
To: "users@royale.apache.org" 
Subject: Re: RemoteObject and SimpleRemoteObject not working with WebORB for 
.NET

Hi Radu,

Althoght we don't have 0.9.3 released you can use nightly build [1].

Probably later you will need MXRoyale branch to go with Emulation path.[2]

Alex,

Is it even possible sync that branch with develop?

[1] 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/
[2] 
https://github.com/apache/royale-asjs/wiki/emulation-components

Thanks,
Piotr

On Fri, Aug 10, 2018, 9:15 AM Carlos Rovira 
mailto:carlosrov...@apache.org>> wrote:
Hi Joe,

- correlationId is received from server (talking about BlazeDS always, since 
don't know about WebOrb), and is a String if small messages are off and a 
ByteArray if on.
- operation is send from client and is 5 (client pong operation) in a normal RO 
operation (not SimpleRO) to establish connection with BlazeDS, then "operation" 
is the name of the method your are asking for.
In SimpleRO instead of 5 is 13 (trigger connect operation) for the first 
connection.

So my guess is that something is wrong in your code

I'll respond to the other email now



2018-08-10 1:19 GMT+02:00 JoeBoxer 
mailto:craigsi...@hotmail.com>>:
Hello Carlos and Alex.

After digging a bit further i noticed that WebORB is expecting 2 additional
properties in the remoting request than what AbstractMessage.as is sending.

AbstractMessage.as sends:

body
clientId
destination
headers
messageId
timestamp
timeToLive

WebORB is expecting...

body
clientId
destination
headers
messageId
timestamp
timeToLive

AND

operation
correlationId

This could be why the WebORB parser is throwing an exception.  Your
thoughts?

Regards



--
Sent from: 
http://apache-royale-users.20374.n8.nabble.com/



--
Carlos Rovira
http://about.me/carlosrovira

Re: WORK ON EMULATION

[Alex Harui]

Hi Alina,

What is being loaded?  Flex apps should be using mx.controls.SWFLoader, 
mx.modules.ModuleLoader and mx.controls.Image (or their Spark equivalents) and 
not flash.display.Loader directly.  It would be better to change your 
application to not use flash.display.Loader unless there are lots of instances 
of using it.

-Alex

On 8/10/18, 2:27 AM, "Alina Kazi"  wrote:

Hi Alex,

 

flash.display.Loader 

flash.display.Loader:content

flash.display.Loader:contentLoaderInfo 

flash.display.Loader:height

flash.display.Loader:load

flash.display.Loader:loadBytes

flash.display.Loader:mask

flash.display.Loader:width

flash.display.Loader:x 

flash.display.Loader:y

 

These properties and methods of API Loader are used.

Should I create mx Emulation for Loader?

 

Regards,

Alina Kazi

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

[JoeBoxer]

Hello Carlos.

The destinations for WebORB are defined in a different config file.  I'll
upload that file for you too see.  I use the GenericDestination because its
a wild card and doesn't require me to specify any namespaces.

remoting-config.xml
  

   

*

 

I'll take some time to test various settings in the remoting-config file and
see if i get a different response.

The initRemoting click event does call the following code
protected function initRemoting():void 
{ 
 remotingService.send("GetCountryList",[]); 
} 

Its a simple request that returns an array.  From what i can tell in the
WebORB logs is that the request coming in from RemoteObject or
SimpleRemoteObject is not being parsed correctly.  It doesn't matter what i
put in for the source, destination properties it still results in... 

PM:cannot parse request. possible reasons: malformed request or protocol
formatter is not registered 

Thank you for your continued attention with this issue.

Regards



--
Sent from: http://apache-royale-users.20374.n8.nabble.com/

WORK ON EMULATION

[Alina Kazi]

Hi Alex,

 

flash.display.Loader 

flash.display.Loader:content

flash.display.Loader:contentLoaderInfo 

flash.display.Loader:height

flash.display.Loader:load

flash.display.Loader:loadBytes

flash.display.Loader:mask

flash.display.Loader:width

flash.display.Loader:x 

flash.display.Loader:y

 

These properties and methods of API Loader are used.

Should I create mx Emulation for Loader?

 

Regards,

Alina Kazi

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

[Carlos Rovira]

Hi

I forgot to mention one more thing about passing a List. In BlazeDS and
ColdFusion (for what I know from other users), a server side Collection is
passed like an externalized object reference. We solved this for BlazeDS
and Coldfusion. I think that should work the same for WebOrb, but since
maybe you're the first trying this I don't know for sure at this time. Ad
well, in Royale we use ArrayList instead of ArrayCollection like we use to
do in Flex. For that reason I encourage you to start with a simple pass of
a String and then cover other scenarios progressively.

thanks

Carlos



2018-08-10 9:51 GMT+02:00 Carlos Rovira :

> Jose,
>
> based in your info I could make a working example to try. I think code is
> missing, but I can explain what I see so you can see if you need to fix
> things in your code or is only information that is missing in your email.
>
> Looking to the info you give:
>
> 1) The RO configuration is:
>  source = "Remoting.Service.Components.RemotingTest"
>  destination = "GenericDestination
>
> source is a deprecated property left in RO for
> backwards compatibility, since it expose the path to the server object.
> It's not needed anymore. Again talking about BlazeDS. Only destination
> should be required along "endPoint". If I search for "GenericDestination"
> in the config file you posted I don't find it. The same happens for "
> Remoting.Service.Components.RemotingTest". IMHO the .Net class should be
> exposed in the weborb config file like this one:
>
> 
> ExamplesActivationSession
> Weborb.Examples.ShoppingCart
> 
>
> to have something like:
>
> 
> RemotingTest
> Remoting.Service.Components.RemotingTest
> 
>
>
> In our example in BlazeDS we don't do this in config file since we have a
> Spring annotation in code. Example:
>
> @Service("exampleService")
> @RemotingDestination
> public class ExampleService {
>
> just guessing and trying to match what I know from BlazeDS and what I see
> in your WebOrb config file
>
> Then remove "source" property from the Royale RO declaration
>
> Now going to the calling code: I don't see nothing of that in your sample
> code. It seems the button calls "initRemoting" but where's the code?
>
> The code should be something like:
>
> protected function sendName():void
> {
> service.send("XXX", []);
> }
>
> Where XXX is the name of the method in the .Net class
> Remoting.Service.Components.RemotingTest
> second param is the array of params to send to that method. I understand
> in this case we don't send anything
>
> Then managing the result, I don't see again any callback code. But lets
> imagine s something like this:
>
> private function onResult(evt:ResultEvent):void
> {
> trace("[Client:" + RoyaleClient.getInstance().id + "]
> Result= " + evt.data);
>
> var arr:ArrayList = new ArrayList(evt.data as Array);
> list.dataProvider = arr;
>
> }
>
> If you run in debug mode (js-debug) in your browser (and here is important
> that you left your browser communication within local and external sources
> since that security restriction will make this communication not work)
> you should see a trace with the "clientId" and the data from server.
> clientId will then be shared in each transaction with the server
>
> then since we are receiving a list of countries for what I understand, you
> should get an Array (maybe for the first connection you should start with
> only a String, instead this structure since is more complex)
>
> For the Array, one important thing is to know if each object in the array
> are plain Objects or TypedObjects and if the later, you'll need something
> like the following example in the Class:
>
> [RemoteClass(alias="org.apache.royale.amfsamples.valueobjects.Product")]
> public class Product
> {
>
> Maybe in WebOrb is needed as well some config, on this point.
>
> My suggestion is that instead of try for the first time to exchange a
> list, you'll try to send a simple string and send back another string from
> WebOrb method. That will make a safe point from wich you can evolve to
> something more complicated. Then try a Typed object, and then try a List of
> typed objects.
>
>
>
>
>
> 2018-08-10 9:15 GMT+02:00 Carlos Rovira :
>
>> Hi Joe,
>>
>> - correlationId is received from server (talking about BlazeDS always,
>> since don't know about WebOrb), and is a String if small messages are off
>> and a ByteArray if on.
>> - operation is send from client and is 5 (client pong operation) in a
>> normal RO operation (not SimpleRO) to establish connection with BlazeDS,
>> then "operation" is the name of the method your are asking for.
>> In SimpleRO instead of 5 is 13 (trigger connect operation) for the first
>> connection.
>>
>> So my guess is that something is wrong in your code
>>
>> I'll respond to the other email now
>>
>>
>>
>> 2018-08-10 1:19 GMT+02:00 JoeBoxer :
>>
>>> Hello Carlos and Alex.
>>>
>>> After digging a bit further i noticed that WebORB is expecting

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

[Carlos Rovira]

Jose,

based in your info I could make a working example to try. I think code is
missing, but I can explain what I see so you can see if you need to fix
things in your code or is only information that is missing in your email.

Looking to the info you give:

1) The RO configuration is:
 source = "Remoting.Service.Components.RemotingTest"
 destination = "GenericDestination

source is a deprecated property left in RO for
backwards compatibility, since it expose the path to the server object.
It's not needed anymore. Again talking about BlazeDS. Only destination
should be required along "endPoint". If I search for "GenericDestination"
in the config file you posted I don't find it. The same happens for "
Remoting.Service.Components.RemotingTest". IMHO the .Net class should be
exposed in the weborb config file like this one:


ExamplesActivationSession
Weborb.Examples.ShoppingCart


to have something like:


RemotingTest
Remoting.Service.Components.RemotingTest



In our example in BlazeDS we don't do this in config file since we have a
Spring annotation in code. Example:

@Service("exampleService")
@RemotingDestination
public class ExampleService {

just guessing and trying to match what I know from BlazeDS and what I see
in your WebOrb config file

Then remove "source" property from the Royale RO declaration

Now going to the calling code: I don't see nothing of that in your sample
code. It seems the button calls "initRemoting" but where's the code?

The code should be something like:

protected function sendName():void
{
service.send("XXX", []);
}

Where XXX is the name of the method in the .Net class
Remoting.Service.Components.RemotingTest
second param is the array of params to send to that method. I understand in
this case we don't send anything

Then managing the result, I don't see again any callback code. But lets
imagine s something like this:

private function onResult(evt:ResultEvent):void
{
trace("[Client:" + RoyaleClient.getInstance().id + "]
Result= " + evt.data);

var arr:ArrayList = new ArrayList(evt.data as Array);
list.dataProvider = arr;

}

If you run in debug mode (js-debug) in your browser (and here is important
that you left your browser communication within local and external sources
since that security restriction will make this communication not work)
you should see a trace with the "clientId" and the data from server.
clientId will then be shared in each transaction with the server

then since we are receiving a list of countries for what I understand, you
should get an Array (maybe for the first connection you should start with
only a String, instead this structure since is more complex)

For the Array, one important thing is to know if each object in the array
are plain Objects or TypedObjects and if the later, you'll need something
like the following example in the Class:

[RemoteClass(alias="org.apache.royale.amfsamples.valueobjects.Product")]
public class Product
{

Maybe in WebOrb is needed as well some config, on this point.

My suggestion is that instead of try for the first time to exchange a list,
you'll try to send a simple string and send back another string from WebOrb
method. That will make a safe point from wich you can evolve to something
more complicated. Then try a Typed object, and then try a List of typed
objects.





2018-08-10 9:15 GMT+02:00 Carlos Rovira :

> Hi Joe,
>
> - correlationId is received from server (talking about BlazeDS always,
> since don't know about WebOrb), and is a String if small messages are off
> and a ByteArray if on.
> - operation is send from client and is 5 (client pong operation) in a
> normal RO operation (not SimpleRO) to establish connection with BlazeDS,
> then "operation" is the name of the method your are asking for.
> In SimpleRO instead of 5 is 13 (trigger connect operation) for the first
> connection.
>
> So my guess is that something is wrong in your code
>
> I'll respond to the other email now
>
>
>
> 2018-08-10 1:19 GMT+02:00 JoeBoxer :
>
>> Hello Carlos and Alex.
>>
>> After digging a bit further i noticed that WebORB is expecting 2
>> additional
>> properties in the remoting request than what AbstractMessage.as is
>> sending.
>>
>> AbstractMessage.as sends:
>>
>> body
>> clientId
>> destination
>> headers
>> messageId
>> timestamp
>> timeToLive
>>
>> WebORB is expecting...
>>
>> body
>> clientId
>> destination
>> headers
>> messageId
>> timestamp
>> timeToLive
>>
>> AND
>>
>> operation
>> correlationId
>>
>> This could be why the WebORB parser is throwing an exception.  Your
>> thoughts?
>>
>> Regards
>>
>>
>>
>> --
>> Sent from: http://apache-royale-users.20374.n8.nabble.com/
>>
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com


Conócenos en 1 minuto! 


AVISO LEGAL: La información contenida en 

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

[Piotr Zarzycki]

Hi Radu,

Althoght we don't have 0.9.3 released you can use nightly build [1].

Probably later you will need MXRoyale branch to go with Emulation path.[2]

Alex,

Is it even possible sync that branch with develop?

[1]
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/
[2] https://github.com/apache/royale-asjs/wiki/emulation-components

Thanks,
Piotr

On Fri, Aug 10, 2018, 9:15 AM Carlos Rovira  wrote:

> Hi Joe,
>
> - correlationId is received from server (talking about BlazeDS always,
> since don't know about WebOrb), and is a String if small messages are off
> and a ByteArray if on.
> - operation is send from client and is 5 (client pong operation) in a
> normal RO operation (not SimpleRO) to establish connection with BlazeDS,
> then "operation" is the name of the method your are asking for.
> In SimpleRO instead of 5 is 13 (trigger connect operation) for the first
> connection.
>
> So my guess is that something is wrong in your code
>
> I'll respond to the other email now
>
>
>
> 2018-08-10 1:19 GMT+02:00 JoeBoxer :
>
>> Hello Carlos and Alex.
>>
>> After digging a bit further i noticed that WebORB is expecting 2
>> additional
>> properties in the remoting request than what AbstractMessage.as is
>> sending.
>>
>> AbstractMessage.as sends:
>>
>> body
>> clientId
>> destination
>> headers
>> messageId
>> timestamp
>> timeToLive
>>
>> WebORB is expecting...
>>
>> body
>> clientId
>> destination
>> headers
>> messageId
>> timestamp
>> timeToLive
>>
>> AND
>>
>> operation
>> correlationId
>>
>> This could be why the WebORB parser is throwing an exception.  Your
>> thoughts?
>>
>> Regards
>>
>>
>>
>> --
>> Sent from: http://apache-royale-users.20374.n8.nabble.com/
>>
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

[Alex Harui]

Hi Radu,

Thanks for your offer.  I don’t think there is a central place to accept 
monetary donations for Apache Royale.  Donating to the Apache Software 
Foundation is always a nice thing to do, but it won’t directly accelerate 
development.

There may be a few committers with spare time who would be encouraged to spend 
more time on Royale if they could get paid for it.  That’s one way to help.  
Another is for you to donate your time instead of money.  Learn how to fix bugs 
and develop new features in Royale.  We could always use more folks 
contributing code, tests, doc, etc.

Thanks,
-Alex

From: radu birsan 
Reply-To: "users@royale.apache.org" 
Date: Thursday, August 9, 2018 at 10:33 PM
To: "users@royale.apache.org" 
Subject: Re: RemoteObject and SimpleRemoteObject not working with WebORB for 
.NET

Where can we make a donation to help release the official Apache 9.3 with AMF 
support?

Re: RemoteObject and SimpleRemoteObject not working with WebORB for .NET

[Carlos Rovira]

Hi Joe,

- correlationId is received from server (talking about BlazeDS always,
since don't know about WebOrb), and is a String if small messages are off
and a ByteArray if on.
- operation is send from client and is 5 (client pong operation) in a
normal RO operation (not SimpleRO) to establish connection with BlazeDS,
then "operation" is the name of the method your are asking for.
In SimpleRO instead of 5 is 13 (trigger connect operation) for the first
connection.

So my guess is that something is wrong in your code

I'll respond to the other email now



2018-08-10 1:19 GMT+02:00 JoeBoxer :

> Hello Carlos and Alex.
>
> After digging a bit further i noticed that WebORB is expecting 2 additional
> properties in the remoting request than what AbstractMessage.as is sending.
>
> AbstractMessage.as sends:
>
> body
> clientId
> destination
> headers
> messageId
> timestamp
> timeToLive
>
> WebORB is expecting...
>
> body
> clientId
> destination
> headers
> messageId
> timestamp
> timeToLive
>
> AND
>
> operation
> correlationId
>
> This could be why the WebORB parser is throwing an exception.  Your
> thoughts?
>
> Regards
>
>
>
> --
> Sent from: http://apache-royale-users.20374.n8.nabble.com/
>



-- 
Carlos Rovira
http://about.me/carlosrovira