[jira] [Commented] (CONNECTORS-430) An error should be returned if invalid seeds are typed into the seeds list for the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233515#comment-13233515 ] Karl Wright commented on CONNECTORS-430: Some comments. First, it is not a good idea to include quotation marks in translated messages. The quotation marks belong as part of the Javascript. Second, the following Javascript constructs are unsupported by the browser simulator: - typeof() - it looks like you could just remove this, however. - toString() - once again, looks like this could be just removed. - split() - easy to add. - the "+=" operator - can be added, or you might more readily just rephrase the expression to not use it > An error should be returned if invalid seeds are typed into the seeds list > for the web connector > > > Key: CONNECTORS-430 > URL: https://issues.apache.org/jira/browse/CONNECTORS-430 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3, > ManifoldCF 0.4, ManifoldCF 0.5 >Reporter: Erlend Garåsen >Assignee: Erlend Garåsen >Priority: Minor > Fix For: ManifoldCF 0.6 > > > If you create a job for the web connector and enter an invalid URL into the > seeds list, any value is accepted. An error message should be returned to the > user in order to prevent invalid seeds. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Possible bug in seeds list (web connector)
I have created a ticket for this and entered some unfinished JavaScript code. My head does not work very well with regular expressions today, so I will improve the code tomorrow. Please write a few lines about what I need to do with the Python browser simulator in order to test the JavaScript. Erlend On 20.03.12 14.14, Erlend Garåsen wrote: This sounds very ok. I have already written the necessary JavaScript code, and it works as it should. I didn't create a ticket because I needed time to figure out the best solution and in order to learn more about how the connector works by reading the Java code. I will create a ticket right away and include the JavaScript, but I think I will create a patch as well before I commit my work. Erlend On 20.03.12 13.59, Karl Wright wrote: I think this is a reasonable approach. You may need to modify the python browser simulator, though, to keep the UI tests working. I can help you with that when the time comes. If you create a ticket and include your proposed Javascript, I can review it and let you know how challenging I think it will be to support it in the browser simulator. Also, since we are trying to get a release out the door, I think it makes sense to hold off on these changes until I can make the release branch. Sound OK? Thanks! Karl On Tue, Mar 20, 2012 at 8:54 AM, Erlend Garåsen wrote: I think it will be much easier to validate the seeds list by using JavaScript instead of parsing urls with java.net.URL, simply because this is how we do validation elsewhere in the application. Checking for valid URLs, supported protocols and illegal characters shouldn't be very complicated by using JavaScript. What do you think? Erlend On 16.03.12 11.51, Karl Wright wrote: "Do you agree that a well-formed URL is what java.net.URL will accept in the constructor's argument? Then www.example.org will fail, but http://www.example.org (without a trailing slash) will pass." I might even go a bit further. See the following code in: WebcrawlerConnector: protected String makeDocumentIdentifier(String parentIdentifier, String rawURL, DocumentURLFilter filter) Thanks! Karl On Fri, Mar 16, 2012 at 5:52 AM, Erlend Garåsen wrote: On 15.03.12 19.30, Karl Wright wrote: A seed can be a specific html file so complaining about a trailing slash would make that not work. For example: http://hello.world.com/startpage.html I think I was a little bit unclear in my recent email. By a trailing slash, I was thinking more about the domain name itself, e.g. www.example.org/. I will create a Jira ticket now, but I will only focus about well-formed URLs in the seeds list. Do you agree that a well-formed URL is what java.net.URL will accept in the constructor's argument? Then www.example.org will fail, but http://www.example.org (without a trailing slash) will pass. Erlend -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050 -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050 -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
[jira] [Commented] (CONNECTORS-430) An error should be returned if invalid seeds are typed into the seeds list for the web connector
[
https://issues.apache.org/jira/browse/CONNECTORS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233468#comment-13233468
]
Erlend Garåsen commented on CONNECTORS-430:
---
This can be fixed by using JavaScript which performs an url validation. I have
entered the following in editjobs.jsp (vrawler-ui) which seems to work. This
code is not finished since some URLs (localhost) are not accepted.
{code}
function checkSeedsList()
{
if (typeof(editjob.seeds) != "undefined")
{
var regexp =
/http(s)?:\/\/[a-z0-9-\.]+\.[a-z]{2,4}\/?([^\s<>\#%"\,\{\}\\|\\\^\[\]`]+)?/;
var lines = editjob.seeds.value.toString().split("\n");
var invalidUrlList = "";
for (var i = 0; i < lines.length; i++) {
if (lines[i].length > 0 &&
!regexp.test(lines[i]))
{
invalidUrlList += lines[i] + "\n";
}
}
if (invalidUrlList.length > 0)
{
alert(<%=Messages.getString(pageContext.getRequest().getLocale(),"editjob.InvalidUrlInSeedsList")%>
+ "\n" + invalidUrlList);
editjob.seeds.focus();
return false;
}
}
return true;
}
{code}
> An error should be returned if invalid seeds are typed into the seeds list
> for the web connector
>
>
> Key: CONNECTORS-430
> URL: https://issues.apache.org/jira/browse/CONNECTORS-430
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Web connector
>Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3,
> ManifoldCF 0.4, ManifoldCF 0.5
>Reporter: Erlend Garåsen
>Assignee: Erlend Garåsen
>Priority: Minor
> Fix For: ManifoldCF 0.6
>
>
> If you create a job for the web connector and enter an invalid URL into the
> seeds list, any value is accepted. An error message should be returned to the
> user in order to prevent invalid seeds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-430) An error should be returned if invalid seeds are typed into the seeds list for the web connector
An error should be returned if invalid seeds are typed into the seeds list for the web connector Key: CONNECTORS-430 URL: https://issues.apache.org/jira/browse/CONNECTORS-430 Project: ManifoldCF Issue Type: Improvement Components: Web connector Affects Versions: ManifoldCF 0.4, ManifoldCF 0.3, ManifoldCF 0.2, ManifoldCF 0.1, ManifoldCF 0.5 Reporter: Erlend Garåsen Assignee: Erlend Garåsen Priority: Minor Fix For: ManifoldCF 0.6 If you create a job for the web connector and enter an invalid URL into the seeds list, any value is accepted. An error message should be returned to the user in order to prevent invalid seeds. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-425) Elastic Search documentation missing images
[ https://issues.apache.org/jira/browse/CONNECTORS-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi resolved CONNECTORS-425. --- Resolution: Fixed r1302909. > Elastic Search documentation missing images > --- > > Key: CONNECTORS-425 > URL: https://issues.apache.org/jira/browse/CONNECTORS-425 > Project: ManifoldCF > Issue Type: Bug > Components: Documentation >Reporter: Karl Wright >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF 0.5 > > Original Estimate: 4h > Remaining Estimate: 4h > > The ElasticSearch documentation refers to images that never actually were > committed. Looking back at the ticket, they were never included in any > uploaded patch either. These are: > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-connection-parameters.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-user.PNG. (No context info > available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-job-parameters.PNG. (No context > info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-history-report.PNG. (No context > info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-connection-parameters.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-user.PNG. (No context info > available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-job-parameters.PNG. (No context > info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-history-report.PNG. (No context > info available) > [exec] X [0] > ja_JP/images/ja_JP/elasticsearch-connection-parameters_ja_JP.PNG BROKEN: No > pipeline matched request: ja_ > JP/images/ja_JP/elasticsearch-connection-parameters_ja_JP.PNG > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-connection-parameters_ja_JP.PNG. > (No context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-user_ja_JP.PNG. (No context info > available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-job-parameters_ja_JP.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-history-report_ja_JP.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-connection-parameters_ja_JP.PNG. > (No context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-user_ja_JP.PNG. (No context info > available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-job-parameters_ja_JP.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-history-report_ja_JP.PNG. (No > context info available) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Possible bug in seeds list (web connector)
This sounds very ok. I have already written the necessary JavaScript code, and it works as it should. I didn't create a ticket because I needed time to figure out the best solution and in order to learn more about how the connector works by reading the Java code. I will create a ticket right away and include the JavaScript, but I think I will create a patch as well before I commit my work. Erlend On 20.03.12 13.59, Karl Wright wrote: I think this is a reasonable approach. You may need to modify the python browser simulator, though, to keep the UI tests working. I can help you with that when the time comes. If you create a ticket and include your proposed Javascript, I can review it and let you know how challenging I think it will be to support it in the browser simulator. Also, since we are trying to get a release out the door, I think it makes sense to hold off on these changes until I can make the release branch. Sound OK? Thanks! Karl On Tue, Mar 20, 2012 at 8:54 AM, Erlend Garåsen wrote: I think it will be much easier to validate the seeds list by using JavaScript instead of parsing urls with java.net.URL, simply because this is how we do validation elsewhere in the application. Checking for valid URLs, supported protocols and illegal characters shouldn't be very complicated by using JavaScript. What do you think? Erlend On 16.03.12 11.51, Karl Wright wrote: "Do you agree that a well-formed URL is what java.net.URL will accept in the constructor's argument? Then www.example.org will fail, but http://www.example.org (without a trailing slash) will pass." I might even go a bit further. See the following code in: WebcrawlerConnector: protected String makeDocumentIdentifier(String parentIdentifier, String rawURL, DocumentURLFilter filter) Thanks! Karl On Fri, Mar 16, 2012 at 5:52 AM, Erlend Garåsen wrote: On 15.03.12 19.30, Karl Wright wrote: A seed can be a specific html file so complaining about a trailing slash would make that not work. For example: http://hello.world.com/startpage.html I think I was a little bit unclear in my recent email. By a trailing slash, I was thinking more about the domain name itself, e.g. www.example.org/. I will create a Jira ticket now, but I will only focus about well-formed URLs in the seeds list. Do you agree that a well-formed URL is what java.net.URL will accept in the constructor's argument? Then www.example.org will fail, but http://www.example.org (without a trailing slash) will pass. Erlend -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050 -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050 -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Postpone localization tickets for 0.5 release?
I would like to work on Japanese screenshots. Give me an hour. Piergiorgio Il 20 marzo 2012 13:18, Karl Wright ha scritto: > Ok, I've postponed. Piergiorgio, do you still intend to generate > Japanese screenshots for the ElasticSearch connector documentation? > If not we should postpone that ticket as well. > > Karl > > On Tue, Mar 20, 2012 at 6:34 AM, Piergiorgio Lucidi > wrote: >> +1 from me. >> >> Piergiorgio >> >> Il 19 marzo 2012 20:33, Karl Wright ha scritto: >>> Hi all, >>> >>> I've not heard anything from Hitoshi Ozawa about whether he will be >>> able to complete some of the Japanese localization work that was >>> scheduled for 0.5-incubating. Since the day is rapidly approaching >>> when we have to spin the first RC, I'd like a show of hands as to >>> whether we should postpone the two tickets currently on Hitoshi's >>> plate for the next release. The tickets in question are >>> CONNECTORS-394 and CONNECTORS-404. >>> >>> +1 from me for postponing. >>> >>> Karl >> >> >> >> -- >> Piergiorgio Lucidi >> http://www.open4dev.com -- Piergiorgio Lucidi http://www.open4dev.com
Re: Possible bug in seeds list (web connector)
I think this is a reasonable approach. You may need to modify the python browser simulator, though, to keep the UI tests working. I can help you with that when the time comes. If you create a ticket and include your proposed Javascript, I can review it and let you know how challenging I think it will be to support it in the browser simulator. Also, since we are trying to get a release out the door, I think it makes sense to hold off on these changes until I can make the release branch. Sound OK? Thanks! Karl On Tue, Mar 20, 2012 at 8:54 AM, Erlend Garåsen wrote: > > I think it will be much easier to validate the seeds list by using > JavaScript instead of parsing urls with java.net.URL, simply because this is > how we do validation elsewhere in the application. > > Checking for valid URLs, supported protocols and illegal characters > shouldn't be very complicated by using JavaScript. > > What do you think? > > Erlend > > > On 16.03.12 11.51, Karl Wright wrote: >> >> "Do you agree that a well-formed URL is what java.net.URL will accept >> in the constructor's argument? Then www.example.org will fail, but >> http://www.example.org (without a trailing slash) will pass." >> >> I might even go a bit further. See the following code in: >> WebcrawlerConnector: protected String makeDocumentIdentifier(String >> parentIdentifier, String rawURL, DocumentURLFilter filter) >> >> Thanks! >> Karl >> >> >> >> On Fri, Mar 16, 2012 at 5:52 AM, Erlend Garåsen >> wrote: >>> >>> On 15.03.12 19.30, Karl Wright wrote: A seed can be a specific html file so complaining about a trailing slash would make that not work. For example: http://hello.world.com/startpage.html >>> >>> >>> >>> I think I was a little bit unclear in my recent email. By a trailing >>> slash, >>> I was thinking more about the domain name itself, e.g. www.example.org/. >>> >>> I will create a Jira ticket now, but I will only focus about well-formed >>> URLs in the seeds list. >>> >>> Do you agree that a well-formed URL is what java.net.URL will accept in >>> the >>> constructor's argument? Then www.example.org will fail, but >>> http://www.example.org (without a trailing slash) will pass. >>> >>> >>> Erlend >>> >>> -- >>> Erlend Garåsen >>> Center for Information Technology Services >>> University of Oslo >>> P.O. Box 1086 Blindern, N-0317 OSLO, Norway >>> Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: >>> 31050 > > > > -- > Erlend Garåsen > Center for Information Technology Services > University of Oslo > P.O. Box 1086 Blindern, N-0317 OSLO, Norway > Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Possible bug in seeds list (web connector)
I think it will be much easier to validate the seeds list by using JavaScript instead of parsing urls with java.net.URL, simply because this is how we do validation elsewhere in the application. Checking for valid URLs, supported protocols and illegal characters shouldn't be very complicated by using JavaScript. What do you think? Erlend On 16.03.12 11.51, Karl Wright wrote: "Do you agree that a well-formed URL is what java.net.URL will accept in the constructor's argument? Then www.example.org will fail, but http://www.example.org (without a trailing slash) will pass." I might even go a bit further. See the following code in: WebcrawlerConnector: protected String makeDocumentIdentifier(String parentIdentifier, String rawURL, DocumentURLFilter filter) Thanks! Karl On Fri, Mar 16, 2012 at 5:52 AM, Erlend Garåsen wrote: On 15.03.12 19.30, Karl Wright wrote: A seed can be a specific html file so complaining about a trailing slash would make that not work. For example: http://hello.world.com/startpage.html I think I was a little bit unclear in my recent email. By a trailing slash, I was thinking more about the domain name itself, e.g. www.example.org/. I will create a Jira ticket now, but I will only focus about well-formed URLs in the seeds list. Do you agree that a well-formed URL is what java.net.URL will accept in the constructor's argument? Then www.example.org will fail, but http://www.example.org (without a trailing slash) will pass. Erlend -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050 -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Postpone localization tickets for 0.5 release?
Ok, I've postponed. Piergiorgio, do you still intend to generate Japanese screenshots for the ElasticSearch connector documentation? If not we should postpone that ticket as well. Karl On Tue, Mar 20, 2012 at 6:34 AM, Piergiorgio Lucidi wrote: > +1 from me. > > Piergiorgio > > Il 19 marzo 2012 20:33, Karl Wright ha scritto: >> Hi all, >> >> I've not heard anything from Hitoshi Ozawa about whether he will be >> able to complete some of the Japanese localization work that was >> scheduled for 0.5-incubating. Since the day is rapidly approaching >> when we have to spin the first RC, I'd like a show of hands as to >> whether we should postpone the two tickets currently on Hitoshi's >> plate for the next release. The tickets in question are >> CONNECTORS-394 and CONNECTORS-404. >> >> +1 from me for postponing. >> >> Karl > > > > -- > Piergiorgio Lucidi > http://www.open4dev.com
[jira] [Updated] (CONNECTORS-394) Alt tags in crawler UI navigation are not internationalized
[ https://issues.apache.org/jira/browse/CONNECTORS-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-394: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF next > Alt tags in crawler UI navigation are not internationalized > --- > > Key: CONNECTORS-394 > URL: https://issues.apache.org/jira/browse/CONNECTORS-394 > Project: ManifoldCF > Issue Type: Bug > Components: Framework crawler agent >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Hitoshi Ozawa >Priority: Minor > Fix For: ManifoldCF next > > > The alt tags for all the navigation links in the crawler UI navigation pane > are not internationalized. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-404) Japanese "how to build and deploy" page out of date
[ https://issues.apache.org/jira/browse/CONNECTORS-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-404: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF next > Japanese "how to build and deploy" page out of date > --- > > Key: CONNECTORS-404 > URL: https://issues.apache.org/jira/browse/CONNECTORS-404 > Project: ManifoldCF > Issue Type: Bug > Components: Documentation >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Hitoshi Ozawa > Fix For: ManifoldCF next > > > Recent changes to the build target are not reflected in the Japanese version > of "how to build and deploy". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Postpone localization tickets for 0.5 release?
+1 from me. Piergiorgio Il 19 marzo 2012 20:33, Karl Wright ha scritto: > Hi all, > > I've not heard anything from Hitoshi Ozawa about whether he will be > able to complete some of the Japanese localization work that was > scheduled for 0.5-incubating. Since the day is rapidly approaching > when we have to spin the first RC, I'd like a show of hands as to > whether we should postpone the two tickets currently on Hitoshi's > plate for the next release. The tickets in question are > CONNECTORS-394 and CONNECTORS-404. > > +1 from me for postponing. > > Karl -- Piergiorgio Lucidi http://www.open4dev.com
Re: Postpone localization tickets for 0.5 release?
On 19.03.12 20.33, Karl Wright wrote: Hi all, I've not heard anything from Hitoshi Ozawa about whether he will be able to complete some of the Japanese localization work that was scheduled for 0.5-incubating. Since the day is rapidly approaching when we have to spin the first RC, I'd like a show of hands as to whether we should postpone the two tickets currently on Hitoshi's plate for the next release. The tickets in question are CONNECTORS-394 and CONNECTORS-404. +1 from me for postponing. Karl +1 -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
