Hello,

> 1) My target platform is linux ppc or linux/zos, are there any  
> depencies to
> x86 hardware (I assume no)

You're right, no dependencies for MDweb2.

> 2) geotools is an import part of the customers GDI infrastructure,  
> he wants
> to reuse the skills (of course)

The MDweb2 core is GT based, it use the metadata GT library for the  
ISO19115 part and JaxB Un/Marshalling technology is used by the CSW  
2.0.2 to generate ISO19139 XML streams. The same approach is used for  
SensorML streams in SWE infrastructure. JaxB is the main reason of the  
"GT-2.9" fork, it was taking place in the trunk, but we removed it for  
<humor> JaxB racism reason</humor> .

Lucene geospatial enhancement is made using GT (CQL, Filter, ....) an  
then can permit spatial metadata search.

>
> 3) DB2 is a criticial point, I know I have to contribute the code,
> this should not be the problem. (I am responsible for the new jdbc-db2
> module in geotools).
> Integration into Websphere and DB2 is essential and must be evaluated
> soon.
>
>
> I am ready to contribute, btw, has anyone thought about the  
> possibility to
> put the the object model and the search logic in an ejb 3.0 container.

We looked at this few month ago, but for the reasons explained by  
Simone on the following e-mail, we wanted to be able to run MDweb2 in  
tomcat, then we decided to delay such work until EJB and Spring  
harmonize their views (who said JEE6 ?).


Cheers,

Vincent

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to