Eclipse Community Forums: BIRT » http 401 error (xml data source) with viewer deployed in tomcat

Home » Archived » BIRT » http 401 error (xml data source) with viewer deployed in tomcat

http 401 error (xml data source) with viewer deployed in tomcat [message #363465]

Tue, 24 June 2008 19:33

Eclipse User

Originally posted by: keitha.spam.gmail.com

I have created a simple report with an XML data source.

The URL for the data source is in this format:
http://servername/origen.web.live/default.aspx?cmd=@web.xml& amp;file=CS.PARCEL&ID=0940/5

When I paste this URL into my browser (IE7) it returns the XML correctly.

When I develop the report in BIRT RCP Designer 2.3RC3 it returns the XML
correctly. I created a simple report with a single table and it is working
fine (in report designer).

Now I have just done a fresh install of tomcat 5.5 on my development
machine (Windows XP) and installed viewer birt-runtime-2.3RC4. (I
validated the install by testing the sample reports and they worked fine).
Then I copied my test report into the viewer directory and tried to run
the report using the following URL:

http://localhost:8080/birt-viewer/run?__report=report\Ozone% 20Business%20Object.rptdesign

When I do this I get the following error:

Table (id = 8):
- Cannot execute the statement.
Server returned HTTP response code: 401 for URL:
http://servername/origen.web.live/default.aspx?cmd=@web.xml& amp;file=CS.PARCEL&ID=0940/5
odaconsumer.CannotExecuteStatement ( 1 time(s) )
etc. etc.

As my report was working fine in birt designer I can only assume there is
a security setting somewhere in tomcat that is causing this problem.

So, apologies for posting a tomcat configuration question on the birt
list, but how can I easily fix this?
(The report is for proof of concept for birt only, so I do not actually
wish to restrict access to who can run the report).

Thanks in advance
Keith

Re: http 401 error (xml data source) with viewer deployed in tomcat [message #363468 is a reply to message #363465]

Tue, 24 June 2008 21:44

Eclipse User

Hi Keith

I got the same issue, it works in designer bug failed in deployment
please try this xml url which I used:
https://bugs.eclipse.org/bugs/attachment.cgi?id=79863

If you can reproduce it by this url it should be a bug. Please log a bug
on bugzilla

Thanks

Tianli

Re: http 401 error (xml data source) with viewer deployed in tomcat [message #363469 is a reply to message #363468]

Tue, 24 June 2008 22:55

Eclipse User

Originally posted by: keitha.spam.gmail.com

Hi Tianli

I created a data source using the url which you supplied. (I tried 'Test
Connection') and got the message 'Ping succeeded'.

However when I tried to create a data set using this data source I got the
following error:

XML data source cannot be retrieved. XML data source is invalid or the
file doesn't exist.

Details:
org.eclipse.datatools.connectivity.oda.OdaException: XML data source
cannot be retrieved.XML data source file is invalid or the file doesn't
exist.
at
org.eclipse.datatools.enablement.oda.xml.ui.wizards.XPathCho osePage.populateXMLTree(XPathChoosePage.java:320)
at
org.eclipse.datatools.enablement.oda.xml.ui.wizards.XPathCho osePage.createPageCustomControl(XPathChoosePage.java:98)
at
org.eclipse.datatools.connectivity.oda.design.ui.wizards.Dat aSetWizardPage.createControl(DataSetWizardPage.java:123)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.ja va:170)
at
org.eclipse.jface.wizard.WizardDialog.createPageControls(Wiz ardDialog.java:669)
at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog .java:1083)
at
org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDi alog.java:1142)
at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog. java:1139)
at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.jav a:1128)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog. java:1126)
at
org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDial og.java:820)
at
org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:369)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.jav a:624)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:227)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3821)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3420)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825 )
at org.eclipse.jface.window.Window.open(Window.java:801)
at
org.eclipse.birt.report.designer.ui.actions.NewDataSetAction .createNewDataSet(NewDataSetAction.java:185)
at
org.eclipse.birt.report.designer.ui.actions.NewDataSetAction .run(NewDataSetAction.java:170)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:583)
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:500)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3821)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3420)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.birt.report.designer.ui.rcp.DesignerApplication. run(DesignerApplication.java:38)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.eclipse.equinox.internal.app.EclipseAppContainer.callMet hodWithException(EclipseAppContainer.java:574)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:195)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

I know the structure of the XML file you gave me is OK as I also saved a
local copy to run the test and that worked fine.

So I am not actually able to run the test you asked me to check.

Thanks
Keith

Tianli wrote:

> Hi Keith

> I got the same issue, it works in designer bug failed in deployment
> please try this xml url which I used:
> https://bugs.eclipse.org/bugs/attachment.cgi?id=79863

> If you can reproduce it by this url it should be a bug. Please log a bug
> on bugzilla

> Thanks

> Tianli

Re: http 401 error (xml data source) with viewer deployed in tomcat [message #363506 is a reply to message #363469]

Wed, 25 June 2008 18:25

Eclipse User

Originally posted by: keitha.spam.gmail.com

I retried the test you asked me to do at home and it worked perfectly.
I used https://bugs.eclipse.org/bugs/attachment.cgi?id=79863 as the URL
for my datasource, created a report in RCP designer, deploy to tomcat and
it worked fine.

I think maybe my original problem is that IIS is serving the XML and maybe
it is needing some credentials? I will see if I can retest by using the
URL in firefox later.

But even if it is an IIS problem the fact still remains that everything is
working fine in in the designer, it is only deploying to the birt viewer
in tomcat that is giving me the problem.

Any suggestions still gratefully received.

Keith

keitha wrote:

> Hi Tianli

> I created a data source using the url which you supplied. (I tried 'Test
> Connection') and got the message 'Ping succeeded'.

> However when I tried to create a data set using this data source I got the
> following error:

> XML data source cannot be retrieved. XML data source is invalid or the
> file doesn't exist.

> Details:
> org.eclipse.datatools.connectivity.oda.OdaException: XML data source
> cannot be retrieved.XML data source file is invalid or the file doesn't
> exist.
> at
>
org.eclipse.datatools.enablement.oda.xml.ui.wizards.XPathCho osePage.populateXMLTree(XPathChoosePage.java:320)
> at
>
org.eclipse.datatools.enablement.oda.xml.ui.wizards.XPathCho osePage.createPageCustomControl(XPathChoosePage.java:98)
> at
>
org.eclipse.datatools.connectivity.oda.design.ui.wizards.Dat aSetWizardPage.createControl(DataSetWizardPage.java:123)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.ja va:170)
> at
>
org.eclipse.jface.wizard.WizardDialog.createPageControls(Wiz ardDialog.java:669)
> at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog .java:1083)
> at
> org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDi alog.java:1142)
> at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog. java:1139)
> at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.jav a:1128)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog. java:1126)
> at
> org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDial og.java:820)
> at
> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:369)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.jav a:624)
> at
> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:227)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3821)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3420)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825 )
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at
>
org.eclipse.birt.report.designer.ui.actions.NewDataSetAction .createNewDataSet(NewDataSetAction.java:185)
> at
>
org.eclipse.birt.report.designer.ui.actions.NewDataSetAction .run(NewDataSetAction.java:170)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
> at
>
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:583)
> at
>
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:500)
> at
>
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3821)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3420)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
>
org.eclipse.birt.report.designer.ui.rcp.DesignerApplication. run(DesignerApplication.java:38)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
>
org.eclipse.equinox.internal.app.EclipseAppContainer.callMet hodWithException(EclipseAppContainer.java:574)
> at
>
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:195)
> at
>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
> at
>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

> I know the structure of the XML file you gave me is OK as I also saved a
> local copy to run the test and that worked fine.

> So I am not actually able to run the test you asked me to check.

> Thanks
> Keith

> Tianli wrote:

>> Hi Keith

>> I got the same issue, it works in designer bug failed in deployment
>> please try this xml url which I used:
>> https://bugs.eclipse.org/bugs/attachment.cgi?id=79863

>> If you can reproduce it by this url it should be a bug. Please log a bug
>> on bugzilla

>> Thanks

>> Tianli

Re: http 401 error (xml data source) with viewer deployed in tomcat [message #363509 is a reply to message #363506]

Wed, 25 June 2008 20:44

Eclipse User

Originally posted by: keitha.spam.gmail.com

OK, I found a workaround.

To start tomcat I run tomcat5.exe from the command line (instead of
running as a service where it is running as user SYSTEM). Once tomcat is
running as me the birt report displays just fine.

keitha wrote:

> I retried the test you asked me to do at home and it worked perfectly.
> I used https://bugs.eclipse.org/bugs/attachment.cgi?id=79863 as the URL
> for my datasource, created a report in RCP designer, deploy to tomcat and
> it worked fine.

> I think maybe my original problem is that IIS is serving the XML and maybe
> it is needing some credentials? I will see if I can retest by using the
> URL in firefox later.

> But even if it is an IIS problem the fact still remains that everything is
> working fine in in the designer, it is only deploying to the birt viewer
> in tomcat that is giving me the problem.

> Any suggestions still gratefully received.

> Keith

> keitha wrote:

>> Hi Tianli

>> I created a data source using the url which you supplied. (I tried 'Test
>> Connection') and got the message 'Ping succeeded'.

>> However when I tried to create a data set using this data source I got the
>> following error:

>> XML data source cannot be retrieved. XML data source is invalid or the
>> file doesn't exist.

>> Details:
>> org.eclipse.datatools.connectivity.oda.OdaException: XML data source
>> cannot be retrieved.XML data source file is invalid or the file doesn't
>> exist.
>> at
>>
>
org.eclipse.datatools.enablement.oda.xml.ui.wizards.XPathCho osePage.populateXMLTree(XPathChoosePage.java:320)
>> at
>>
>
org.eclipse.datatools.enablement.oda.xml.ui.wizards.XPathCho osePage.createPageCustomControl(XPathChoosePage.java:98)
>> at
>>
>
org.eclipse.datatools.connectivity.oda.design.ui.wizards.Dat aSetWizardPage.createControl(DataSetWizardPage.java:123)
>> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.ja va:170)
>> at
>>
>
org.eclipse.jface.wizard.WizardDialog.createPageControls(Wiz ardDialog.java:669)
>> at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog .java:1083)
>> at
>> org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDi alog.java:1142)
>> at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog. java:1139)
>> at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.jav a:1128)
>> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
>> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog. java:1126)
>> at
>> org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDial og.java:820)
>> at
>> org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDi alog.java:369)
>> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.jav a:624)
>> at
>> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe ner.java:227)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
>> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3821)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3420)
>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825 )
>> at org.eclipse.jface.window.Window.open(Window.java:801)
>> at
>>
>
org.eclipse.birt.report.designer.ui.actions.NewDataSetAction .createNewDataSet(NewDataSetAction.java:185)
>> at
>>
>
org.eclipse.birt.report.designer.ui.actions.NewDataSetAction .run(NewDataSetAction.java:170)
>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498 )
>> at
>>
>
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:583)
>> at
>>
>
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:500)
>> at
>>
>
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:411)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
>> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3821)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3420)
>> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
>> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
>> at
>> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
>> at
>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
>> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
>> at
>>
>
org.eclipse.birt.report.designer.ui.rcp.DesignerApplication. run(DesignerApplication.java:38)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at
>>
>
org.eclipse.equinox.internal.app.EclipseAppContainer.callMet hodWithException(EclipseAppContainer.java:574)
>> at
>>
>
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:195)
>> at
>>
>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
>> at
>>
>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
>> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
>> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> at java.lang.reflect.Method.invoke(Unknown Source)
>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
>> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

>> I know the structure of the XML file you gave me is OK as I also saved a
>> local copy to run the test and that worked fine.

>> So I am not actually able to run the test you asked me to check.

>> Thanks
>> Keith

>> Tianli wrote:

>>> Hi Keith

>>> I got the same issue, it works in designer bug failed in deployment
>>> please try this xml url which I used:
>>> https://bugs.eclipse.org/bugs/attachment.cgi?id=79863

>>> If you can reproduce it by this url it should be a bug. Please log a bug
>>> on bugzilla

>>> Thanks

>>> Tianli

Re: http 401 error (xml data source) with viewer deployed in tomcat [message #363512 is a reply to message #363509]

Wed, 25 June 2008 21:09

Eclipse User

:-) glad to hear that. May be it is tomcat related issue. But I have to
double check why it didn't work in my birt runtime, I started the server
by command line too.

Tianli

Re: http 401 error (xml data source) with viewer deployed in tomcat [message #547863 is a reply to message #363509]

Mon, 19 July 2010 17:33

Eclipse User

Hi,

Can you please check my posting which Iam expereincing the same problem.

http://www.eclipse.org/forums/index.php?t=msg&goto=54785 0&#msg_547850

It would great if u can let me know how you fix the above error as Iam exhausting working on this issue.

I was expecting Tomcat should prompt credentials of XML DataSource, so that user enter them and should get report generated, but it not prompting for credentials.

Any help would be appreciated.

Thanks,
Sreedhar

Re: http 401 error (xml data source) with viewer deployed in tomcat [message #547864 is a reply to message #363509]

Mon, 19 July 2010 17:33

Eclipse User

No Message Body

Previous Topic:	Does BIRT fully support HTML tags (e.g. <style>)?
Next Topic:	Upgrade BIRT 2.3.2 to BIRT2.6

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 24 18:13:51 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter