Hi Janak, thank you so much for helping. The jar holding 'MyClientCoderRegistryProvider' is in the Library path.
I looked at the lax - file. There it referes to the jre included in version 6.2.2 which is of version 1.4.xxx. So i tried to replace that entry refering to my jre which is 1.6.0_13, but that did not work either. In ULC Load 3.0.2 UI.lax I put lax.nl.current.vm=C:\\Programme\\Java\\jre1.6.0_13\\bin\\java.exe Everything else you mentioned has been provided. What else would you suggest? Best regards Martin -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Janak Mulani Gesendet: Freitag, 12. Februar 2010 12:12 An: [email protected] Betreff: RE: [ULC-developer] AW: custom client coder registry provider Hi Martin, ULCLoad 3.0.2 requires ULC 6.2.2 or higher. This means that in the ui/lib dir of ULCLoad you should have client side jars ulc-applet-client.jar, ulc-base-client.jar, ulc-base-trusted.jar and ulc-servlet-client.jar from ULC 6.2.2 or higher. You must ensure that version of ULC used by ULCLoad is the same as the version of ULC used be the ULC Application on the server which is going to be load tested. Now the question of choosing the custom client coder registry provider: To be able to choose a custom client side class (such as MyClientCoderRegistryProvider extends DefaultClientCoderRegistryProvider) you need to put the the jar file containing this class in the path of ULCLoad i.e. choose and include the jar in the Library list on the Recorder screen. It has been reported sometimes that even if the required jar is included in the classpath library list, the combobox for client coder registry still does not show the custom client coder registry class for selection. I just tested this with ULCLoad 3.0.2 running with ULC 6.2.2 and ULC 2008 u4. In both the cases I was able to select the custom client side class that was compiled with combinations of {ULC 6.2.2, ULC 2008, ULC 2008 u3} and {Java 5, Java 6}. However as I said earlier this issue has been reported before. So you must ensure that: 1. the custom client side class is compiled with same version of ULC that is being used by ULCLoad and the ULCApp. 2. ULCLoad is running with the same Java version (see xxxUI.lax file in bin dir) as the one with which the custom client class was compiled. Thanks and regards, Janak ----------------------------------------- Janak Mulani email: [email protected] url: http://www.canoo.com Beyond AJAX - Java Rich Internet Applications http://www.canoo.com/ulc ----------------------------------------- > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Sturzenegger Martin DFR IT AG > Sent: Friday, February 12, 2010 8:01 AM > To: [email protected]; [email protected] > Subject: AW: [ULC-developer] AW: custom client coder registry provider > > Hi Janak, > the classes on the serverside are compiled with java 1.6, the > ones on the client with java 1.6 target 1.5 > the ULC version used ist 6.2.3 > could you please name the version of ULCLoad that suits? > many thanks in advance > regards > martin > > > > -----Ursprüngliche Nachricht----- > Von: [email protected] > [mailto:[email protected]] Im Auftrag von > Janak Mulani > Gesendet: Donnerstag, 11. Februar 2010 09:01 > An: [email protected] > Betreff: RE: [ULC-developer] AW: custom client coder registry provider > > Hi John, Martin, > > There are 2 dependencies: > > 1. The ULC version used by ULCLoad (the ULC client side jars > that you have > in your ui/lib dir) has to be the same as that used by the > ULC App running > on the server. This is a given, otherwise, you will run into version > mismatch while recording and playing. This means the ULC client side > extension classes must be compiled with the same version of ULC. > > 2. The Java version used for compiling the classes must also > be the same > (this has been the observed behavior). > > Thanks and regards, > > Janak > > ----------------------------------------- > Janak Mulani > > email: [email protected] > url: http://www.canoo.com > > Beyond AJAX - Java Rich Internet Applications > > http://www.canoo.com/ulc > ----------------------------------------- > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > Prince John, Bedag > > Sent: Thursday, February 11, 2010 6:10 AM > > To: [email protected]; Sturzenegger Martin DFR IT AG > > Subject: RE: [ULC-developer] AW: custom client coder > registry provider > > > > Hi Martin, Janak, > > > > I don't think this compiler requirement can be right. I ran > > two of our apps the other day under ULC Load with custom > > Coder Registry Providers, both compiled with java 6 (though > > target and source 1.5). > > > > I could only load the provider when I installed ULC load with > > the same version of ulc as used in the application, though (I > > had to install ulcload twice, once for 2008u4 and once for > > 6.2.3). Might that be the problem? > > > > Best wishes > > > > John > > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > Sturzenegger Martin DFR IT AG > > Sent: Wednesday, February 10, 2010 5:17 PM > > To: [email protected]; [email protected] > > Subject: AW: [ULC-developer] AW: custom client coder > registry provider > > > > Hi Janak, > > thank you so much for answering. Alas I'm puzzled: A collegue > > of mine is testing the same software. He uses ulcload on > > ubuntu where he is able to select the custom coder provider. > > The provider is compiled with java 1.6 target 1.5 and he uses > > ulcload 3.0.1 (I tried the same scenario under windows and > it failed). > > Greetings > > Martin > > > > > > > > > > > > -----Ursprüngliche Nachricht----- > > Von: [email protected] > > [mailto:[email protected]] Im Auftrag von > > Janak Mulani > > Gesendet: Mittwoch, 10. Februar 2010 08:59 > > An: [email protected] > > Betreff: RE: [ULC-developer] AW: custom client coder > registry provider > > > > Hi Martin, > > > > Not a matter of luck but somehow your mail from 04.02 did not > > get posted > > on the developer list! > > > > >>> > > As I have to test an third party application that provides a > > custom client coder registry provider I added on the > > ULCRecoder all given > > jars to the classpath including the one jar containing a > custom class > > which subclasses DefaultClientCoderRegistryProvider. > Unfortunately the > > custom client coder registry provider does not show up in the > > Client Coder > > Registry Provider picklist. With 3.0.1 I tried that on ubuntu > > and there it > > worked but under xp it didn't using identical class-libs. As > > this prevents > > from getting started, I appreaciate any piece of information > > that would > > lead to overcome that frustrating effect. > > >>> > > > > To be able to select coder provider it must be compiled > with the same > > javac as that of ULC i.e. Java 1.4. > > > > Thanks and regards, > > > > Janak > > > > ----------------------------------------- > > Janak Mulani > > > > email: [email protected] > > url: http://www.canoo.com <http://www.canoo.com/> > > > > Beyond AJAX - Java Rich Internet Applications > > > > http://www.canoo.com/ulc > > ----------------------------------------- > > > > ________________________________ > > > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > Sturzenegger > > Martin DFR IT AG > > Sent: Tuesday, February 09, 2010 5:03 PM > > To: [email protected] > > Subject: [ULC-developer] AW: custom client coder > > registry provider > > > > > > Hi, > > > > unluckily I didn't get any response. Does that mean, that nobody > > ever encountered that problem or does that mean nobody cares? > > > > I'd just love to know > > > > best regards > > > > m. > > > > > > > > ________________________________ > > > > Von: Sturzenegger Martin DFR IT AG > > Gesendet: Donnerstag, 4. Februar 2010 09:58 > > An: '[email protected]' > > Betreff: custom client coder registry provider > > > > > > > > Hi, > > > > just downloaded evolution copies of ulc-2008-u4 and > > ulcload-3.0.2 > > and installed them on windows xp. It went smoothly and > ulcload starts > > without any problems. > > > > As I have to test an third party application that provides a > > custom client coder registry provider I added on the > > ULCRecoder all given > > jars to the classpath including the one jar containing a > custom class > > which subclasses DefaultClientCoderRegistryProvider. > Unfortunately the > > custom client coder registry provider does not show up in the > > Client Coder > > Registry Provider picklist. With 3.0.1 I tried that on ubuntu > > and there it > > worked but under xp it didn't using identical class-libs. As > > this prevents > > from getting started, I appreaciate any piece of information > > that would > > lead to overcome that frustrating effect. > > > > best regards > > > > --------------------------------- > > > > martin sturzenegger > > > > 062 835 10 07 > > > > 079 456 24 94 > > > > [email protected] > > > > > > > > > > > > _______________________________________________ > > ULC-developer mailing list > > [email protected] > > http://lists.canoo.com/mailman/listinfo/ulc-developer > > _______________________________________________ > > ULC-developer mailing list > > [email protected] > > http://lists.canoo.com/mailman/listinfo/ulc-developer > > _______________________________________________ > > ULC-developer mailing list > > [email protected] > > http://lists.canoo.com/mailman/listinfo/ulc-developer > > > _______________________________________________ > ULC-developer mailing list > [email protected] > http://lists.canoo.com/mailman/listinfo/ulc-developer > _______________________________________________ > ULC-developer mailing list > [email protected] > http://lists.canoo.com/mailman/listinfo/ulc-developer > _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
