Home » Archived » BIRT » BIRT designer stuck when trying to produce a scripted data source with JNDI context
| BIRT designer stuck when trying to produce a scripted data source with JNDI context [message #232634] |
Fri, 06 April 2007 06:42  |
Eclipse User |
|
|
|
Originally posted by: ruby.boyarski.verix.com
hi,
Scripted data sources are great and worked for me when trying to use simple
scenarios (POJOs).
Now I am trying to call an EJB from a scripted data source.
Here's part of the code in the "open" method:
p = new Packages.java.util.Properties();
p.put("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
p.put("java.naming.provider.url", "localhost:51099");
initContext = new Packages.javax.naming.InitialContext(p);
In the last line the BIRT studio just gets "stuck" with no response when
clicking the "preview" tab.
When putting these lines in a class file and running it from a "Main" it
works just fine.
When calling the class from the script code the same phenomenon happens -
stuck.
Anyone has an idea how to solve this problem?
Cheers,
Ruby
|
|
| | | | | | | |
| Re: BIRT designer stuck when trying to produce a scripted data source with JNDI context [message #234097 is a reply to message #234076] |
Thu, 12 April 2007 11:18  |
| Eclipse User |
|
|
|
Originally posted by: ruby.boyarski.verix.com
Here is the text in the "open" method of the scripted data set:
invoker = "";
p = new Packages.java.util.Properties();
p.put("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
p.put("java.naming.provider.url", "ami-pc:21099");
initContext = new Packages.javax.naming.InitialContext(p);
objref = initContext.lookup("ejb/GeneralServices"); // Here the
exception happens (the first exception)
data = "11";//invoker.makeCall();
totalRows=1;
currentRow=0;
The exception occurs in the lookup line.
The same code works when in a java Main.
I attached the log file (look at the first exception - connection issue. The
second one is a result of the first).
thanks,
Ruby
"news://news.eclipse.org/eclipse.birt" <ruby.boyarski@verix.com> wrote in
message news:evlgi5$5ov$1@build.eclipse.org...
> Sure.
> What is the easiest way to log text? (I tried using System.out but
> couldn't)
>
>
> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
> news:evlfeb$tj5$1@build.eclipse.org...
>> Can you try a couple to things.
>> In your oda specifically log the URL before it gets used.
>>
>> Run the script version again and attach the log and report.
>>
>> Thanks
>>
>> Jason
>>
>> news://news.eclipse.org/eclipse.birt wrote:
>>> Same happens when using an ODA data source (with the same code -
>>> invoking
>>> an EJB).
>>> I attached the log.
>>> I have a similiar thread in the "eclipse.dtp" named "ODA driver for EJB
>>> access". Linda Chan answered me there saying that you may be able to
>>> provide help for the same problem (same problem happens in ODA driver
>>> and
>>> scripted data source).
>>>
>>> For some reason the designer "thinks" that the lookup URL is
>>> " Files/Actuate9/BRDPro/eclipse/plugins/org.eclipse.birt.repor t.viewer_2.1.2.v20061218-0710/birt/WEB-INF/classes/] "
>>> although I haven't specified it anywhere... (the real lookup is my own
>>> string "ejb/GeneralServices")
>>>
>>> Thanks for the help,
>>> Ruby
>>>
>>>
>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>> news:evg9h5$8jp$1@build.eclipse.org...
>>>> Can you turn on logging in the Viewer plugin web.xml?
>>>> Post the log when the error happens.
>>>>
>>>> Also can you preview the data set?
>>>>
>>>> Jason
>>>>
>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>> It happens when previewing the report.
>>>>> The screen is just stuck and no output is shown.
>>>>> Thanks,
>>>>> Ruby
>>>>>
>>>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>>>> news:evdtp6$nam$2@build.eclipse.org...
>>>>>> Does the error happen when you preview the report or the dataset?
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>>>> hi,
>>>>>>>
>>>>>>> Scripted data sources are great and worked for me when trying to use
>>>>>>> simple scenarios (POJOs).
>>>>>>> Now I am trying to call an EJB from a scripted data source.
>>>>>>> Here's part of the code in the "open" method:
>>>>>>> p = new Packages.java.util.Properties();
>>>>>>> p.put("java.naming.factory.initial",
>>>>>>> "org.jnp.interfaces.NamingContextFactory");
>>>>>>> p.put("java.naming.provider.url", "localhost:51099");
>>>>>>> initContext = new Packages.javax.naming.InitialContext(p);
>>>>>>>
>>>>>>> In the last line the BIRT studio just gets "stuck" with no response
>>>>>>> when
>>>>>>> clicking the "preview" tab.
>>>>>>> When putting these lines in a class file and running it from a
>>>>>>> "Main"
>>>>>>> it
>>>>>>> works just fine.
>>>>>>> When calling the class from the script code the same phenomenon
>>>>>>> happens -
>>>>>>> stuck.
>>>>>>>
>>>>>>> Anyone has an idea how to solve this problem?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Ruby
>>>>>
>>>
>
|
|
|
| Re: BIRT designer stuck when trying to produce a scripted data source with JNDI context [message #234203 is a reply to message #234097] |
Thu, 12 April 2007 12:30 |
| Eclipse User |
|
|
|
Originally posted by: jasonweathersby.alltel.net
Ruby,
Can you try installing BRDPro or OS BIRT in a path that has no spaces.
I assume this
Files/Actuate9/BRDPro/eclipse/plugins/org.eclipse.birt.repor t.viewer_2.1.2.v20061218-0710/birt/WEB-INF/classes/
should be c:\Program Files?
Run the same example and let us know what happens.
Jason
news://news.eclipse.org/eclipse.birt wrote:
> Here is the text in the "open" method of the scripted data set:
> invoker = "";
> p = new Packages.java.util.Properties();
> p.put("java.naming.factory.initial",
> "org.jnp.interfaces.NamingContextFactory");
> p.put("java.naming.provider.url", "ami-pc:21099");
> initContext = new Packages.javax.naming.InitialContext(p);
> objref = initContext.lookup("ejb/GeneralServices"); // Here the
> exception happens (the first exception)
> data = "11";//invoker.makeCall();
> totalRows=1;
> currentRow=0;
>
> The exception occurs in the lookup line.
> The same code works when in a java Main.
> I attached the log file (look at the first exception - connection issue. The
> second one is a result of the first).
>
> thanks,
> Ruby
>
>
>
> "news://news.eclipse.org/eclipse.birt" <ruby.boyarski@verix.com> wrote in
> message news:evlgi5$5ov$1@build.eclipse.org...
>> Sure.
>> What is the easiest way to log text? (I tried using System.out but
>> couldn't)
>>
>>
>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>> news:evlfeb$tj5$1@build.eclipse.org...
>>> Can you try a couple to things.
>>> In your oda specifically log the URL before it gets used.
>>>
>>> Run the script version again and attach the log and report.
>>>
>>> Thanks
>>>
>>> Jason
>>>
>>> news://news.eclipse.org/eclipse.birt wrote:
>>>> Same happens when using an ODA data source (with the same code -
>>>> invoking
>>>> an EJB).
>>>> I attached the log.
>>>> I have a similiar thread in the "eclipse.dtp" named "ODA driver for EJB
>>>> access". Linda Chan answered me there saying that you may be able to
>>>> provide help for the same problem (same problem happens in ODA driver
>>>> and
>>>> scripted data source).
>>>>
>>>> For some reason the designer "thinks" that the lookup URL is
>>>> " Files/Actuate9/BRDPro/eclipse/plugins/org.eclipse.birt.repor t.viewer_2.1.2.v20061218-0710/birt/WEB-INF/classes/] "
>>>> although I haven't specified it anywhere... (the real lookup is my own
>>>> string "ejb/GeneralServices")
>>>>
>>>> Thanks for the help,
>>>> Ruby
>>>>
>>>>
>>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>>> news:evg9h5$8jp$1@build.eclipse.org...
>>>>> Can you turn on logging in the Viewer plugin web.xml?
>>>>> Post the log when the error happens.
>>>>>
>>>>> Also can you preview the data set?
>>>>>
>>>>> Jason
>>>>>
>>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>>> It happens when previewing the report.
>>>>>> The screen is just stuck and no output is shown.
>>>>>> Thanks,
>>>>>> Ruby
>>>>>>
>>>>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>>>>> news:evdtp6$nam$2@build.eclipse.org...
>>>>>>> Does the error happen when you preview the report or the dataset?
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>>>>> hi,
>>>>>>>>
>>>>>>>> Scripted data sources are great and worked for me when trying to use
>>>>>>>> simple scenarios (POJOs).
>>>>>>>> Now I am trying to call an EJB from a scripted data source.
>>>>>>>> Here's part of the code in the "open" method:
>>>>>>>> p = new Packages.java.util.Properties();
>>>>>>>> p.put("java.naming.factory.initial",
>>>>>>>> "org.jnp.interfaces.NamingContextFactory");
>>>>>>>> p.put("java.naming.provider.url", "localhost:51099");
>>>>>>>> initContext = new Packages.javax.naming.InitialContext(p);
>>>>>>>>
>>>>>>>> In the last line the BIRT studio just gets "stuck" with no response
>>>>>>>> when
>>>>>>>> clicking the "preview" tab.
>>>>>>>> When putting these lines in a class file and running it from a
>>>>>>>> "Main"
>>>>>>>> it
>>>>>>>> works just fine.
>>>>>>>> When calling the class from the script code the same phenomenon
>>>>>>>> happens -
>>>>>>>> stuck.
>>>>>>>>
>>>>>>>> Anyone has an idea how to solve this problem?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Ruby
>
>
|
|
|
| Re: BIRT designer stuck when trying to produce a scripted data source with JNDI context [message #234525 is a reply to message #234203] |
Fri, 13 April 2007 13:42 |
| Eclipse User |
|
|
|
Originally posted by: ruby.boyarski.verix.com
I have done what you suggested and it worked like a charm! :-)
Now I have a problem deploying it to the iServer (actually, the problem is
in accessing the data source using the iPortal). I guess I should turn to
Actuate's support for that...
Thanks a lot for your support.
Ruby
"Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
news:evlmp5$tiv$1@build.eclipse.org...
> Ruby,
>
> Can you try installing BRDPro or OS BIRT in a path that has no spaces.
> I assume this
> Files/Actuate9/BRDPro/eclipse/plugins/org.eclipse.birt.repor t.viewer_2.1.2.v20061218-0710/birt/WEB-INF/classes/
> should be c:\Program Files?
>
> Run the same example and let us know what happens.
>
> Jason
>
> news://news.eclipse.org/eclipse.birt wrote:
>> Here is the text in the "open" method of the scripted data set:
>> invoker = "";
>> p = new Packages.java.util.Properties();
>> p.put("java.naming.factory.initial",
>> "org.jnp.interfaces.NamingContextFactory");
>> p.put("java.naming.provider.url", "ami-pc:21099");
>> initContext = new Packages.javax.naming.InitialContext(p);
>> objref = initContext.lookup("ejb/GeneralServices"); // Here the
>> exception happens (the first exception)
>> data = "11";//invoker.makeCall();
>> totalRows=1;
>> currentRow=0;
>>
>> The exception occurs in the lookup line.
>> The same code works when in a java Main.
>> I attached the log file (look at the first exception - connection issue.
>> The second one is a result of the first).
>>
>> thanks,
>> Ruby
>>
>>
>>
>> "news://news.eclipse.org/eclipse.birt" <ruby.boyarski@verix.com> wrote in
>> message news:evlgi5$5ov$1@build.eclipse.org...
>>> Sure.
>>> What is the easiest way to log text? (I tried using System.out but
>>> couldn't)
>>>
>>>
>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>> news:evlfeb$tj5$1@build.eclipse.org...
>>>> Can you try a couple to things.
>>>> In your oda specifically log the URL before it gets used.
>>>>
>>>> Run the script version again and attach the log and report.
>>>>
>>>> Thanks
>>>>
>>>> Jason
>>>>
>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>> Same happens when using an ODA data source (with the same code -
>>>>> invoking
>>>>> an EJB).
>>>>> I attached the log.
>>>>> I have a similiar thread in the "eclipse.dtp" named "ODA driver for
>>>>> EJB
>>>>> access". Linda Chan answered me there saying that you may be able to
>>>>> provide help for the same problem (same problem happens in ODA driver
>>>>> and
>>>>> scripted data source).
>>>>>
>>>>> For some reason the designer "thinks" that the lookup URL is
>>>>> " Files/Actuate9/BRDPro/eclipse/plugins/org.eclipse.birt.repor t.viewer_2.1.2.v20061218-0710/birt/WEB-INF/classes/] "
>>>>> although I haven't specified it anywhere... (the real lookup is my own
>>>>> string "ejb/GeneralServices")
>>>>>
>>>>> Thanks for the help,
>>>>> Ruby
>>>>>
>>>>>
>>>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>>>> news:evg9h5$8jp$1@build.eclipse.org...
>>>>>> Can you turn on logging in the Viewer plugin web.xml?
>>>>>> Post the log when the error happens.
>>>>>>
>>>>>> Also can you preview the data set?
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>>>> It happens when previewing the report.
>>>>>>> The screen is just stuck and no output is shown.
>>>>>>> Thanks,
>>>>>>> Ruby
>>>>>>>
>>>>>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>>>>>> news:evdtp6$nam$2@build.eclipse.org...
>>>>>>>> Does the error happen when you preview the report or the dataset?
>>>>>>>>
>>>>>>>> Jason
>>>>>>>>
>>>>>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>>>>>> hi,
>>>>>>>>>
>>>>>>>>> Scripted data sources are great and worked for me when trying to
>>>>>>>>> use
>>>>>>>>> simple scenarios (POJOs).
>>>>>>>>> Now I am trying to call an EJB from a scripted data source.
>>>>>>>>> Here's part of the code in the "open" method:
>>>>>>>>> p = new Packages.java.util.Properties();
>>>>>>>>> p.put("java.naming.factory.initial",
>>>>>>>>> "org.jnp.interfaces.NamingContextFactory");
>>>>>>>>> p.put("java.naming.provider.url", "localhost:51099");
>>>>>>>>> initContext = new Packages.javax.naming.InitialContext(p);
>>>>>>>>>
>>>>>>>>> In the last line the BIRT studio just gets "stuck" with no
>>>>>>>>> response
>>>>>>>>> when
>>>>>>>>> clicking the "preview" tab.
>>>>>>>>> When putting these lines in a class file and running it from a
>>>>>>>>> "Main"
>>>>>>>>> it
>>>>>>>>> works just fine.
>>>>>>>>> When calling the class from the script code the same phenomenon
>>>>>>>>> happens -
>>>>>>>>> stuck.
>>>>>>>>>
>>>>>>>>> Anyone has an idea how to solve this problem?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Ruby
>>
|
|
|
| Re: BIRT designer stuck when trying to produce a scripted data source with JNDI context [message #234816 is a reply to message #234525] |
Mon, 16 April 2007 11:36 |
| Eclipse User |
|
|
|
Originally posted by: jasonweathersby.alltel.net
Ruby,
Glad to hear this worked. The iPortal question is probably better
posted on Actuate's support site.
Thanks
Jason
news://news.eclipse.org/eclipse.birt wrote:
> I have done what you suggested and it worked like a charm! :-)
> Now I have a problem deploying it to the iServer (actually, the problem is
> in accessing the data source using the iPortal). I guess I should turn to
> Actuate's support for that...
> Thanks a lot for your support.
> Ruby
>
> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
> news:evlmp5$tiv$1@build.eclipse.org...
>> Ruby,
>>
>> Can you try installing BRDPro or OS BIRT in a path that has no spaces.
>> I assume this
>> Files/Actuate9/BRDPro/eclipse/plugins/org.eclipse.birt.repor t.viewer_2.1.2.v20061218-0710/birt/WEB-INF/classes/
>> should be c:\Program Files?
>>
>> Run the same example and let us know what happens.
>>
>> Jason
>>
>> news://news.eclipse.org/eclipse.birt wrote:
>>> Here is the text in the "open" method of the scripted data set:
>>> invoker = "";
>>> p = new Packages.java.util.Properties();
>>> p.put("java.naming.factory.initial",
>>> "org.jnp.interfaces.NamingContextFactory");
>>> p.put("java.naming.provider.url", "ami-pc:21099");
>>> initContext = new Packages.javax.naming.InitialContext(p);
>>> objref = initContext.lookup("ejb/GeneralServices"); // Here the
>>> exception happens (the first exception)
>>> data = "11";//invoker.makeCall();
>>> totalRows=1;
>>> currentRow=0;
>>>
>>> The exception occurs in the lookup line.
>>> The same code works when in a java Main.
>>> I attached the log file (look at the first exception - connection issue.
>>> The second one is a result of the first).
>>>
>>> thanks,
>>> Ruby
>>>
>>>
>>>
>>> "news://news.eclipse.org/eclipse.birt" <ruby.boyarski@verix.com> wrote in
>>> message news:evlgi5$5ov$1@build.eclipse.org...
>>>> Sure.
>>>> What is the easiest way to log text? (I tried using System.out but
>>>> couldn't)
>>>>
>>>>
>>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>>> news:evlfeb$tj5$1@build.eclipse.org...
>>>>> Can you try a couple to things.
>>>>> In your oda specifically log the URL before it gets used.
>>>>>
>>>>> Run the script version again and attach the log and report.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Jason
>>>>>
>>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>>> Same happens when using an ODA data source (with the same code -
>>>>>> invoking
>>>>>> an EJB).
>>>>>> I attached the log.
>>>>>> I have a similiar thread in the "eclipse.dtp" named "ODA driver for
>>>>>> EJB
>>>>>> access". Linda Chan answered me there saying that you may be able to
>>>>>> provide help for the same problem (same problem happens in ODA driver
>>>>>> and
>>>>>> scripted data source).
>>>>>>
>>>>>> For some reason the designer "thinks" that the lookup URL is
>>>>>> " Files/Actuate9/BRDPro/eclipse/plugins/org.eclipse.birt.repor t.viewer_2.1.2.v20061218-0710/birt/WEB-INF/classes/] "
>>>>>> although I haven't specified it anywhere... (the real lookup is my own
>>>>>> string "ejb/GeneralServices")
>>>>>>
>>>>>> Thanks for the help,
>>>>>> Ruby
>>>>>>
>>>>>>
>>>>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>>>>> news:evg9h5$8jp$1@build.eclipse.org...
>>>>>>> Can you turn on logging in the Viewer plugin web.xml?
>>>>>>> Post the log when the error happens.
>>>>>>>
>>>>>>> Also can you preview the data set?
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>>>>> It happens when previewing the report.
>>>>>>>> The screen is just stuck and no output is shown.
>>>>>>>> Thanks,
>>>>>>>> Ruby
>>>>>>>>
>>>>>>>> "Jason Weathersby" <jasonweathersby@alltel.net> wrote in message
>>>>>>>> news:evdtp6$nam$2@build.eclipse.org...
>>>>>>>>> Does the error happen when you preview the report or the dataset?
>>>>>>>>>
>>>>>>>>> Jason
>>>>>>>>>
>>>>>>>>> news://news.eclipse.org/eclipse.birt wrote:
>>>>>>>>>> hi,
>>>>>>>>>>
>>>>>>>>>> Scripted data sources are great and worked for me when trying to
>>>>>>>>>> use
>>>>>>>>>> simple scenarios (POJOs).
>>>>>>>>>> Now I am trying to call an EJB from a scripted data source.
>>>>>>>>>> Here's part of the code in the "open" method:
>>>>>>>>>> p = new Packages.java.util.Properties();
>>>>>>>>>> p.put("java.naming.factory.initial",
>>>>>>>>>> "org.jnp.interfaces.NamingContextFactory");
>>>>>>>>>> p.put("java.naming.provider.url", "localhost:51099");
>>>>>>>>>> initContext = new Packages.javax.naming.InitialContext(p);
>>>>>>>>>>
>>>>>>>>>> In the last line the BIRT studio just gets "stuck" with no
>>>>>>>>>> response
>>>>>>>>>> when
>>>>>>>>>> clicking the "preview" tab.
>>>>>>>>>> When putting these lines in a class file and running it from a
>>>>>>>>>> "Main"
>>>>>>>>>> it
>>>>>>>>>> works just fine.
>>>>>>>>>> When calling the class from the script code the same phenomenon
>>>>>>>>>> happens -
>>>>>>>>>> stuck.
>>>>>>>>>>
>>>>>>>>>> Anyone has an idea how to solve this problem?
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Ruby
>
|
|
|
Goto Forum:
Current Time: Tue Jul 22 02:22:51 EDT 2025
Powered by FUDForum. Page generated in 0.10715 seconds |
Home