Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [lyo-dev] How to manually set rdf:about in automatically created resources

Hi,
I built lyo from a more recent version and that solved the problem.
The about URIs are now correct...

Thanks!
_________________________________________________________
Erica Brown

DASH/Blaze Software Developer
IBM Software | Cloud & Smarter Infrastructure
919.224.1460 (phone) | 687.1460 (tie-line)

UI Services (DASH) is on SMC - Check it Out



Inactive hide details for lyo-dev-request---07/10/2013 04:07:16 AM---Send lyo-dev mailing list submissions to  lyo-dev@eclipse.lyo-dev-request---07/10/2013 04:07:16 AM---Send lyo-dev mailing list submissions to  lyo-dev@xxxxxxxxxxx

From: lyo-dev-request@xxxxxxxxxxx
To: lyo-dev@xxxxxxxxxxx
Date: 07/10/2013 04:07 AM
Subject: lyo-dev Digest, Vol 24, Issue 11
Sent by: lyo-dev-bounces@xxxxxxxxxxx





Send lyo-dev mailing list submissions to
lyo-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/lyo-dev
or, via email, send a message with subject or body 'help' to
lyo-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
lyo-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of lyo-dev digest..."


Today's Topics:

  1. Re: How to manually set rdf:about in automatically created
     resources (Idrissa)


----------------------------------------------------------------------

Message: 1
Date: Wed, 10 Jul 2013 10:06:44 +0200
From: Idrissa <idydieng@xxxxxxxxx>
To: Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>
Subject: Re: [lyo-dev] How to manually set rdf:about in automatically
created resources
Message-ID:
<CAMFbzpVYpaPKVAyAtHAip0Jc8cMQnKcB2+6+Yxrez=dC-qawSw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi Erica & Samuel,

I had the same problem using Lyo 1.1. Indeed, there is a bug Lyo (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=397561) but this bug is
already solved. I don't know which version of Lyo you are using?. Buiding a
preliminary Lyo version (in local) from the Lyo Git repository should
resolve your problem. I had do the same.

Hope this will be helpful.

--
Best regards / Cordialement / Mit freundlichen Gr?ssen
--
Dr. Idrissa Abdoulaye DIENG
Technology Manager

Phone: +33 (0)9 83 25 77 12
Fax: +33 (0)9 83 56 77 12

Web:
http://www.itemis.com
Mail: idrissa.dieng@xxxxxxxxxx
LinkedIn:
http://www.linkedin.com/in/idydi

itemis France SAS
198, Avenue de Verdun
92130 Issy-Les-Moulineaux
France



2013/7/9 Samuel Padgett <spadgett@xxxxxxxxxx>

> Erica,
>
> The ResponseInfo URI comes from the HttpServletRequest. I believe per the
> OSLC spec it must match, so it's not something I'd suggest you change (and
> I don't think it's possible in Lyo).
>
>
>
http://open-services.net/bin/view/Main/OslcCoreSpecification?sortcol=table;table=up#Resource_Paging
>
> "The subject resource URI of the oslc:ResponseInfo resource
> representation will be the HTTP request URI, or URI from subsequent
> redirects."
>
> What request URL did you use to get that query response?
>
> --
> Samuel Padgett | IBM Rational | spadgett@xxxxxxxxxx
>
>
> -----lyo-dev-bounces@xxxxxxxxxxx wrote: -----
> To: lyo-dev@xxxxxxxxxxx
> From: Erica Brown/Durham/IBM@IBMUS
> Sent by: lyo-dev-bounces@xxxxxxxxxxx
> Date: 07/09/2013 12:51PM
> Subject: [lyo-dev] How to manually set rdf:about in automatically created
> resources
>
>
> Hi,
> So, I have this implementation of oslc4j working in our environment...
> I am having a problem showing the proper URI in rdf:about for the returned
> service.. Here is an example:
> If I goto the oslc interface:
> *http://localhost:8080/XXXX/oslc/* <
http://localhost:8080/Blaze/oslc/>
> I get the output from the service provider:
> rdf:RDF xmlns:dcterms="
http://purl.org/dc/terms/" xmlns:rdf="
>
http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="
>
http://www.w3.org/2000/01/rdf-schema#" xmlns:oslc="
>
http://open-services.net/ns/core#">
>
>    <oslc:ServiceProvider rdf:about="
http://localhost:8080/XXXX/oslc/<http://localhost:8080/Blaze/oslc/>
>    ">
>       <oslc:details rdf:resource="
http://localhost:8080/XXXX/oslc/version<http://localhost:8080/Blaze/oslc/version>
>       "/>
>       <oslc:prefixDefinition>
>          <oslc:PrefixDefinition>
>             <oslc:prefixBase rdf:resource="
http://jazz.net/ns/ism/console#
>             "/>
>             <oslc:prefix>console</oslc:prefix>
>          </oslc:PrefixDefinition>
>       </oslc:prefixDefinition>
>       <oslc:service>
>          <oslc:Service>
>             <oslc:queryCapability>
>                <oslc:QueryCapability>
>                   <oslc:usage rdf:resource="
>                  
http://open-services.net/ns/core#default"/>
>                   <dcterms:title rdf:datatype="
>                  
http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral">
>                      Queries for deployments that are available in this
>                      service
>                   </dcterms:title>
>                   <oslc:resourceType rdf:resource="
>                  
http://jazz.net/ns/ism/console#Deployment"/>
>                   <oslc:queryBase rdf:resource="
>                  
http://localhost:8080/XXXX/oslc/deployments<http://localhost:8080/Blaze/oslc/deployments>
>                   "/>
>                   <oslc:label>Query Deployments</oslc:label>
>                </oslc:QueryCapability>
>             </oslc:queryCapability>
>             <oslc:queryCapability>
>                <oslc:QueryCapability>
>
>
>    Now, if I go to the resource connections:
>    I see the about is not the correct URI for the ResponseInfo:
>       <rdf:RDF xmlns:dcterms="
http://purl.org/dc/terms/" xmlns:rdf="
>      
http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="
>      
http://www.w3.org/2000/01/rdf-schema#" xmlns:oslc="
>      
http://open-services.net/ns/core#"xmlns:console="
>      
http://jazz.net/ns/ism/console#">
>    <oslc:ResponseInfo rdf:about="
>      
http://vulcan-w520.raleigh.ibm.com:8080/XXXX/connections<http://vulcan-w520.raleigh.ibm.com:8080/Blaze/connections>
>       ">
>          <rdfs:member>
>             <rdf:Description rdf:about="
>            
http://localhost:8080/XXXX/oslc//connections/connCuri<http://localhost:8080/Blaze/oslc//connections/connCuri>
>             ">
>                <console:protocol>https</console:protocol>
>                <console:id>connCuri</console:id>
>                <console:password>password</console:password>
>                <console:username>smadmin</console:username>
>
>                <console:url>/ibm/tivoli/rest/datasets/ConnectionManager</console:url>
>                <console:port>16311</console:port>
>                <console:host>9.42.101.105</console:host>
>                <console:type>
>                
http://jazz.net/ns/ism/console/connection#curi
>                </console:type>
>             </rdf:Description>
>          </rdfs:member>
>
> But it is set properly for the connection being returned because I set it
> manually
> In the code I have this set for the path..
>
>    @OslcService(IRestConstants.*CONSOLE_URI*)//
>    
http://jazz.net/ns/ism/console#
>    @Path(IRestConstants.*CONNECTIONS*)//connections
>
> So, I assume the about is being set to the App/{path} instead of using the
> URI set for the service provider..
>
> In the web.xml I setup the servlet mapping for the OSLC interface
>
> <servlet-mapping>
>  <servlet-name>OSLCServlet</servlet-name>
>  <url-pattern>/*oslc*</url-pattern>
>  <url-pattern>/*oslc*/*</url-pattern>
>  </servlet-mapping>
>
> So, the user has to goto localhost:<port>/App/oslc
> For the service provider
> and
> localhost:<port>/App/oslc/connections
> For the connections and so on.
>
> Is there a way around this by just setting the about for the response with
> the URI base..
> Or do I need to work things in a different way.
> Let me know if I need to include more information. I am not keen on all
> the naming of things yet,
> so this explaination may seem confusing to some.
> Sorry, I'm still new to OSLC.
> Thanks!
>
> _________________________________________________________*
> Erica Brown*
> DASH/Blaze Software Developer
> IBM Software | Cloud & Smarter Infrastructure
> 919.224.1460 (phone) | 687.1460 (tie-line)*
> **UI Services (DASH) is on SMC - Check it Out*<
https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=b8caedd7-3aca-41c1-a9c1-7be87a51c50e>
> *
> *<
https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=b8caedd7-3aca-41c1-a9c1-7be87a51c50e>
> _______________________________________________
> lyo-dev mailing list
> lyo-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/lyo-dev
>
> _______________________________________________
> lyo-dev mailing list
> lyo-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/lyo-dev
>
>


--
Cordialement,
Idrissa Abdoulaye DIENG
----------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
https://dev.eclipse.org/mailman/private/lyo-dev/attachments/20130710/3a12ffd5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Image.1__=08BBF130DFCADC248f9e8a93df938@xxxxxxxxxxxxxx
Type: image/jpeg
Size: 25233 bytes
Desc: not available
URL: <
https://dev.eclipse.org/mailman/private/lyo-dev/attachments/20130710/3a12ffd5/attachment.jpg>

------------------------------

_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/lyo-dev


End of lyo-dev Digest, Vol 24, Issue 11
***************************************


JPEG image

GIF image


Back to the top