|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
Provides the ability to write Features information.
Capabilities:
false
to
allow new feature creation. These changes
One thing that is really nice about the approach to adding content is that the generation of FID is not left in the users control.
Method Summary | |
void |
close()
Release the underlying resources. |
FeatureType |
getFeatureType()
FeatureType this reader has been configured to create. |
boolean |
hasNext()
Query whether this FeatureWriter has another Feature. |
Feature |
next()
Reads a Feature from the underlying AttributeReader. |
void |
remove()
Removes current Feature, must be called before hasNext. |
void |
write()
Wrties the current Feature, must be called before hasNext. |
Method Detail |
public FeatureType getFeatureType()
public Feature next() throws java.io.IOException
This method may return a Feature even though hasNext() returns
false
, this allows FeatureWriters to provide an ability to
append content.
java.io.IOException
- DOCUMENT ME!public void remove() throws java.io.IOException
FeatureWriters will need to allow all FeatureSources of the same
typeName to issue a FeatureEvent event of type
FeatureEvent.FEATURES_REMOVED
when this method is called.
If this FeatureWriter is opperating against a Transaction FEATURES_REMOVED events should only be sent to FeatureSources operating on the same Transaction. When Transaction commit() is called other FeatureSources will be informed of the modifications.
When the current Feature has been provided as new content, this method "cancels" the add opperation (and notification needed).
java.io.IOException
- DOCUMENT ME!public void write() throws java.io.IOException
FeautreWriters will need to allow FeatureSources of the same typeName to issue a FeatureEvent:
false
.
true
and the resulting Feature has indeed been
modified.
If this FeatureWriter is opperating against a Transaction the FEATURES_MODIFIED or FEATURES_ADDED events should only be sent to FeatureSources opperating on the same Transaction. When Transaction commit() is called other FeatureSources will be informed of the modifications.
If you have not called write() when you call hasNext() or next(), no modification will occur().
java.io.IOException
public boolean hasNext() throws java.io.IOException
Please note: it is more efficient to construct your FeatureWriter with a Filer (to skip entries you do not want), than to force the creation of entire Features only to skip over them.
FeatureWriters that support append opperations will allow calls to next,
even when haveNext() returns false
.
true
if an additional Feature
is
available.
java.io.IOException
- DOCUMENT ME!public void close() throws java.io.IOException
java.io.IOException
- if there there are problems releasing underlying resources, or
possibly if close has been called (up to the implementation).
|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |