|
Deprecated Methods |
com.hp.hpl.jena.rdf.model.ModelCon.add(Resource, Property, String, String, boolean)
since Jena2. It is no longer legal to have a language
tag on a well-formed XMLLiteral. Use the 4-argument form of
add instead.
add a statement to this model. |
com.hp.hpl.jena.ontology.OntDocumentManager.addLanguageEntry(String, String)
Language determination via the ODM will be removed from Jena 2.4 onwards |
com.hp.hpl.jena.graph.query.Query.addMatch(String, Node, Node, Node)
named triple patterns are not supported |
com.hp.hpl.jena.ontology.OntDocumentManager.addPrefixMapping(String, String)
Prefix management via the ODM is very likely to be removed from Jena 2.4 onwards |
com.hp.hpl.jena.rdf.model.Statement.changeObject(boolean)
use changeLiteralObject etc |
com.hp.hpl.jena.rdf.model.Statement.changeObject(double)
use changeLiteralObject etc |
com.hp.hpl.jena.rdf.model.Statement.changeObject(float)
use changeLiteralObject etc |
com.hp.hpl.jena.rdf.model.Statement.changeObject(long)
use changeLiteralObject etc |
com.hp.hpl.jena.rdf.model.Statement.changeObject(Object)
use changeLiteralObject etc |
com.hp.hpl.jena.db.ModelRDB.clear()
Since Jena 2.0 this call is not recommended (it's name
is misleading) - to clear an entire database use DBConnection.cleanDB,
to remove just this Model use Model.remove(). |
com.hp.hpl.jena.rdf.arp.ARPOptions.copy()
Not intended for public use, will be removed from API |
com.hp.hpl.jena.db.ModelRDB.create(IDBConnection, String)
Since Jena 2.0 this call is no longer needed - it is preferable to
specify the database type when constructing the DBConnection. Then use the call
ModelRDB.createModel(IDBConnection) |
com.hp.hpl.jena.db.ModelRDB.create(IDBConnection, String, String)
Since Jena 2.0 this call is no longer needed - it is preferable
to specify the database type when constructing the DBConnection and to modify
the layout by using the properties in the DBConnection. Then use the
call ModelRDB.createModel(IDBConnection) |
com.hp.hpl.jena.graph.Node.create(PrefixMapping, String)
Use NodeCreateUtils.create(PrefixMapping,String) instead |
com.hp.hpl.jena.graph.Node.create(String)
Use NodeCreateUtils.create(String) instead |
com.hp.hpl.jena.db.ModelRDB.deleteModel(IDBConnection, String)
Since Jena 2.0, to remove a model use the ModelRDB.remove() |
com.hp.hpl.jena.util.FileUtils.encodeFileName(String)
Broken: use toURL() |
com.hp.hpl.jena.ontology.OntDocumentManager.getDeclaredPrefixMapping()
Prefix management via the ODM is very likely to be removed from Jena 2.4 onwards |
com.hp.hpl.jena.db.IDBConnection.getDriver(String, String)
As of Jena 2.0 this call should not be used. Instead specify the database type
when constructing a DBConnection and then pass that connection to the GraphRDB. There is
no longer any need for applications to interact with the IRDBDriver. To customize the
database configuration/layout use the formatDB(propertyModel) call. |
com.hp.hpl.jena.db.DBConnection.getDriver(String, String)
As of Jena 2.0 this call should not be used. Instead specify the database type
when constructing a DBConnection and then pass that connection to the GraphRDB. There is
no longer any need for applications to interact with the IRDBDriver. To customize the
database configuration/layout use the formatDB(propertyModel) call. |
com.hp.hpl.jena.ontology.OntDocumentManager.getLanguage(String)
Language determination via the ODM will be removed from Jena 2.4 onwards |
com.hp.hpl.jena.ontology.OntModel.getModelMaker()
use getImportModelMaker instead for consistency with name
changes to OntModelSpec to avoid ambiguity with base vs import makers. |
com.hp.hpl.jena.rdf.model.Resource.getNode()
use asNode(). |
com.hp.hpl.jena.rdf.model.JenaConfig.getOldLiteralCompare()
this functionality is temporary |
com.hp.hpl.jena.ontology.OntDocumentManager.getPrefixForURI(String)
Prefix management via the ODM is very likely to be removed from Jena 2.4 onwards |
com.hp.hpl.jena.graph.query.Query.getTriples()
use getPattern for the raw triples |
com.hp.hpl.jena.ontology.OntDocumentManager.getURIForPrefix(String)
Prefix management via the ODM is very likely to be removed from Jena 2.4 onwards |
com.hp.hpl.jena.rdf.model.Literal.getWellFormed()
use isWellFormedXML instead. |
com.hp.hpl.jena.util.ModelLoader.guessLang(String)
Use FileUtils.guessLang |
com.hp.hpl.jena.util.ModelLoader.guessLang(String, String)
Use FileUtils.guessLang |
com.hp.hpl.jena.ontology.OntModel.listImportedModels()
This method has been re-named to listSubModels,
but note that to obtain the same behaviour as listImportedModels
from Jena 2.4 and earlier, callers should invoke OntModel.listSubModels(boolean)
with parameter true. |
com.hp.hpl.jena.db.ModelRDB.loadAll()
Since Jena 2.0, this call is not recommended. Instead use
the soon-to-be-released bulk-load functions. |
com.hp.hpl.jena.assembler.AssemblerHelp.loadClasses(AssemblerGroup, Model)
Use loadAssemblerClasses instead
(since it's explicit in what kinds of classes it loads). |
com.hp.hpl.jena.util.ModelLoader.loadModel(Model, String)
Use FileManager.get().readModel(model, urlStr) instead |
com.hp.hpl.jena.util.ModelLoader.loadModel(Model, String, String)
Use FileManager.get().readModel(model, urlStr, lang) instead |
com.hp.hpl.jena.util.ModelLoader.loadModel(String)
Use FileManager.get().loadModel(urlStr) |
com.hp.hpl.jena.util.ModelLoader.loadModel(String, String)
Use FileManager.get().loadModel(urlStr, lang) |
com.hp.hpl.jena.reasoner.rulesys.Util.loadResourceFile(String)
Use loadRuleParserFromResourceFile |
com.hp.hpl.jena.rdf.arp.SAX2RDF.newInstance(String)
Use SAX2RDF.create(String). |
com.hp.hpl.jena.rdf.arp.SAX2Model.newInstance(String, Model)
Use SAX2Model.create(String, Model) |
com.hp.hpl.jena.rdf.arp.SAX2Model.newInstance(String, Model, String)
Use SAX2Model.create(String, Model, String) |
com.hp.hpl.jena.rdf.arp.SAX2RDF.newInstance(String, String)
Use SAX2RDF.create(String,String). |
com.hp.hpl.jena.util.FileManager.remap(String)
Use mapURI |
com.hp.hpl.jena.rdf.model.RDFList.removeAll()
Replaced by RDFList.removeList() |
com.hp.hpl.jena.reasoner.rulesys.Rule.rulesStringFromReader(BufferedReader)
Use rulesParserFromReader |
com.hp.hpl.jena.rdf.arp.ARP.setDefaultErrorMode()
Use ARP.getOptions().setDefaultErrorMode() |
com.hp.hpl.jena.rdf.arp.ARP.setEmbedding(boolean)
Use ARP.getOptions().setEmbedding(embed) |
com.hp.hpl.jena.rdf.arp.ARP.setErrorHandler(ErrorHandler)
Use ARP.getHandlers().setErrorHandler(eh) |
com.hp.hpl.jena.rdf.arp.ARP.setErrorMode(int, int)
Use ARP.getOptions().setErrorMode(errno,mode) |
com.hp.hpl.jena.rdf.arp.ARP.setExtendedHandler(ExtendedHandler)
Use ARP.getHandlers().setExtendedHandler(eh) |
com.hp.hpl.jena.rdf.arp.ARP.setLaxErrorMode()
Use ARP.getOptions().setLaxErrorMode() |
com.hp.hpl.jena.util.FileManager.setMapper(LocationMapper)
Use setLocationMapper |
com.hp.hpl.jena.rdf.arp.ARP.setNamespaceHandler(NamespaceHandler)
Use ARP.getHandlers().setNamespaceHandler(nh) |
com.hp.hpl.jena.rdf.model.JenaConfig.setOldLiteralCompare(boolean)
this functionality is temporary |
com.hp.hpl.jena.rdf.arp.ARP.setStatementHandler(StatementHandler)
Use ARP.getHandlers().setStatementHandler(sh) |
com.hp.hpl.jena.rdf.arp.ARP.setStrictErrorMode()
Use ARP.getOptions().setStrictErrorMode() |
com.hp.hpl.jena.rdf.arp.ARP.setStrictErrorMode(int)
Use ARP.getOptions().setStrictErrorMode(nonErrorMode) |
com.hp.hpl.jena.ontology.OntDocumentManager.setUseDeclaredPrefixes(boolean)
Prefix management via the ODM is very likely to be removed from Jena 2.4 onwards |
com.hp.hpl.jena.ontology.OntDocumentManager.useDeclaredPrefixes()
Prefix management via the ODM is very likely to be removed from Jena 2.4 onwards |
com.hp.hpl.jena.rdf.arp.JenaReader.useMe(Model)
This is the default behaviour |
|
Deprecated Constructors |
com.hp.hpl.jena.rdf.arp.ARPHandlers()
Use ARPConfig.getHandlers() |
com.hp.hpl.jena.rdf.arp.ARPOptions()
Use ARPConfig.getOptions() |
com.hp.hpl.jena.db.DBConnection(Connection)
As of Jena 2.0, it is recommended to use one of the DBConnection
constructors which takes a database type as an argument. (The DBConnection can
operate more efficiently if it knows the database type). |
com.hp.hpl.jena.db.DBConnection(String, String, String)
As of Jena 2.0, it is recommended to use one of the DBConnection
constructors which takes a database type as an argument. (The DBConnection can
operate more efficiently if it knows the database type). |
com.hp.hpl.jena.rdf.arp.DOM2Model(String, Model)
Use DOM2Model.createD2M(String, Model) |
com.hp.hpl.jena.rdf.arp.DOM2Model(String, Model, String)
Use DOM2Model.createD2M(String, Model, String) |
com.hp.hpl.jena.db.GraphRDB(IDBConnection, String, Graph, boolean)
Please use the alternate constructor and choose the desired
reification behaviour. |
com.hp.hpl.jena.db.ModelRDB(IDBConnection)
Since Jena 2.0, this call is not recommended -
in the short-term use ModelRDB.open or ModelRDB.createModel;
in the longer-term use factory methods to construct persistent models. |
com.hp.hpl.jena.db.ModelRDB(IDBConnection, String)
Since Jena 2.0, this call is not recommended -
in the short-term use ModelRDB.open or ModelRDB.createModel;
in the longer-term use factory methods to construct persistent models. |