Just a follow-up to the group.  Let me set some accountability for
myself.  I'll definitely go back and contribute to the Wiki.  As of
yet, I am still learning my way, and getting more comfortable.  I
intend to go back and help add to some documentation -- (i.e. beginner
user ...how to create your own datastore...things to look out for,
etc.)  If I don't, call me out on it..and I will.

The problem that was solved -- not sure I have a good answer.  The
solution doesn't make a lot of sense to me, which is why I don't want
to add this to the wiki...but here were my steps.

The feature and the feature type had attributes of type java.lang.Integer
The attribute type exception was being thrown complaining it expected
long, but got java.lang.Long

In typical hacking fashion, I changed all the attribute types to
primitive int to see what would happen.  When I did this, more
attribute type exceptions were thrown that said it expected
java.lang.Integer, but got int (the long execption went away).

So, in more typical hacking fashion, I changed the attribute types
back to java.lang.Integer (i.e. back to square one), and suddenly a
map was displayed for me.

I don't know why this solved anything, but my guess is that somehow,
the feature type and the feature were not aligned.  However, the
feature type is generated via reflection (I am fixing this), so it
should never have been mis-aligned.

As a follow-up, I would like to have the feature type be generated
from an XSD file that is read in.  I intend to either implement the
FeatureType interface and use the create method for this, or implement
the FeatureFactory interface and use the create method for this.  I am
trending toward the former, b/c this way, I can guarantee the schema
will be in line.

To that note, if I intend on building the feature type from reading in
an XSD, where should this be implemented?  What interface/subclass
should actually do this, so it is persistent and flexible.  I want to
do this only one time (singleton)?  Any help?

Regards,
Davis




On 12/23/05, Chris Holmes <[EMAIL PROTECTED]> wrote:
> Out of curiosity, what was the problem?  If you have a bit of time it'd
> be a great way to contribute back to GeoServer if you could document
> some of the problems you ran into, and how you solved them.  I just
> made the Use Narrative section:
> http://docs.codehaus.org/display/GEOSDOC/Use+Narrative where you can
> informally just write about the experience of implementing a new
> datastore.  Or you as this is sort of more of a 'developer' task, you
> could add a section under Hints and Tricks.
>
> thanks,
>
> Chris
>
> Quoting Davis Ford <[EMAIL PROTECTED]>:
>
> > Hi Justin, I fixed it.  WMS is working now for our datastore.
> >
> > Thx,
> > Davis
> >
> > On 12/22/05, Justin Deoliveira <[EMAIL PROTECTED]> wrote:
> > > Hi Davis,
> > >
> > > Can you turn on logging to disk (Config->Server)
> > >
> > > and re-exercise the problem.
> > >
> > > The full stack trace should show up in the log.
> > >
> > > -Justin
> > >
> > > Davis Ford wrote:
> > > > Hi, when trying to display WMS via
> > > >
> > > >
> >
> http://localhost:8090/geoserver/wms?version=1.3.0&request=GetMap&layers=teleatlas:RoadElement&BBOX=5.7,49.4,6.5,50.1&srs=EPSG:4326&width=300&height=300&format=image/png&STYLES=simple_roads
> > > >
> > > > The layer refers to our own datastore.
> > > >
> > > > I am seeing the following error:
> > > >
> > > >
> > org.geotools.renderer.lite.StreamingRenderer$DefaultRenderListener -
> > > > expected long, but got java.lang.Long
> > > >
> > > > ..and a blank .png image comes back.
> > > >
> > > > Does anyone have an idea why this may be occurring -- I don't
> > believe
> > > > I even have Long as a type in this feature, or in the FeatureType
> > > > schema.
> > > >
> > > > Reagards,
> > > > Davis
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This SF.net email is sponsored by: Splunk Inc. Do you grep
> > through log files
> > > > for problems?  Stop!  Download the new AJAX search engine that
> > makes
> > > > searching your log files as easy as surfing the  web.  DOWNLOAD
> > SPLUNK!
> > > > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
> > > > _______________________________________________
> > > > Geotools-gt2-users mailing list
> > > > [email protected]
> > > > https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
> > > >
> > >
> > >
> > > --
> > > Justin Deoliveira
> > > The Open Planning Project
> > > http://topp.openplans.org
> > >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through
> > log files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD
> > SPLUNK!
> > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
> > _______________________________________________
> > Geotools-gt2-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
> >
>
>
>
>
> ----------------------------------------------------------
> This mail sent through IMP: https://webmail.limegroup.com/
>


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Reply via email to