Re: Change JavaXPCOM interfaces package name?

Micael Gallego Carrillo <[email protected]>
Newsgroups gmane.comp.mozilla.devel.java
Message-ID <v-2dnQYCQItRx9zYnZ2dnUVZ_tGdnZ2d__46352.5235107683$1161911805$gmane$org@mozilla.org>
Hello Javier,

I think that changing package name from "org.mozilla.xpcom" to 
"org.mozilla.interfaces" is a good idea. But, as you say, the best 
solution is improve xpidl tool to process namespaces correctly.

It is possible to generate JavaDoc files for interfaces and publish it 
on-line in Mozilla Servers?? Can be very useful for Java developers.

Regards...

Micael Gallego

Javier Pedemonte escribió:
> Currently, all of the generated Mozilla interfaces are put in the 
> package "org.mozilla.xpcom".  In 
> https://bugzilla.mozilla.org/show_bug.cgi?id=330256, I tried to come up 
> with a better solution.
> 
> Ideally, the interfaces should their own package; as in 
> "org.mozilla.network", "org.mozilla.dom", "com.foo.bar" (as in a company 
> called Foo that wishes to release a Bar extension).  Unfortunately, 
> while XPIDL (the Mozilla interface language) has support for 
> 'namespaces', xpidl (the tool for processing Mozilla interfaces) assumes 
> a flat namespace.  So this solution is not viable at the moment.
> 
> Instead, I propose changing the package name to the more generic 
> "org.mozilla.interfaces".  That way, all the interfaces, including those 
> by a 3rd party, don't get lumped under 'xpcom'.  The Mozilla class and 
> related classes would stay under "org.mozilla.xpcom".
> 
> For those of you who have used JavaXPCOM, does this sound good?  Please 
> let me know.
> 
> 
> javier pedemonte
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.