org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.

[OSIR-DLKV]

Hi,

very nice solution, but I'm having problems with testing it.

For any SQL query, for example:

select order_number from doo_headers_all where rownum = 1

I receive this error:

org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
at java.xml/com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at java.xml/com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at my.jdbc.wsdl_driver.UtilsKt.parseXml(Utils.kt:108)
at my.jdbc.wsdl_driver.UtilsKt.sendSqlViaWsdl(Utils.kt:173)
at my.jdbc.wsdl_driver.WsdlDatabaseMetaData.getTables(WsdlDatabaseMetaData.kt:378)
at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCDatabaseMetaDataImpl.getTables(JDBCDatabaseMetaDataImpl.java:1116)
at org.jkiss.dbeaver.ext.generic.model.meta.GenericMetaModel.prepareTableLoadStatement(GenericMetaModel.java:571)
at org.jkiss.dbeaver.ext.generic.model.TableCache.prepareLookupStatement(TableCache.java:62)
at org.jkiss.dbeaver.ext.generic.model.TableCache.prepareLookupStatement(TableCache.java:1)
at org.jkiss.dbeaver.model.impl.jdbc.cache.JDBCStructLookupCache.prepareObjectsStatement(JDBCStructLookupCache.java:155)
at org.jkiss.dbeaver.model.impl.jdbc.cache.JDBCObjectCache.loadObjects(JDBCObjectCache.java:113)
at org.jkiss.dbeaver.model.impl.jdbc.cache.JDBCObjectCache.getAllObjects(JDBCObjectCache.java:76)
at org.jkiss.dbeaver.ext.generic.model.GenericObjectContainer.cacheStructure(GenericObjectContainer.java:243)
at org.jkiss.dbeaver.ext.generic.model.GenericDataSource.cacheStructure(GenericDataSource.java:727)
at org.jkiss.dbeaver.model.sql.SQLSearchUtils.findNestedObject(SQLSearchUtils.java:240)
at org.jkiss.dbeaver.model.sql.SQLSearchUtils.findObjectByPath(SQLSearchUtils.java:189)
at org.jkiss.dbeaver.model.sql.SQLSearchUtils.findObjectByFQN(SQLSearchUtils.java:124)
at org.jkiss.dbeaver.model.sql.SQLSearchUtils.findObjectByFQN(SQLSearchUtils.java:54)
at org.jkiss.dbeaver.model.sql.semantics.context.SQLQueryDataSourceContext.findRealObjectImpl(SQLQueryDataSourceContext.java:110)
at org.jkiss.dbeaver.model.sql.semantics.context.SQLQueryDataSourceContext.findRealTable(SQLQueryDataSourceContext.java:92)
at org.jkiss.dbeaver.model.sql.semantics.context.SQLQuerySyntaxContext.findRealTable(SQLQuerySyntaxContext.java:61)
at org.jkiss.dbeaver.model.sql.semantics.context.SQLQueryDataContext.resolveSource(SQLQueryDataContext.java:106)
at org.jkiss.dbeaver.model.sql.semantics.context.SQLQuerySyntaxContext.resolveSource(SQLQuerySyntaxContext.java:101)
at org.jkiss.dbeaver.model.sql.semantics.model.select.SQLQueryRowsTableDataModel.propagateContextImpl(SQLQueryRowsTableDataModel.java:250)
at org.jkiss.dbeaver.model.sql.semantics.model.select.SQLQueryRowsSourceModel.propagateContext(SQLQueryRowsSourceModel.java:107)
at org.jkiss.dbeaver.model.sql.semantics.model.select.SQLQueryRowsProjectionModel.propagateContextImpl(SQLQueryRowsProjectionModel.java:165)
at org.jkiss.dbeaver.model.sql.semantics.model.select.SQLQueryRowsSourceModel.propagateContext(SQLQueryRowsSourceModel.java:107)
at org.jkiss.dbeaver.model.sql.semantics.model.select.SQLQueryRowsSourceModel.applyContext(SQLQueryRowsSourceModel.java:95)
at org.jkiss.dbeaver.model.sql.semantics.model.SQLQueryModel.propagateContext(SQLQueryModel.java:100)
at org.jkiss.dbeaver.model.sql.semantics.SQLQueryModelRecognizer.recognizeQuery(SQLQueryModelRecognizer.java:170)
at org.jkiss.dbeaver.model.sql.semantics.SQLQueryModelRecognizer.recognizeQuery(SQLQueryModelRecognizer.java:1058)
at org.jkiss.dbeaver.ui.editors.sql.semantics.SQLBackgroundParsingJob.doWork(SQLBackgroundParsingJob.java:591)
at org.jkiss.dbeaver.ui.editors.sql.semantics.SQLBackgroundParsingJob$1.run(SQLBackgroundParsingJob.java:83)
at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:119)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

If i try to run the query directly in report it works correclty:

SOAP UI also return 200 OK:

[krokozyab]

Hi!
I's your Fusion instance is front-ended by an SSO gateway?

if your Fusion instance is front-ended by an SSO gateway, any unauthenticated call to the WSDL URL will be redirected to an HTML login page (or SAML handshake), not the raw ?WSDL XML. The driver then sees that HTML and blows up with “Content is not allowed in prolog.”

Use a non-SSO service account
Create (or ask your Fusion admin for) a dedicated “API user” on Fusion Cloud that isn’t forced through your SSO provider, and enable Basic-Auth on the report WSDL. Then point your JDBC URL at that user’s credentials.

Whitelist the reporting service
In Fusion’s security settings you can exempt the /xmlpserver/services/ExternalReportWSSService?WSDL endpoint from SSO, allowing direct Basic-Auth.

Until the driver can fetch the raw XML (not an HTML login page), you’ll keep seeing that SAX “prolog” error.

[OSIR-DLKV]

SSO is not enabled on this Fusion instance. But then I switched accounts as you mention to an "integration account" which we are using and it's working now.

I guess the problem is that the other account is used (same username) for other services which is then authenticated through IAM (VB, OIC etc.).

Thanks, this looks great for now.

[krokozyab]

keep it open for future reference