Query about Help Needed

Nic Ferrier nferrier@tapsellferrier.co.uk
Mon Apr 2 11:31:00 GMT 2001


>>> Joerg Brunsmann <joerg_brunsmann@yahoo.de> 02-Apr-01 6:24:08 PM
>>>
>Being more concrete, the project at
> http://oje.sourceforge.net 
>tries to implement these extensions. And of course 
>there's
> http://www.classpath.org 
>Perhaps convincing and involving the author of the 
>'Open Java Extension' to move to gcj is a great goal?

Have you seen my post to Classpath about moving OJE to GNU?
I would also like to draw your attention that Andrew Selkirk of the
OJE project took on the task of producing free javax APIs - not
necessarily their implementations.
I would also like to query why you think that Classpath is
duplicating GCJ effort? Surely the GCJ java lib implementation comes
from Classpath.
>Before starting to think about such an implementation, I 
>would definitively want to suggest to clear the wanted
>packaging of such software. Bryce already mentioned 
>that the security package get's quite large. I guess the 
>extensions will be large, too. So the questions rise:
>should the extensions be supplied in a separate package?
>Should a gcj configurator (someone who does run the 
>configure script) be able to select from a set of packages?

Please see my message to the Classpath list about the OJE project.
IMHO there is *no* reason for the GCJ project to host the effort to
produce *all* the javax libs. GCJ should do what it does with the java
libs, import them from another project.
This is especially true since most javax projects are pure Java, with
no need to be tied to the GCJ platform particularly.
My own view is that the FSF should setup different projects (within
GNU) to manage the production of such libs. 
I have that view because I ask myself "why would someone working on
Swing need to be in the same project as someone working on JNDI?"
>One day a gcj compiled EJB container want to see 
>the light

GNU-Paperclips won't be EJB (unless someone other than me makes it
so) but it will be compiled with GCJ.
>It'll need jndi and rmi. So perhaps it makes sense 
>to start with the javax/naming and java.rmi and then 
>with javax/ejb ;-)

Classpath (and therefore GCJ) has the beginnings of RMI.
I am personally quite keen that someone somewhere should start a
GPLed JNDI project. When I've finished with the OJE IMAP/Javamail
stuff I'll probably start one myself. I've never implemented LDAP
before though, so I'll need help.
Nic Ferrier
Aboiut me: I'm one of the contributors to the OJE project (I'm
working on the javamail stuff, including the IMAP provider). I'm also
the maintainer of GNU-Paperclips, the GNU project servlet engine.


More information about the Java mailing list

AltStyle によって変換されたページ (->オリジナル) /