| |
| |
| |
|
Page: 1 2 3 4 5 6 7
Comments:
<0> its like doing Button b = new Button();
<0> except you don't hardcode the type
<0> so you can create instances of certain objects at runtime
<1> Rob_uknow, do you know if it's possible to create a type of a type p***ed as parameter in a generic?
<2> Cl***Loader.cl***ForName(string) ?
<0> you would need to know what type that is
<1> T :P
<0> see the Cl*** documentation
<0> it has methods like getConstructors
<0> getDeclaredAnnotations
<0> getGenericInterfaces
<2> nope
<2> Cl***.forName(string) ?
<0> wolfey?
<2> well cl*** of type p***ed?
<2> isnt that...Cl***.forName ?
<2> you p*** cl*** name and get cl***?
<2> or am i getting it terribly wrong?
<0> yes
<0> Cl***.forName("java.awt.Button");
<0> returns the cl*** Button
<2> of course i only used this for sql driver ;)
<2> but looks cool
<0> I used it for plugins
<0> the plugins extended some base cl***
<0> and I had a config file containing the plugin cl***es
<0> my app could create instances of these plugins based on the config file
<0> and call the base methods
<0> I used it to write a javabot with plugin funtionality
<2> great:) well i understand that database vendor driver extended java.sql.Driver
<0> its nice to write something like that
<0> it also gives insight on how webapps get loaded by the servlet container
<0> how it 'loads' the webapp jars during runtime
<2> replaces cl***loader?
<2> with new one?
<2> somebody told me so
<0> you can use URLCl***Loader and add the jars in the web-inf/lib directory
<0> any cl*** instantiated with that URLCl***Loader is able to find cl***es in the jars
<2> this URLCl***Loader.. is the thing in RMI magic too?
<2> i heard you can get cl***es from http in RMI client
<0> well you access the cl***loader remotely
<2> okey... mmm
<0> I would think the server interprets the rmi messages
<0> creates objects when needed
<0> invokes a method on the object
<0> and returns the result
<0> you can write that mechanism in a few hours if you want
<0> just as an experiment
<2> i guess.. well i did read about cache patterns, 'connection pools'.. so you create new instance only when needed, and keep already created ones for later reuse
<2> that's what you mean?
<2> i just dont see any good reason why i should be trying that:)
<0> i would only keep them alive if needed
<0> well its just interessting to see how rmi works
<0> or other technologies
<0> not by reading but by doing, guessing etc
<0> you are coding something and then a lightbulb starts glowing
<0> heh, this technique is probably also used for.. this and that
<2> well for now im satisfied that rmi works:)
<3> can anyone tell me what is object slicing
Return to
#java
or
Go to some related
logs:
KOKUMBER
#asm
#linux
#AllNiteCafe
#AllNiteCafe
grub-install fedora 5 usb
pcdiscount israel
#php
What does an autophobe avoid referring to ?
#java
|
|