Home » Archived » Visual Editor (VE) » [JEM] getting all constructors/fields/methods?
[JEM] getting all constructors/fields/methods? [message #78574] |
Sat, 29 January 2005 14:20  |
Eclipse User |
|
|
|
Originally posted by: lmorley.wpi.edu
Our plugin needs its own JVM. We've decided that JEM Proxy is the
closest to what we're looking for, and we've been checking to see if it
fits all of our needs. We're currently looking at 1.0.1, and there's one
issue we're running into.
We'd like to be able to get all of the constructors for a given class
(Class.getConstructors()). I expected to find this in a
IBeanTypeProxy.getConstructorProxies(), but this doesn't exist. (Same
thing goes for fields and methods, as well as declared
constructors/fields/methods).
Is there a workaround, or is there any way to get something like this
into a future release? If there isn't a workaround currently, we'd be
happy to contribute a patch if you guys are on a tight schedule and
don't mind including it.
--
Liam Morley
Computer Science Undergraduate
Worcester Polytechnic Institute
|
|
|
Re: [JEM] getting all constructors/fields/methods? [message #78590 is a reply to message #78574] |
Sun, 30 January 2005 13:35   |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
At this time we don't have a need for it so we didn't add it to the
interface. However, an IBeanTypeProxy is a proxy for the true
java.lang.Class for the type, so you can just go against the proxy for
java.lang.Class and get the method proxy for getConstructors. Then just
invoke this method proxy passing in the type proxy for the class of
interest.
Liam Morley wrote:
> Our plugin needs its own JVM. We've decided that JEM Proxy is the
> closest to what we're looking for, and we've been checking to see if it
> fits all of our needs. We're currently looking at 1.0.1, and there's one
> issue we're running into.
>
> We'd like to be able to get all of the constructors for a given class
> (Class.getConstructors()). I expected to find this in a
> IBeanTypeProxy.getConstructorProxies(), but this doesn't exist. (Same
> thing goes for fields and methods, as well as declared
> constructors/fields/methods).
>
> Is there a workaround, or is there any way to get something like this
> into a future release? If there isn't a workaround currently, we'd be
> happy to contribute a patch if you guys are on a tight schedule and
> don't mind including it.
>
--
Thanks,
Rich Kulp
|
|
|
FYI: [JEM] getting all constructors/fields/methods? [message #79902 is a reply to message #78590] |
Thu, 10 February 2005 17:42   |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
I just added these. They will be available in the next JEM/VE build.
Rich Kulp wrote:
> At this time we don't have a need for it so we didn't add it to the
> interface. However, an IBeanTypeProxy is a proxy for the true
> java.lang.Class for the type, so you can just go against the proxy for
> java.lang.Class and get the method proxy for getConstructors. Then just
> invoke this method proxy passing in the type proxy for the class of
> interest.
>
> Liam Morley wrote:
>
>> Our plugin needs its own JVM. We've decided that JEM Proxy is the
>> closest to what we're looking for, and we've been checking to see if
>> it fits all of our needs. We're currently looking at 1.0.1, and
>> there's one issue we're running into.
>>
>> We'd like to be able to get all of the constructors for a given class
>> (Class.getConstructors()). I expected to find this in a
>> IBeanTypeProxy.getConstructorProxies(), but this doesn't exist. (Same
>> thing goes for fields and methods, as well as declared
>> constructors/fields/methods).
>>
>> Is there a workaround, or is there any way to get something like this
>> into a future release? If there isn't a workaround currently, we'd be
>> happy to contribute a patch if you guys are on a tight schedule and
>> don't mind including it.
>>
>
--
Thanks,
Rich Kulp
|
|
|
Re: FYI: [JEM] getting all constructors/fields/methods? [message #82829 is a reply to message #79902] |
Tue, 08 March 2005 17:21   |
Eclipse User |
|
|
|
Originally posted by: lmorley.wpi.edu
Thanks again for your help, you've been invaluable. We successfully
implemented the suggestion you proposed in an earlier note, but we
figured that if you are in the process of adding these already, we'd let
you know what else we're making use of:) as it's probably more efficient
(from our point of view) for these things to be taken care of in the JVM
layer rather than in our plug-in. If you don't believe that the
following methods should be included, no big deal, as we're already
using the implementation method suggested earlier, but just in case
you're bored...;)
We're using:
Class.getDeclaredFields()
Class.getMethods()
Constructor.getParameterTypes()
Member.getName()
Member.getModifiers()
Rich Kulp wrote:
> I just added these. They will be available in the next JEM/VE build.
>
> Rich Kulp wrote:
>
>> At this time we don't have a need for it so we didn't add it to the
>> interface. However, an IBeanTypeProxy is a proxy for the true
>> java.lang.Class for the type, so you can just go against the proxy for
>> java.lang.Class and get the method proxy for getConstructors. Then
>> just invoke this method proxy passing in the type proxy for the class
>> of interest.
>>
>> Liam Morley wrote:
>>
>>> Our plugin needs its own JVM. We've decided that JEM Proxy is the
>>> closest to what we're looking for, and we've been checking to see if
>>> it fits all of our needs. We're currently looking at 1.0.1, and
>>> there's one issue we're running into.
>>>
>>> We'd like to be able to get all of the constructors for a given class
>>> (Class.getConstructors()). I expected to find this in a
>>> IBeanTypeProxy.getConstructorProxies(), but this doesn't exist. (Same
>>> thing goes for fields and methods, as well as declared
>>> constructors/fields/methods).
>>>
>>> Is there a workaround, or is there any way to get something like this
>>> into a future release? If there isn't a workaround currently, we'd be
>>> happy to contribute a patch if you guys are on a tight schedule and
>>> don't mind including it.
>>>
>>
>
--
Liam Morley
Computer Science Undergraduate
Worcester Polytechnic Institute
|
|
|
Re: FYI: [JEM] getting all constructors/fields/methods? [message #82844 is a reply to message #82829] |
Tue, 08 March 2005 18:49  |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Liam Morley wrote:
> Thanks again for your help, you've been invaluable. We successfully
> implemented the suggestion you proposed in an earlier note, but we
> figured that if you are in the process of adding these already, we'd let
> you know what else we're making use of:) as it's probably more efficient
> (from our point of view) for these things to be taken care of in the JVM
> layer rather than in our plug-in. If you don't believe that the
> following methods should be included, no big deal, as we're already
> using the implementation method suggested earlier, but just in case
> you're bored...;)
>
> We're using:
>>>> We've since added these due to your earlier suggestion:
> Class.getDeclaredFields()
> Class.getMethods()
>>>> IMethodProxy already had getParameterTypes, but for some reason we
>>>> forgot to do the same for IConstructorProxy.
> Constructor.getParameterTypes()
>>>> I'm not so sure about these, maybe they should be there. I'll have
to think about it.
> Member.getName()
> Member.getModifiers()
>
--
Thanks,
Rich Kulp
|
|
|
Re: [JEM] getting all constructors/fields/methods? [message #604890 is a reply to message #78574] |
Sun, 30 January 2005 13:35  |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
At this time we don't have a need for it so we didn't add it to the
interface. However, an IBeanTypeProxy is a proxy for the true
java.lang.Class for the type, so you can just go against the proxy for
java.lang.Class and get the method proxy for getConstructors. Then just
invoke this method proxy passing in the type proxy for the class of
interest.
Liam Morley wrote:
> Our plugin needs its own JVM. We've decided that JEM Proxy is the
> closest to what we're looking for, and we've been checking to see if it
> fits all of our needs. We're currently looking at 1.0.1, and there's one
> issue we're running into.
>
> We'd like to be able to get all of the constructors for a given class
> (Class.getConstructors()). I expected to find this in a
> IBeanTypeProxy.getConstructorProxies(), but this doesn't exist. (Same
> thing goes for fields and methods, as well as declared
> constructors/fields/methods).
>
> Is there a workaround, or is there any way to get something like this
> into a future release? If there isn't a workaround currently, we'd be
> happy to contribute a patch if you guys are on a tight schedule and
> don't mind including it.
>
--
Thanks,
Rich Kulp
|
|
|
FYI: [JEM] getting all constructors/fields/methods? [message #605195 is a reply to message #78590] |
Thu, 10 February 2005 17:42  |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
I just added these. They will be available in the next JEM/VE build.
Rich Kulp wrote:
> At this time we don't have a need for it so we didn't add it to the
> interface. However, an IBeanTypeProxy is a proxy for the true
> java.lang.Class for the type, so you can just go against the proxy for
> java.lang.Class and get the method proxy for getConstructors. Then just
> invoke this method proxy passing in the type proxy for the class of
> interest.
>
> Liam Morley wrote:
>
>> Our plugin needs its own JVM. We've decided that JEM Proxy is the
>> closest to what we're looking for, and we've been checking to see if
>> it fits all of our needs. We're currently looking at 1.0.1, and
>> there's one issue we're running into.
>>
>> We'd like to be able to get all of the constructors for a given class
>> (Class.getConstructors()). I expected to find this in a
>> IBeanTypeProxy.getConstructorProxies(), but this doesn't exist. (Same
>> thing goes for fields and methods, as well as declared
>> constructors/fields/methods).
>>
>> Is there a workaround, or is there any way to get something like this
>> into a future release? If there isn't a workaround currently, we'd be
>> happy to contribute a patch if you guys are on a tight schedule and
>> don't mind including it.
>>
>
--
Thanks,
Rich Kulp
|
|
|
Re: FYI: [JEM] getting all constructors/fields/methods? [message #605771 is a reply to message #79902] |
Tue, 08 March 2005 17:21  |
Eclipse User |
|
|
|
Thanks again for your help, you've been invaluable. We successfully
implemented the suggestion you proposed in an earlier note, but we
figured that if you are in the process of adding these already, we'd let
you know what else we're making use of:) as it's probably more efficient
(from our point of view) for these things to be taken care of in the JVM
layer rather than in our plug-in. If you don't believe that the
following methods should be included, no big deal, as we're already
using the implementation method suggested earlier, but just in case
you're bored...;)
We're using:
Class.getDeclaredFields()
Class.getMethods()
Constructor.getParameterTypes()
Member.getName()
Member.getModifiers()
Rich Kulp wrote:
> I just added these. They will be available in the next JEM/VE build.
>
> Rich Kulp wrote:
>
>> At this time we don't have a need for it so we didn't add it to the
>> interface. However, an IBeanTypeProxy is a proxy for the true
>> java.lang.Class for the type, so you can just go against the proxy for
>> java.lang.Class and get the method proxy for getConstructors. Then
>> just invoke this method proxy passing in the type proxy for the class
>> of interest.
>>
>> Liam Morley wrote:
>>
>>> Our plugin needs its own JVM. We've decided that JEM Proxy is the
>>> closest to what we're looking for, and we've been checking to see if
>>> it fits all of our needs. We're currently looking at 1.0.1, and
>>> there's one issue we're running into.
>>>
>>> We'd like to be able to get all of the constructors for a given class
>>> (Class.getConstructors()). I expected to find this in a
>>> IBeanTypeProxy.getConstructorProxies(), but this doesn't exist. (Same
>>> thing goes for fields and methods, as well as declared
>>> constructors/fields/methods).
>>>
>>> Is there a workaround, or is there any way to get something like this
>>> into a future release? If there isn't a workaround currently, we'd be
>>> happy to contribute a patch if you guys are on a tight schedule and
>>> don't mind including it.
>>>
>>
>
--
Liam Morley
Computer Science Undergraduate
Worcester Polytechnic Institute
|
|
|
Re: FYI: [JEM] getting all constructors/fields/methods? [message #605774 is a reply to message #82829] |
Tue, 08 March 2005 18:49  |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Liam Morley wrote:
> Thanks again for your help, you've been invaluable. We successfully
> implemented the suggestion you proposed in an earlier note, but we
> figured that if you are in the process of adding these already, we'd let
> you know what else we're making use of:) as it's probably more efficient
> (from our point of view) for these things to be taken care of in the JVM
> layer rather than in our plug-in. If you don't believe that the
> following methods should be included, no big deal, as we're already
> using the implementation method suggested earlier, but just in case
> you're bored...;)
>
> We're using:
>>>> We've since added these due to your earlier suggestion:
> Class.getDeclaredFields()
> Class.getMethods()
>>>> IMethodProxy already had getParameterTypes, but for some reason we
>>>> forgot to do the same for IConstructorProxy.
> Constructor.getParameterTypes()
>>>> I'm not so sure about these, maybe they should be there. I'll have
to think about it.
> Member.getName()
> Member.getModifiers()
>
--
Thanks,
Rich Kulp
|
|
|
Goto Forum:
Current Time: Wed Jun 04 11:43:28 EDT 2025
Powered by FUDForum. Page generated in 0.04382 seconds
|