Hi,
I tried loading XML RPC from SS3 as suggested by evaluating: Gofer new squeaksource3: 'XMLRPC'; package: 'ConfigurationOfXMLRPC'; package: 'Spy'; package: 'XMLRPC-Client-Core'; package: 'XMLRPC-Client-Tests'; package: 'XMLRPC-Server'; package: 'XMLRPC-Server-Core'; package: 'XMLRPC-Server-Tests'; load But I got an exeception "Unable to resolve Spy-maf.4". It seem that there is a problem, since the latest Spy is version 7. I tested on both Pharo 2 and 1.4 and got the same result. Then I tried to loadConfigurationOfXMLRPC alone Gofer new squeaksource3: 'XMLRPC'; package: 'ConfigurationOfXMLRPC'; load ConfigurationOfXMLRPC load On Pharo 2, I got notifications (see below) that make me belive that DynamicBindgs and KomHttpServer were not ported to Pharo 2. Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury ***Dynamic Bindings This package depends on the following classes: BlockContext You must resolve these dependencies before you will be able to load these definitions: forkWithBindings forkWithBindings: forkWithClampedBindings forkWithClampedBindings: forkWithIsolatedBindings forkWithIsolatedBindings: newProcessWithBindings newProcessWithBindings: newProcessWithClampedBindings newProcessWithClampedBindings: newProcessWithIsolatedBindings newProcessWithIsolatedBindings: valueWithBindings: valueWithBindingsContext: ***KomHttpServer This package depends on the following classes: TranscriptStream BlockContext You must resolve these dependencies before you will be able to load these definitions: doPostProcessingFor:response: processHttp processHttpRequest: processVisitor: validateForStack: visitWithValuable: isTranscriptStream Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print |
why spy is needed?
I thought it was a meta spying tools. May be this is also time to build a configuration. because Stef On May 31, 2012, at 12:34 PM, Noury Bouraqadi wrote: > Hi, > > I tried loading XML RPC from SS3 as suggested by evaluating: > Gofer new > squeaksource3: 'XMLRPC'; > package: 'ConfigurationOfXMLRPC'; > package: 'Spy'; > package: 'XMLRPC-Client-Core'; > package: 'XMLRPC-Client-Tests'; > package: 'XMLRPC-Server'; > package: 'XMLRPC-Server-Core'; > package: 'XMLRPC-Server-Tests'; > load > > But I got an exeception "Unable to resolve Spy-maf.4". > It seem that there is a problem, since the latest Spy is version 7. > I tested on both Pharo 2 and 1.4 and got the same result. > > Then I tried to loadConfigurationOfXMLRPC alone > Gofer new > squeaksource3: 'XMLRPC'; > package: 'ConfigurationOfXMLRPC'; > load > ConfigurationOfXMLRPC load > > On Pharo 2, I got notifications (see below) that make me belive that DynamicBindgs and KomHttpServer were not ported to Pharo 2. > > Noury > -- > http://twitter.com/#!/NouryBouraqadi > http://www.kroobe.com/profile/noury > > > ***Dynamic Bindings > This package depends on the following classes: > BlockContext > You must resolve these dependencies before you will be able to load these definitions: > forkWithBindings > forkWithBindings: > forkWithClampedBindings > forkWithClampedBindings: > forkWithIsolatedBindings > forkWithIsolatedBindings: > newProcessWithBindings > newProcessWithBindings: > newProcessWithClampedBindings > newProcessWithClampedBindings: > newProcessWithIsolatedBindings > newProcessWithIsolatedBindings: > valueWithBindings: > valueWithBindingsContext: > > > ***KomHttpServer > This package depends on the following classes: > TranscriptStream > BlockContext > You must resolve these dependencies before you will be able to load these definitions: > doPostProcessingFor:response: > processHttp > processHttpRequest: > processVisitor: > validateForStack: > visitWithValuable: > isTranscriptStream > > > > Afin de contribuer au respect de l'environnement, > merci de n'imprimer ce courriel qu'en cas de necessite > > Please consider the environment before you print > > > > |
It seems that XMlRPC-Server relies on it. Strage.
We need to clean it up. Luc and I started looking at it because we need it for a robotic project. Noury On 31 mai 2012, at 14:50, Stéphane Ducasse wrote: > why spy is needed? > I thought it was a meta spying tools. > May be this is also time to build a configuration. because > > > Stef > > On May 31, 2012, at 12:34 PM, Noury Bouraqadi wrote: > >> Hi, >> >> I tried loading XML RPC from SS3 as suggested by evaluating: >> Gofer new >> squeaksource3: 'XMLRPC'; >> package: 'ConfigurationOfXMLRPC'; >> package: 'Spy'; >> package: 'XMLRPC-Client-Core'; >> package: 'XMLRPC-Client-Tests'; >> package: 'XMLRPC-Server'; >> package: 'XMLRPC-Server-Core'; >> package: 'XMLRPC-Server-Tests'; >> load >> >> But I got an exeception "Unable to resolve Spy-maf.4". >> It seem that there is a problem, since the latest Spy is version 7. >> I tested on both Pharo 2 and 1.4 and got the same result. >> >> Then I tried to loadConfigurationOfXMLRPC alone >> Gofer new >> squeaksource3: 'XMLRPC'; >> package: 'ConfigurationOfXMLRPC'; >> load >> ConfigurationOfXMLRPC load >> >> On Pharo 2, I got notifications (see below) that make me belive that DynamicBindgs and KomHttpServer were not ported to Pharo 2. >> >> Noury >> -- >> http://twitter.com/#!/NouryBouraqadi >> http://www.kroobe.com/profile/noury >> >> >> ***Dynamic Bindings >> This package depends on the following classes: >> BlockContext >> You must resolve these dependencies before you will be able to load these definitions: >> forkWithBindings >> forkWithBindings: >> forkWithClampedBindings >> forkWithClampedBindings: >> forkWithIsolatedBindings >> forkWithIsolatedBindings: >> newProcessWithBindings >> newProcessWithBindings: >> newProcessWithClampedBindings >> newProcessWithClampedBindings: >> newProcessWithIsolatedBindings >> newProcessWithIsolatedBindings: >> valueWithBindings: >> valueWithBindingsContext: >> >> >> ***KomHttpServer >> This package depends on the following classes: >> TranscriptStream >> BlockContext >> You must resolve these dependencies before you will be able to load these definitions: >> doPostProcessingFor:response: >> processHttp >> processHttpRequest: >> processVisitor: >> validateForStack: >> visitWithValuable: >> isTranscriptStream >> >> >> >> Afin de contribuer au respect de l'environnement, >> merci de n'imprimer ce courriel qu'en cas de necessite >> >> Please consider the environment before you print >> >> >> >> > > Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print |
Hi:
Sorry the late answer.... If you take an 1.4 stock image, and evaluates (as is commented on http://code.google.com/p/pharo-xmlrpc/): Gofer it url: 'http://ss3.gemstone.com/ss/XMLRPC'; package: 'ConfigurationOfXMLRPC'; load. and then: (ConfigurationOfXMLRPC project version: '1.0-Beta4') load: 'All'. the whole stuff should load. I noticed an error: This package depends on the following classes: TranscriptStream You must resolve these dependencies before you will be able to load these definitions: isTranscriptStream (May be another thing changed in Pharo that I need to know and fix, press proceed to load anyway). But the bad new is that in 1.4 I've some errors on tests, mainly a serious one in server that freeze the image, caution. However, the XMLRPC Client seems to work. XMLRPC is always in my to-do list but a project in what I can invest only a portion of my limited free time. The latest new was that I adapted the Client to use with Zinc, but need still to make the same thing with the server, then all xmlrpc should install and run in a stock image, without need Komanche for example. With respect to Pharo 2.0 I can't help, not tried yet. HTH. Germán. |
Hi Germán,
Thanks for your answer. Indeed, I tried with Pharo 1.4. And had the same issues. My plan is to port XML RPC to Pharo 2. I'm interested on your work with Zinc. Where is it available ? Can I get write access grant to the repo, so I can upload any improvement I do ? What I wanted to do is to cut off everything not XML RPC and complete based on sUnit tests. BTW, any simple way to load all SUnit tests for all packages ? I started analyzing the ConfigurationOfxxx classes. ConfigurationOfXMLSupport includes some references that I would like to have some hints on them (where they are used): - Grease - Opax - Pastell - SiXX - XML-Observable Thanx, Noury On 3 juin 2012, at 17:26, garduino wrote: > Hi: > > Sorry the late answer.... > > If you take an 1.4 stock image, and evaluates (as is commented on > http://code.google.com/p/pharo-xmlrpc/): > > Gofer it > url: 'http://ss3.gemstone.com/ss/XMLRPC'; > package: 'ConfigurationOfXMLRPC'; > load. > > and then: > > > (ConfigurationOfXMLRPC project version: '1.0-Beta4') load: 'All'. > > the whole stuff should load. > > I noticed an error: > > This package depends on the following classes: > TranscriptStream > You must resolve these dependencies before you will be able to load these > definitions: > isTranscriptStream > > (May be another thing changed in Pharo that I need to know and fix, press > proceed to load anyway). > > But the bad new is that in 1.4 I've some errors on tests, mainly a serious > one in server that freeze the image, caution. However, the XMLRPC Client > seems to work. > > XMLRPC is always in my to-do list but a project in what I can invest only a > portion of my limited free time. > > The latest new was that I adapted the Client to use with Zinc, but need > still to make the same thing with the server, then all xmlrpc should install > and run in a stock image, without need Komanche for example. > > With respect to Pharo 2.0 I can't help, not tried yet. > > HTH. > Germán. > > > > > > -- > View this message in context: http://forum.world.st/Trouble-loading-XML-RPC-tp4632653p4633037.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print |
On Jun 4, 2012, at 4:34 PM, Noury Bouraqadi wrote: > Hi Germán, > > Thanks for your answer. Indeed, I tried with Pharo 1.4. And had the same issues. > My plan is to port XML RPC to Pharo 2. I'm interested on your work with Zinc. > Where is it available ? > > Can I get write access grant to the repo, so I can upload any improvement I do ? > > What I wanted to do is to cut off everything not XML RPC and complete based on sUnit tests. > BTW, any simple way to load all SUnit tests for all packages ? load: {'Tests'} ? > > I started analyzing the ConfigurationOfxxx classes. > ConfigurationOfXMLSupport includes some references that I would like to have some hints on them (where they are used): ConfigurationOfXMLSupport is a bad example to me it is not good to have all the clients of XML groups. Normally it is much better to have a nice configuration for Opax Sixx Pastell separated. > - Grease > - Opax > - Pastell > - SiXX > - XML-Observable > > Thanx, > Noury > > On 3 juin 2012, at 17:26, garduino wrote: > >> Hi: >> >> Sorry the late answer.... >> >> If you take an 1.4 stock image, and evaluates (as is commented on >> http://code.google.com/p/pharo-xmlrpc/): >> >> Gofer it >> url: 'http://ss3.gemstone.com/ss/XMLRPC'; >> package: 'ConfigurationOfXMLRPC'; >> load. >> >> and then: >> >> >> (ConfigurationOfXMLRPC project version: '1.0-Beta4') load: 'All'. >> >> the whole stuff should load. >> >> I noticed an error: >> >> This package depends on the following classes: >> TranscriptStream >> You must resolve these dependencies before you will be able to load these >> definitions: >> isTranscriptStream >> >> (May be another thing changed in Pharo that I need to know and fix, press >> proceed to load anyway). >> >> But the bad new is that in 1.4 I've some errors on tests, mainly a serious >> one in server that freeze the image, caution. However, the XMLRPC Client >> seems to work. >> >> XMLRPC is always in my to-do list but a project in what I can invest only a >> portion of my limited free time. >> >> The latest new was that I adapted the Client to use with Zinc, but need >> still to make the same thing with the server, then all xmlrpc should install >> and run in a stock image, without need Komanche for example. >> >> With respect to Pharo 2.0 I can't help, not tried yet. >> >> HTH. >> Germán. >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Trouble-loading-XML-RPC-tp4632653p4633037.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > Noury > -- > http://twitter.com/#!/NouryBouraqadi > http://www.kroobe.com/profile/noury > > > Afin de contribuer au respect de l'environnement, > merci de n'imprimer ce courriel qu'en cas de necessite > > Please consider the environment before you print > > > > |
In reply to this post by Noury Bouraqadi-2
Hi Noury:
>Thanks for your answer. Indeed, I tried with Pharo 1.4. And had the same issues. >My plan is to port XML RPC to Pharo 2. I'm interested on your work with Zinc. >Where is it available ? Using the procedure I commented, I had not problems installing in 1.4, except the Transcript stuff. My work with Zinc is pretty simple, at client level is in the latest published .mcz, but at server level I have not published nothing yet, because is a work in progress. > Can I get write access grant to the repo, so I can upload any improvement I do ? Sure, I added you as developer. Let me know if works ok. > What I wanted to do is to cut off everything not XML RPC and complete based on sUnit tests. > BTW, any simple way to load all SUnit tests for all packages ? I'm not sure of understand what you mean. >I started analyzing the ConfigurationOfxxx classes. >ConfigurationOfXMLSupport includes some references that I would like to have some hints on them (where >they are used): >- Grease >- Opax >- Pastell >- SiXX >- XML-Observable I don't know about XMLSupport at this level, I'm only using it. Cheers, Germán. |
On 5 juin 2012, at 13:28, garduino wrote: >> Can I get write access grant to the repo, so I can upload any improvement >> I do ? > > Sure, I added you as developer. Let me know if works ok. > Thanx. I'll try it. >> What I wanted to do is to cut off everything not XML RPC and complete >> based on sUnit tests. >> BTW, any simple way to load all SUnit tests for all packages ? > > I'm not sure of understand what you mean. > Actually, I get only tests from xml rpc with your procedure. I thought there might be a way to get all tests for all required packages, to test their compatibility with Pharo 2.0 But, it seems that I have to load them by hand. Any way, I tried on Pharo 2.0. There is the issue of underscores, but this is no big deal. The good news is that the client side seems to work. At least the tests are green for parts that does not rely on a local server (XMLRPCTest is red!). Tests with Flicker do pass. There is however XMLROCDecoderTest>>#testDecoder that fails. The reason is that now Pharo does take care of nanoseconds, but the encoder does not handle it. I guess this is not supported in the protocol. Isn't it? So, I propose to fix it but putting nanoseconds to zero XMLRPCDateAndTime>>time: t "set the time portion of the datetime." time := Time fromSeconds: t seconds truncated Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print |
Ni Noury:
>Actually, I get only tests from xml rpc with your procedure. >I thought there might be a way to get all tests for all required packages, to test their compatibility with >Pharo 2.0 >But, it seems that I have to load them by hand. Ahh, but is not posible to make the load modifying the configurationof? > Any way, I tried on Pharo 2.0. There is the issue of underscores, but this is no big deal. I should re-check all the code (lot of parts are form older versions). >The good news is that the client side seems to work. At least the tests are green for parts that does not >rely on a local server (XMLRPCTest is red!). >Tests with Flicker do pass. Yes, the client side seems to work ok. Let me polish some more things. >There is however XMLROCDecoderTest>>#testDecoder that fails. The reason is that now Pharo does >take care of nanoseconds, but the encoder does not handle it. >I guess this is not supported in the protocol. Isn't it? So, I propose to fix it but putting nanoseconds to >zero >XMLRPCDateAndTime>>time: t > "set the time portion of the datetime." > time := Time fromSeconds: t seconds truncated Nice catch! I tried and Works ok. I think that will not generate any problem with the protocol. I can publish with some things I'm improving in the code if you agree. By other hand, the Transcript error at load time, have you experienced it? Is something related with some new thing in 1.4 ? I've not checked yet. Cheers and thanks by the cooperation! |
On 5 juin 2012, at 19:57, garduino wrote: > >> There is however XMLROCDecoderTest>>#testDecoder that fails. The reason is > that now Pharo does >take care of nanoseconds, but the encoder does not > handle it. >> I guess this is not supported in the protocol. Isn't it? So, I propose to > fix it but putting nanoseconds to >zero > >> XMLRPCDateAndTime>>time: t >> "set the time portion of the datetime." >> time := Time fromSeconds: t seconds truncated > > > Nice catch! I tried and Works ok. I think that will not generate any problem > with the protocol. > > I can publish with some things I'm improving in the code if you agree. > > By other hand, the Transcript error at load time, have you experienced it? > Is something related with some new thing in 1.4 ? I've not checked yet. > Yes. TranscriptStream was replaced by ThreadSafeTranscriptStream in 1.4. Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print |
Free forum by Nabble | Edit this page |