Hello List,
Recently we added a new DXF module to the Geotools project as a ‘unsupported’ module.
Andrea asked me te make a geoserver extension for it. (as community module?) Of course i will do that but how?? Is there some documentation about creating a new geoserver extension?
Roy
Roy Braam ha scritto:
Hello List,
Recently we added a new DXF module to the Geotools project as a 'unsupported' module.
Andrea asked me te make a geoserver extension for it. (as community module?) Of course i will do that but how?? Is there some documentation about creating a new geoserver extension?
Ha ha, well, I _suggested_ to make it a module, I did not really ask :-p
Anyways, I don't think we have documents on how to do that, it has been
done quite ad-hoc so far, but I think you can play "monkey see, monkey do" using another pure datastore extension like db2. Here are some places you should look into:
http://svn.codehaus.org/geoserver/trunk/src/extension/pom.xml
http://svn.codehaus.org/geoserver/trunk/src/extension/db2/
http://svn.codehaus.org/geoserver/trunk/src/pom.xml
http://svn.codehaus.org/geoserver/trunk/src/release/pom.xml
http://svn.codehaus.org/geoserver/trunk/src/release/ext-db2.xml
And eventually add a profile to:
http://svn.codehaus.org/geoserver/trunk/src/web/app/pom.xml
so that the datastore gets included in GeoServer .war or
in your IDE projects when you add the -Pdxf option to your build.
Now, there is a catch... extensions do require some people using
them before they get to be extensions.
For the moment your dxf datastore is only in Geotools trunk and
in unsupported land.
This is kind of a new situation, not sure how to handle it, but
I sure would love to see more stores in GeoServer (that's
why I suggested you get involved in the first place 
).
Soo... people, what do you say? What's the best way to get
the user base to know and test this new store?
I guess a blog post is a good way, just tell people the store
is there and give them a jar and instructions on how to
download a GS trunk build, a zip containing the extra jars
needed by the store... and well, that should be it.
Ah btw, Roy, Mauro Bartolomeoli time ago contributed
a dxf output format to GeoServer that can be found here:
http://svn.codehaus.org/geoserver/trunk/src/community/dxf/
(for some reason it never made into extensions).
An output format will just turn features into a dxf
file, so it's somehow part of the functionality of a
full store.
It seems like an occasion to merge the two works?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea,
Yep, your right, you suggested it.
I’ll have a look at the url’s you gave me, thanks!
Roy
From: Andrea Aime [mailto:aaime@…1501…]
To: Roy Braam [mailto:roybraam@anonymised.com]
Cc: Geoserver-devel@lists.sourceforge.net, Mauro Bartolomeoli [mailto:m.bartolomeoli@anonymised.com]
Sent: Mon, 03 May 2010 11:23:30 +0200
Subject: Re: [Geoserver-devel] Dxf module/extensionRoy Braam ha scritto:
Hello List,
Recently we added a new DXF module to the Geotools project as a
‘unsupported’ module.
Andrea asked me te make a geoserver extension for it. (as community
module?) Of course i will do that but how?? Is there some documentation
about creating a new geoserver extension?Ha ha, well, I suggested to make it a module, I did not really ask :-p
Anyways, I don’t think we have documents on how to do that, it has been
done quite ad-hoc so far, but I think you can play “monkey see, monkey
do” using another pure datastore extension like db2. Here are some
places you should look into:http://svn.codehaus.org/geoserver/trunk/src/extension/pom.xml
http://svn.codehaus.org/geoserver/trunk/src/extension/db2/
http://svn.codehaus.org/geoserver/trunk/src/pom.xml
http://svn.codehaus.org/geoserver/trunk/src/release/pom.xml
http://svn.codehaus.org/geoserver/trunk/src/release/ext-db2.xmlAnd eventually add a profile to:
http://svn.codehaus.org/geoserver/trunk/src/web/app/pom.xmlso that the datastore gets included in GeoServer .war or
in your IDE projects when you add the -Pdxf option to your build.Now, there is a catch… extensions do require some people using
them before they get to be extensions.
For the moment your dxf datastore is only in Geotools trunk and
in unsupported land.This is kind of a new situation, not sure how to handle it, but
I sure would love to see more stores in GeoServer (that’s
why I suggested you get involved in the first placeSoo… people, what do you say? What’s the best way to get
the user base to know and test this new store?
I guess a blog post is a good way, just tell people the store
is there and give them a jar and instructions on how to
download a GS trunk build, a zip containing the extra jars
needed by the store… and well, that should be it.Ah btw, Roy, Mauro Bartolomeoli time ago contributed
a dxf output format to GeoServer that can be found here:
http://svn.codehaus.org/geoserver/trunk/src/community/dxf/
(for some reason it never made into extensions).An output format will just turn features into a dxf
file, so it’s somehow part of the functionality of a
full store.
It seems like an occasion to merge the two works?Cheers
Andrea–
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Ah btw, Roy, Mauro Bartolomeoli time ago contributed
a dxf output format to GeoServer that can be found here:
http://svn.codehaus.org/geoserver/trunk/src/community/dxf/
(for some reason it never made into extensions).
Just no time to do the job of promoting it to an extension.
An output format will just turn features into a dxf
file, so it's somehow part of the functionality of a
full store.
It seems like an occasion to merge the two works?
I agree, it would be a good thing. If you need any help for the merge let me know.
Mauro
On 05/03/2010 05:23 AM, Andrea Aime wrote:
This is kind of a new situation, not sure how to handle it, but
I sure would love to see more stores in GeoServer (that's
why I suggested you get involved in the first place:-) ).
Wouldn't the existing community module system be applicable in this case? You get nightly builds and a well-defined section of the docs that way.
--
David Winslow
OpenGeo - http://opengeo.org/
David Winslow ha scritto:
On 05/03/2010 05:23 AM, Andrea Aime wrote:
This is kind of a new situation, not sure how to handle it, but
I sure would love to see more stores in GeoServer (that's
why I suggested you get involved in the first place:-) ).
Wouldn't the existing community module system be applicable in this case? You get nightly builds and a well-defined section of the docs that way.
Yep. I guess the main difference is that the assembly
descriptors are listed in community/pom.xml instead of
the main pom.xml, right?
http://svn.codehaus.org/geoserver/trunk/src/community/pom.xml
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.