[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657474#comment-13657474
]
Rishi Verma commented on OODT-605:
----------------------------------
Hey Chris - just an update. It went through and I've added Ross' project to my list of "willing
to mentor".
Thanks!
rishi
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rishi Verma resolved OODT-608.
------------------------------
Resolution: Fixed
Resolved in r1482565.
> filemgr-client fails to run properly due to syntax errors
> ---------------------------------------------------------
>
> Key: OODT-608
> URL: https://issues.apache.org/jira/browse/OODT-608
> Project: OODT
> Issue Type: Bug
> Components: radix
> Affects Versions: 0.5
> Reporter: Rishi Verma
> Assignee: Rishi Verma
> Fix For: 0.6
>
> Attachments: OODT-608.riverma.05092013.patch.txt
>
>
> The bundled RADiX filemgr-client [1] script contains some syntax errors that prevent
it from running properly within the context of RADiX.
> Namely:
> a. The JAVA Spring "action" property sent into the XmlRpcFilemgrClient class is used
twice and overshadows the "option" property
> i.e. "-Dorg.apache.oodt.cas.cli.action.spring.config" occurs twice accidently
> b. The use of an absolute path (and env variable FILEMGR_HOME) within the spring config
properties for "org.apache.oodt.cas.cli.*.spring.config" causes XmlRpcFilemgrClient to interpret
the path incorrectly. Specifically, it assumes a relative path, and thus prepends the current
directory with the environment variable's expanded path following. Often, this causes the
same base path to occur twice within the final path.
> c. The given paths for "-Dorg.apache.oodt.cas.filemgr.properties" and "-Djava.util.logging.config.file"
point to the "conf" directory for looking up files; however, this should instead be the "etc"
directory within the context of RADiX.
> –-
> [1] http://svn.apache.org/repos/asf/oodt/tags/0.5/mvn/archetypes/radix/src/main/resources/archetype-resources/filemgr/src/main/resources/bin/filemgr-client
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Author: riverma
Date: Tue May 14 20:29:47 2013
New Revision: 1482565
URL: http://svn.apache.org/r1482565
Log:
OODT-608 : filemgr-client fails to run properly due to syntax errors
Modified:
oodt/trunk/mvn/archetypes/radix/src/main/resources/archetype-resources/filemgr/src/main/resources/bin/filemgr-client
Modified: oodt/trunk/mvn/archetypes/radix/src/main/resources/archetype-resources/filemgr/src/main/resources/bin/filemgr-client
URL: http://svn.apache.org/viewvc/oodt/trunk/mvn/archetypes/radix/src/main/resources/archetype-resources/filemgr/src/main/resources/bin/filemgr-client?rev=1482565&r1=1482564&r2=1482565&view=diff
==============================================================================
--- oodt/trunk/mvn/archetypes/radix/src/main/resources/archetype-resources/filemgr/src/main/resources/bin/filemgr-client
(original)
+++ oodt/trunk/mvn/archetypes/radix/src/main/resources/archetype-resources/filemgr/src/main/resources/bin/filemgr-client
Tue May 14 20:29:47 2013
@@ -70,8 +70,8 @@ cd "$FILEMGR_HOME"/bin
"$_RUNJAVA" $JAVA_OPTS $OODT_OPTS \
-Djava.ext.dirs="$FILEMGR_HOME"/lib \
- -Dorg.apache.oodt.cas.filemgr.properties="$FILEMGR_HOME"/conf/filemgr.properties \
- -Djava.util.logging.config.file="$FILEMGR_HOME"/conf/logging.properties \
- -Dorg.apache.oodt.cas.cli.action.spring.config="$FILEMGR_HOME"/policy/cmd-line-actions.xml
\
- -Dorg.apache.oodt.cas.cli.action.spring.config="$FILEMGR_HOME"/policy/cmd-line-actions.xml
\
+ -Dorg.apache.oodt.cas.filemgr.properties="$FILEMGR_HOME"/etc/filemgr.properties \
+ -Djava.util.logging.config.file="$FILEMGR_HOME"/etc/logging.properties \
+ -Dorg.apache.oodt.cas.cli.action.spring.config=file:"$FILEMGR_HOME"/policy/cmd-line-actions.xml
\
+ -Dorg.apache.oodt.cas.cli.option.spring.config=file:"$FILEMGR_HOME"/policy/cmd-line-options.xml
\
org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient "$@"
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655168#comment-13655168
]
Chris A. Mattmann commented on OODT-605:
----------------------------------------
Gotcha Reesh -- can you bug Ulrich Stark and the code-awards@apache.org list for info on this?
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Ross Laidlaw created OODT-614:
---------------------------------
Summary: Implement a JAX-RS interface to access File Manager product information
and metadata as configurable JSON streams
Key: OODT-614
URL: https://issues.apache.org/jira/browse/OODT-614
Project: OODT
Issue Type: Sub-task
Components: product server
Affects Versions: 0.6
Reporter: Ross Laidlaw
Assignee: Ross Laidlaw
Fix For: 0.6
Add Java classes to the org.apache.oodt.cas.product.service package and add XML configuration
files to allow File Manager product information and metadata to be accessible as JSON streams
via a JAX-RS RESTful interface (URLs).
The URLs should allow information on single products to be retrieved by product ID, information
on product sets to be retrieved by product type and information to be retrieved for any transfers
in progress.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Ross Laidlaw created OODT-613:
---------------------------------
Summary: Implement a JAX-RS interface to access File Manager product information
and metadata as configurable RSS streams
Key: OODT-613
URL: https://issues.apache.org/jira/browse/OODT-613
Project: OODT
Issue Type: Sub-task
Components: product server
Affects Versions: 0.6
Reporter: Ross Laidlaw
Assignee: Ross Laidlaw
Fix For: 0.6
Add Java classes to the org.apache.oodt.cas.product.service package and add XML configuration
files to allow File Manager product information and metadata to be accessible as RSS streams
via a JAX-RS RESTful interface (URLs).
The URLs should allow information on single products to be retrieved by product ID, information
on product sets to be retrieved by product type and information to be retrieved for any transfers
in progress.
The new JAX-RS interface should also maintain backwards-compatibility with the URLs supported
by the servlets in the org.apache.oodt.cas.product.rss package, as detailed in the user guide:
https://cwiki.apache.org/confluence/display/OODT/File+Manager+REST+API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Ross Laidlaw created OODT-612:
---------------------------------
Summary: Implement a JAX-RS interface to access File Manager product information
and metadata as configurable RDF streams
Key: OODT-612
URL: https://issues.apache.org/jira/browse/OODT-612
Project: OODT
Issue Type: Sub-task
Components: product server
Affects Versions: 0.6
Reporter: Ross Laidlaw
Assignee: Ross Laidlaw
Fix For: 0.6
Add Java classes to the org.apache.oodt.cas.product.service package and add XML configuration
files to allow File Manager product information and metadata to be accessible as RDF streams
via a JAX-RS RESTful interface (URLs).
The URLs should allow information on single products to be retrieved by product ID, information
on product sets to be retrieved by product type and information to be retrieved for any transfers
in progress.
The new JAX-RS interface should also maintain backwards-compatibility with the URLs supported
by the servlets in the org.apache.oodt.cas.product.rdf package, as detailed in the user guide:
https://cwiki.apache.org/confluence/display/OODT/File+Manager+REST+API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Ross Laidlaw created OODT-611:
---------------------------------
Summary: Implement a JAX-RS interface to access File Manager products and associated
metadata as raw data
Key: OODT-611
URL: https://issues.apache.org/jira/browse/OODT-611
Project: OODT
Issue Type: Sub-task
Components: product server
Affects Versions: 0.6
Reporter: Ross Laidlaw
Assignee: Ross Laidlaw
Fix For: 0.6
Add Java classes to the org.apache.oodt.cas.product.service package and add XML configuration
files to allow File Manager products and associated metadata to be served as resources via
a JAX-RS RESTful interface (URLs).
The RESTful interface should return product-metadata combinations as zip (application/zip
MIME type) files.
The URLs should allow products to be retrieved by product ID and allow product sets to be
retrieved by product type.
The new JAX-RS interface should also maintain backwards-compatibility with the URLs supported
by the servlets in the org.apache.oodt.cas.product.data package, as detailed in the user guide:
https://cwiki.apache.org/confluence/display/OODT/File+Manager+REST+API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654543#comment-13654543
]
Rishi Verma commented on OODT-605:
----------------------------------
Hey Chris,
I meant waiting for the Melange system to get a response from Apache. My current status on
Melange (after signing up for a "connection with ASF") is the following: 'Status: Org Action
Required'. I currently don't see any links for looking at proposals or signing up for 'willing
to mentor'.
I think I have to wait for a response from the ASF, no? If not, could you send me a sample
link of where on Melange one can look over proposals etc? I can check to see if I have access
to that page.
Thanks!
Rishi
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ross Laidlaw updated OODT-610:
------------------------------
Summary: Create a skeleton Java package for the CAS-Product JAX-RS service (was: Create
a skeleton Java package for a CAS-Product JAX-RS service)
> Create a skeleton Java package for the CAS-Product JAX-RS service
> -----------------------------------------------------------------
>
> Key: OODT-610
> URL: https://issues.apache.org/jira/browse/OODT-610
> Project: OODT
> Issue Type: Sub-task
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
>
> Create a new package (e.g. named 'org.apache.oodt.cas.product.service') within the CAS-Product
web application (sub-package of org.apache.oodt.cas.product). This package will be used for
the CAS-Prodoct JAX-RS interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ross Laidlaw updated OODT-610:
------------------------------
Description: Create a new Java package (e.g. named 'service') within the CAS-Product web
application (i.e. as a sub-package of org.apache.oodt.cas.product). This package will be
used for the CAS-Prodoct JAX-RS interface. (was: Create a new package (e.g. named 'org.apache.oodt.cas.product.service')
within the CAS-Product web application (sub-package of org.apache.oodt.cas.product). This
package will be used for the CAS-Prodoct JAX-RS interface.)
> Create a skeleton Java package for the CAS-Product JAX-RS service
> -----------------------------------------------------------------
>
> Key: OODT-610
> URL: https://issues.apache.org/jira/browse/OODT-610
> Project: OODT
> Issue Type: Sub-task
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
>
> Create a new Java package (e.g. named 'service') within the CAS-Product web application
(i.e. as a sub-package of org.apache.oodt.cas.product). This package will be used for the
CAS-Prodoct JAX-RS interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ross Laidlaw updated OODT-610:
------------------------------
Summary: Create a skeleton Java package for a CAS-Product JAX-RS service (was: Create
a skeleton package for a CAS-Product JAX-RS service)
> Create a skeleton Java package for a CAS-Product JAX-RS service
> ---------------------------------------------------------------
>
> Key: OODT-610
> URL: https://issues.apache.org/jira/browse/OODT-610
> Project: OODT
> Issue Type: Sub-task
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
>
> Create a new package (e.g. named 'org.apache.oodt.cas.product.service') within the CAS-Product
web application (sub-package of org.apache.oodt.cas.product). This package will be used for
the CAS-Prodoct JAX-RS interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Ross Laidlaw created OODT-610:
---------------------------------
Summary: Create a skeleton package for a CAS-Product JAX-RS service
Key: OODT-610
URL: https://issues.apache.org/jira/browse/OODT-610
Project: OODT
Issue Type: Sub-task
Components: product server
Affects Versions: 0.6
Reporter: Ross Laidlaw
Assignee: Ross Laidlaw
Fix For: 0.6
Create a new package (e.g. named 'org.apache.oodt.cas.product.service') within the CAS-Product
web application (sub-package of org.apache.oodt.cas.product). This package will be used for
the CAS-Prodoct JAX-RS interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Ross Laidlaw created OODT-609:
---------------------------------
Summary: Add Apache CXF dependency to the Maven POM for CAS-Product
Key: OODT-609
URL: https://issues.apache.org/jira/browse/OODT-609
Project: OODT
Issue Type: Sub-task
Components: product server
Affects Versions: 0.6
Reporter: Ross Laidlaw
Assignee: Ross Laidlaw
Fix For: 0.6
Update the Maven POM file (pom.xml) for the CAS-Product web application to include Apache
CXF as a dependency, so that we can use Apache CXF for JAX-RS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653563#comment-13653563
]
Chris A. Mattmann commented on OODT-605:
----------------------------------------
Reesh nothing for Apache to approve the ACK is all you need and you got it.
Outside of the ACK are you registered in Melange? If so, the next step is to indicate your
"willing to mentor" on proposals (aka Ross's) and then to rank the proposals per latest instructions
from Uli.
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rishi Verma updated OODT-608:
-----------------------------
Attachment: OODT-608.riverma.05092013.patch.txt
OODT-608.riverma.05092013.patch.txt details:
* change 'conf' to 'etc' to filemgr properties and logging paths
* add the suffix 'file:' to spring argument paths
* change duplicate action spring path to option path
> filemgr-client fails to run properly due to syntax errors
> ---------------------------------------------------------
>
> Key: OODT-608
> URL: https://issues.apache.org/jira/browse/OODT-608
> Project: OODT
> Issue Type: Bug
> Components: radix
> Affects Versions: 0.5
> Reporter: Rishi Verma
> Assignee: Rishi Verma
> Fix For: 0.6
>
> Attachments: OODT-608.riverma.05092013.patch.txt
>
>
> The bundled RADiX filemgr-client [1] script contains some syntax errors that prevent
it from running properly within the context of RADiX.
> Namely:
> a. The JAVA Spring "action" property sent into the XmlRpcFilemgrClient class is used
twice and overshadows the "option" property
> i.e. "-Dorg.apache.oodt.cas.cli.action.spring.config" occurs twice accidently
> b. The use of an absolute path (and env variable FILEMGR_HOME) within the spring config
properties for "org.apache.oodt.cas.cli.*.spring.config" causes XmlRpcFilemgrClient to interpret
the path incorrectly. Specifically, it assumes a relative path, and thus prepends the current
directory with the environment variable's expanded path following. Often, this causes the
same base path to occur twice within the final path.
> c. The given paths for "-Dorg.apache.oodt.cas.filemgr.properties" and "-Djava.util.logging.config.file"
point to the "conf" directory for looking up files; however, this should instead be the "etc"
directory within the context of RADiX.
> –-
> [1] http://svn.apache.org/repos/asf/oodt/tags/0.5/mvn/archetypes/radix/src/main/resources/archetype-resources/filemgr/src/main/resources/bin/filemgr-client
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Rishi Verma created OODT-608:
--------------------------------
Summary: filemgr-client fails to run properly due to syntax errors
Key: OODT-608
URL: https://issues.apache.org/jira/browse/OODT-608
Project: OODT
Issue Type: Bug
Components: radix
Affects Versions: 0.5
Reporter: Rishi Verma
Assignee: Rishi Verma
Fix For: 0.6
The bundled RADiX filemgr-client [1] script contains some syntax errors that prevent it from
running properly within the context of RADiX.
Namely:
a. The JAVA Spring "action" property sent into the XmlRpcFilemgrClient class is used twice
and overshadows the "option" property
i.e. "-Dorg.apache.oodt.cas.cli.action.spring.config" occurs twice accidently
b. The use of an absolute path (and env variable FILEMGR_HOME) within the spring config properties
for "org.apache.oodt.cas.cli.*.spring.config" causes XmlRpcFilemgrClient to interpret the
path incorrectly. Specifically, it assumes a relative path, and thus prepends the current
directory with the environment variable's expanded path following. Often, this causes the
same base path to occur twice within the final path.
c. The given paths for "-Dorg.apache.oodt.cas.filemgr.properties" and "-Djava.util.logging.config.file"
point to the "conf" directory for looking up files; however, this should instead be the "etc"
directory within the context of RADiX.
–-
[1] http://svn.apache.org/repos/asf/oodt/tags/0.5/mvn/archetypes/radix/src/main/resources/archetype-resources/filemgr/src/main/resources/bin/filemgr-client
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653413#comment-13653413
]
Rishi Verma commented on OODT-605:
----------------------------------
Hey Chris,
Should be ready to do that soon - just waiting for Apache to approve my GSoC mentor connection.
Thanks -
Rishi
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649123#comment-13649123
]
Ross Laidlaw commented on OODT-605:
-----------------------------------
Thanks Chris, much appreciated! :)
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648675#comment-13648675
]
Chris A. Mattmann commented on OODT-605:
----------------------------------------
I clicked wish to mentor to make sure you had at least one of those so the proposal has a
shot to get in.
Rishi please ASAP click "wish to mentor" so you can be a mentor too.
Thanks Ross!
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648644#comment-13648644
]
Ross Laidlaw commented on OODT-605:
-----------------------------------
Thanks Rishi & Chris!
Today I submitted a [GSoC proposal|https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/rlaidlaw/15001].
It should be visible to everyone but please let me know if you can't access the link.
Ross
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647697#comment-13647697
]
Rishi Verma commented on OODT-605:
----------------------------------
+1 to still applying for GSoC - go for it Ross! You have an excellent game plan here, so it
will be valuable either way it goes.
Rishi
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ross Laidlaw updated OODT-605:
------------------------------
Labels: gsoc2013 (was: )
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646582#comment-13646582
]
Ross Laidlaw commented on OODT-605:
-----------------------------------
Hi Chris!
Many thanks for your comments and advice. I see what you mean about GSoC. I'll try to submit
a proposal before Friday's deadline :)
Ross
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645867#comment-13645867
]
Chris A. Mattmann commented on OODT-605:
----------------------------------------
Ross I think you can still apply to GSoC if you want -- I'm not sure how the ranking will
work out so the docs you posted may be right but you'll never know if you don't try. Either
way is fine with me though and I appreciate and thank you for being willing to do the work
regardless!
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645866#comment-13645866
]
Chris A. Mattmann commented on OODT-605:
----------------------------------------
+1 to keeping the old scheme (being back compat).
+1 to defining a new URL scheme that Ross L. proposes below which is awesome and way more
consistent!
Then in later versions of OODT (perhaps before 1.0 but after 0.6 or 0.7) we could revisit
deprecating
and even removing the old APIs (with lots of notice in CHANGES.txt and warnings and other
good stuff).
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645804#comment-13645804
]
Ross Laidlaw edited comment on OODT-605 at 4/30/13 6:25 PM:
------------------------------------------------------------
Hi Rishi,
Many thanks for your comments and advice, much appreciated!
I like your comment about a JAX-RS webapp being more extensible. Hopefully we can write/design
the code in such a way that we can easily add new output formats (and configurations too).
I can see advantages of keeping the same URL format as before - for example, existing users
of OODT wouldn't need to reconfigure their projects to use the new system. Was this the main
reason you were thinking of too?
For reference for anyone looking at this JIRA issue, here's a list of the main URLs for the
CAS-Product webapp that I found in the classes, documentation, wikis, etc:
For raw data (DataDeliveryServlet, DatasetDeliveryServlet):
{panel}
/data
/dataset
{panel}
For RDF streams (RDFProductServlet, RDFDatasetServlet):
{panel}
/rdf
/rdf/dataset
{panel}
For RSS streams (RSSProductServlet, RSSProductTransferServlet):
{panel}
/viewRecent
/viewTransfers
{panel}
As well as keeping these intact, it might also be useful for us to define a consistent URL
scheme/plan that will fit well with extended features we'd like to introduce later. For example,
we could have something like this:
{panel}
/[type]/[format]?parameters
{panel}
Where [format] is the output format and [type] can be 'product', 'dataset', 'transfer', etc.,
e.g.
{panel}
/product/rdf?...
/dataset/rss?...
/transfer/json?...
{panel}
Or we could specify the format as a parameter, e.g.:
{panel}
/product?format=JSON...
/transfer?format=RSS...
/dataset?format=RDF...
{panel}
I'm sure there are many alternative arrangements we could experiment with!
Regarding GSoC, it seems that Apache prefers applications from new recruits rather than students
who have already participated in previous years.[1] Since I participated in GSoC last year
with Apache OODT, I've decided not to apply this year after all. But I'd like to work on
OODT-605 anyway as a normal non-GSoC project. I'm happy to do the work if that's ok with
everyone and will gladly accept advice, guidance, etc from the OODT community. In fact, it
would be awesome to work together with you on this Rishi under your guidance, if you have
time available.
Ross
[1] http://community.apache.org/mentee-ranking-process.html
was (Author: rlaidlaw):
Hi Rishi,
Many thanks for your comments and advice, much appreciated!
I like your comment about a JAX-RS webapp being more extensible. Hopefully we can write/design
the code in such a way that we can easily add new output formats (and configurations too).
I can see advantages of keeping the same URL format as before - for example, existing users
of OODT wouldn't need to reconfigure their projects to use the new system. Was this the main
reason you were thinking of too?
For reference for anyone looking at this JIRA issue, here's a list of the main URLs for the
CAS-Product webapp that I found in the classes, documentation, wikis, etc:
For raw data (DataDeliveryServlet, DatasetDeliveryServlet):
{panel}
/data
/dataset
{panel}
For RDF streams (RDFProductServlet, RDFDatasetServlet):
{panel}
/rdf
/rdf/dataset
{panel}
For RSS streams (RSSProductServlet, RSSProductTransferServlet):
{panel}
/viewRecent
/viewTransfers
{panel}
As well as keeping these intact, it might also be useful for us to define a consistent URL
scheme/plan that will fit well with extended features we'd like to introduce later. For example,
we could have something like this:
{panel}
/[format]/[type]?parameters
{panel}
Where [format] is the output format and [type] can be 'product', 'dataset', 'transfers', etc.,
e.g.
{panel}
/rdf/product
/rss/dataset
/json/transfers
{panel}
Or we could specify the format as a parameter, e.g.:
{panel}
/product?format=JSON...
/transfers?format=RSS...
/dataset?format=RDF...
{panel}
I'm sure there are many alternative arrangements we could experiment with!
Regarding GSoC, it seems that Apache prefers applications from new recruits rather than students
who have already participated in previous years.[1] Since I participated in GSoC last year
with Apache OODT, I've decided not to apply this year after all. But I'd like to work on
OODT-605 anyway as a normal non-GSoC project. I'm happy to do the work if that's ok with
everyone and will gladly accept advice, guidance, etc from the OODT community. In fact, it
would be awesome to work together with you on this Rishi under your guidance, if you have
time available.
Ross
[1] http://community.apache.org/mentee-ranking-process.html
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ross Laidlaw updated OODT-605:
------------------------------
Labels: (was: gsoc2013)
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645804#comment-13645804
]
Ross Laidlaw edited comment on OODT-605 at 4/30/13 6:18 PM:
------------------------------------------------------------
Hi Rishi,
Many thanks for your comments and advice, much appreciated!
I like your comment about a JAX-RS webapp being more extensible. Hopefully we can write/design
the code in such a way that we can easily add new output formats (and configurations too).
I can see advantages of keeping the same URL format as before - for example, existing users
of OODT wouldn't need to reconfigure their projects to use the new system. Was this the main
reason you were thinking of too?
For reference for anyone looking at this JIRA issue, here's a list of the main URLs for the
CAS-Product webapp that I found in the classes, documentation, wikis, etc:
For raw data (DataDeliveryServlet, DatasetDeliveryServlet):
{panel}
/data
/dataset
{panel}
For RDF streams (RDFProductServlet, RDFDatasetServlet):
{panel}
/rdf
/rdf/dataset
{panel}
For RSS streams (RSSProductServlet, RSSProductTransferServlet):
{panel}
/viewRecent
/viewTransfers
{panel}
As well as keeping these intact, it might also be useful for us to define a consistent URL
scheme/plan that will fit well with extended features we'd like to introduce later. For example,
we could have something like this:
{panel}
/[format]/[type]?parameters
{panel}
Where [format] is the output format and [type] can be 'product', 'dataset', 'transfers', etc.,
e.g.
{panel}
/rdf/product
/rss/dataset
/json/transfers
{panel}
Or we could specify the format as a parameter, e.g.:
{panel}
/product?format=JSON...
/transfers?format=RSS...
/dataset?format=RDF...
{panel}
I'm sure there are many alternative arrangements we could experiment with!
Regarding GSoC, it seems that Apache prefers applications from new recruits rather than students
who have already participated in previous years.[1] Since I participated in GSoC last year
with Apache OODT, I've decided not to apply this year after all. But I'd like to work on
OODT-605 anyway as a normal non-GSoC project. I'm happy to do the work if that's ok with
everyone and will gladly accept advice, guidance, etc from the OODT community. In fact, it
would be awesome to work together with you on this Rishi under your guidance, if you have
time available.
Ross
[1] http://community.apache.org/mentee-ranking-process.html
was (Author: rlaidlaw):
Hi Rishi,
Many thanks for your comments and advice, much appreciated!
I like your comment about a JAX-RS webapp being more extensible. Hopefully we can write/design
the code in such a way that we can easily add new output formats (and configurations too).
I can see advantages of keeping the same URL format as before - for example, existing users
of OODT wouldn't need to reconfigure their projects to use the new system. Was this the main
reason you were thinking of too?
For reference for anyone looking at this JIRA issue, here's a list of the main URLs I found
in the classes, documentation, wikis, etc:
For raw data (DataDeliveryServlet, DatasetDeliveryServlet):
{panel}
/data
/dataset
{panel}
For RDF streams (RDFProductServlet, RDFDatasetServlet):
{panel}
/rdf
/rdf/dataset
{panel}
For RSS streams (RSSProductServlet, RSSProductTransferServlet):
{panel}
/viewRecent
/viewTransfers
{panel}
As well as keeping these intact, it might also be useful for us to define a consistent URL
scheme/plan that will fit well with extended features we'd like to introduce later. For example,
we could have something like this:
{panel}
/[format]/[type]?parameters
{panel}
Where [format] is the output format and [type] can be 'product', 'dataset', 'transfers', etc.,
e.g.
{panel}
/rdf/product
/rss/dataset
/json/transfers
{panel}
Or we could specify the format as a parameter, e.g.:
{panel}
/product?format=JSON...
/transfers?format=RSS...
/dataset?format=RDF...
{panel}
I'm sure there are many alternative arrangements we could experiment with!
Regarding GSoC, it seems that Apache prefers applications from new recruits rather than students
who have already participated in previous years.[1] Since I participated in GSoC last year
with Apache OODT, I've decided not to apply this year after all. But I'd like to work on
OODT-605 anyway as a normal non-GSoC project. I'm happy to do the work if that's ok with
everyone and will gladly accept advice, guidance, etc from the OODT community. In fact, it
would be awesome to work together with you on this Rishi under your guidance, if you have
time available.
Ross
[1] http://community.apache.org/mentee-ranking-process.html
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645804#comment-13645804
]
Ross Laidlaw edited comment on OODT-605 at 4/30/13 6:14 PM:
------------------------------------------------------------
Hi Rishi,
Many thanks for your comments and advice, much appreciated!
I like your comment about a JAX-RS webapp being more extensible. Hopefully we can write/design
the code in such a way that we can easily add new output formats (and configurations too).
I can see advantages of keeping the same URL format as before - for example, existing users
of OODT wouldn't need to reconfigure their projects to use the new system. Was this the main
reason you were thinking of too?
For reference for anyone looking at this JIRA issue, here's a list of the main URLs I found
in the classes, documentation, wikis, etc:
For raw data (DataDeliveryServlet, DatasetDeliveryServlet):
{panel}
/data
/dataset
{panel}
For RDF streams (RDFProductServlet, RDFDatasetServlet):
{panel}
/rdf
/rdf/dataset
{panel}
For RSS streams (RSSProductServlet, RSSProductTransferServlet):
{panel}
/viewRecent
/viewTransfers
{panel}
As well as keeping these intact, it might also be useful for us to define a consistent URL
scheme/plan that will fit well with extended features we'd like to introduce later. For example,
we could have something like this:
{panel}
/[format]/[type]?parameters
{panel}
Where [format] is the output format and [type] can be 'product', 'dataset', 'transfers', etc.,
e.g.
{panel}
/rdf/product
/rss/dataset
/json/transfers
{panel}
Or we could specify the format as a parameter, e.g.:
{panel}
/product?format=JSON...
/transfers?format=RSS...
/dataset?format=RDF...
{panel}
I'm sure there are many alternative arrangements we could experiment with!
Regarding GSoC, it seems that Apache prefers applications from new recruits rather than students
who have already participated in previous years.[1] Since I participated in GSoC last year
with Apache OODT, I've decided not to apply this year after all. But I'd like to work on
OODT-605 anyway as a normal non-GSoC project. I'm happy to do the work if that's ok with
everyone and will gladly accept advice, guidance, etc from the OODT community. In fact, it
would be awesome to work together with you on this Rishi under your guidance, if you have
time available.
Ross
[1] http://community.apache.org/mentee-ranking-process.html
was (Author: rlaidlaw):
Hi Rishi,
Many thanks for your comments and advice, much appreciated!
I like your comment about a JAX-RS webapp being more extensible. Hopefully we can write/design
the code in such a way that we can easily add new output formats (and configurations too).
I can see advantages of keeping the same URL format as before - for example, existing users
of OODT wouldn't need to reconfigure their projects to use the new system. Was this the main
reason you were thinking of too?
For reference for anyone looking at this JIRA issue, here's a list of the main URLs I found
in the classes, documentation, wikis, etc:
For raw data (DataDeliveryServlet, DatasetDeliveryServlet):
{panel}
/data
/dataset
{panel}
For RDF streams (RDFProductServlet, RDFDatasetServlet):
{panel}
/rdf
/rdf/dataset
{panel}
For RSS streams (RSSProductServlet, RSSProductTransferServlet):
{panel}
/viewRecent
/viewTransfers
{panel}
As well as keeping these intact, it might also be useful for us to define a consistent URL
scheme/plan that will fit well with extended features we'd like to introduce later. For example,
we could have something like this:
{panel}
/[format]/[type]?parameters
{panel}
Where [format] is the output format and [type] can be 'product', 'dataset', 'transfers', etc.,
e.g.
{panel}
/rdf/product
/rss/dataset
/json/transfers
{panel}
Or we could specify the format as a parameter, e.g.:
/product?format=JSON...
/transfers?format=RSS...
/dataset?format=RDF...
I'm sure there are many alternative arrangements we could experiment with!
Regarding GSoC, it seems that Apache prefers applications from new recruits rather than students
who have already participated in previous years.[1] Since I participated in GSoC last year
with Apache OODT, I've decided not to apply this year after all. But I'd like to work on
OODT-605 anyway as a normal non-GSoC project. I'm happy to do the work if that's ok with
everyone and will gladly accept advice, guidance, etc from the OODT community. In fact, it
would be awesome to work together with you on this Rishi under your guidance, if you have
time available.
Ross
[1] http://community.apache.org/mentee-ranking-process.html
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645804#comment-13645804
]
Ross Laidlaw commented on OODT-605:
-----------------------------------
Hi Rishi,
Many thanks for your comments and advice, much appreciated!
I like your comment about a JAX-RS webapp being more extensible. Hopefully we can write/design
the code in such a way that we can easily add new output formats (and configurations too).
I can see advantages of keeping the same URL format as before - for example, existing users
of OODT wouldn't need to reconfigure their projects to use the new system. Was this the main
reason you were thinking of too?
For reference for anyone looking at this JIRA issue, here's a list of the main URLs I found
in the classes, documentation, wikis, etc:
For raw data (DataDeliveryServlet, DatasetDeliveryServlet):
{panel}
/data
/dataset
{panel}
For RDF streams (RDFProductServlet, RDFDatasetServlet):
{panel}
/rdf
/rdf/dataset
{panel}
For RSS streams (RSSProductServlet, RSSProductTransferServlet):
{panel}
/viewRecent
/viewTransfers
{panel}
As well as keeping these intact, it might also be useful for us to define a consistent URL
scheme/plan that will fit well with extended features we'd like to introduce later. For example,
we could have something like this:
{panel}
/[format]/[type]?parameters
{panel}
Where [format] is the output format and [type] can be 'product', 'dataset', 'transfers', etc.,
e.g.
{panel}
/rdf/product
/rss/dataset
/json/transfers
{panel}
Or we could specify the format as a parameter, e.g.:
/product?format=JSON...
/transfers?format=RSS...
/dataset?format=RDF...
I'm sure there are many alternative arrangements we could experiment with!
Regarding GSoC, it seems that Apache prefers applications from new recruits rather than students
who have already participated in previous years.[1] Since I participated in GSoC last year
with Apache OODT, I've decided not to apply this year after all. But I'd like to work on
OODT-605 anyway as a normal non-GSoC project. I'm happy to do the work if that's ok with
everyone and will gladly accept advice, guidance, etc from the OODT community. In fact, it
would be awesome to work together with you on this Rishi under your guidance, if you have
time available.
Ross
[1] http://community.apache.org/mentee-ranking-process.html
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645680#comment-13645680
]
Lewis John McGibbney commented on OODT-581:
-------------------------------------------
If this serves as a basis for discussion then it will be a move in the right direction. I
am happy to go to chat or skype or phone/whatever to talk through this. There is a good bit
of work to be done to bring it up in quality. Thanks
> Update and upgrade usage of Lucene core dependency to write File Manager catalogs
> ----------------------------------------------------------------------------------
>
> Key: OODT-581
> URL: https://issues.apache.org/jira/browse/OODT-581
> Project: OODT
> Issue Type: Improvement
> Components: catalog, file manager
> Reporter: Lewis John McGibbney
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.6
>
> Attachments: OODT-581-notes.txt, OODT-581.patch, OODT-581.patch
>
>
> As recently explained on the user@ list [0], FM could so with an upgrade of the lucene-core
library for improved writing of catalogs.
> We can discuss which new features we can leverage from lucene-core 4.X
> [0] http://www.mail-archive.com/user%40oodt.apache.org/msg00603.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-408.
------------------------------------
Resolution: Fixed
- patch applied in r1477690 and r1477691. Thanks Lewis!
> Drop Spring logging levels from WARNING to SEVERE
> -------------------------------------------------
>
> Key: OODT-408
> URL: https://issues.apache.org/jira/browse/OODT-408
> Project: OODT
> Issue Type: Improvement
> Components: catalog, crawler, file manager, resource manager, workflow manager
> Affects Versions: 0.4
> Environment: none
> Reporter: Brian Foster
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.6
>
> Attachments: OODT-408.patch
>
>
> change logging.properties to:
> org.springframework.beans.level = SEVERE
> org.springframework.core.level = SEVERE
> org.springframework.level = SEVERE
> org.springframework.beans.factory.level = SEVERE
> org.springframework.beans.factory.config.level = SEVERE
> org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.level = SEVERE
> org.apache.oodt.cas.crawl.util.CasPropertyPlaceholderConfigurer.level = SEVERE
> sun.net.level = SEVERE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Author: mattmann
Date: Tue Apr 30 15:34:12 2013
New Revision: 1477691
URL: http://svn.apache.org/r1477691
Log:
Drop Spring logging levels from WARNING to SEVERE
Modified:
oodt/trunk/CHANGES.txt
Modified: oodt/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/oodt/trunk/CHANGES.txt?rev=1477691&r1=1477690&r2=1477691&view=diff
==============================================================================
--- oodt/trunk/CHANGES.txt (original)
+++ oodt/trunk/CHANGES.txt Tue Apr 30 15:34:12 2013
@@ -4,6 +4,9 @@ Apache OODT Change Log
Release 0.6 - Current Development
--------------------------------------------
+* OODT-408 Drop Spring logging levels from WARNING to SEVERE (Lewis John McGibbney
+ via mattmann, bfoster)
+
* OODT-607 SciPgeWriter that is a simple MetKey template replacer (mattmann)
* OODT-606 SciPgeWriter that uses ApacheVelocity (mattmann, pramirez)
Author: mattmann
Date: Tue Apr 30 15:33:59 2013
New Revision: 1477690
URL: http://svn.apache.org/r1477690
Log:
OODT-408: Drop Spring logging levels from WARNING to SEVERE
Modified:
oodt/trunk/catalog/src/main/resources/logging.properties
oodt/trunk/crawler/src/main/resources/logging.properties
oodt/trunk/filemgr/src/main/resources/logging.properties
oodt/trunk/resource/src/main/resources/logging.properties
oodt/trunk/workflow/src/main/resources/logging.properties
Modified: oodt/trunk/catalog/src/main/resources/logging.properties
URL: http://svn.apache.org/viewvc/oodt/trunk/catalog/src/main/resources/logging.properties?rev=1477690&r1=1477689&r2=1477690&view=diff
==============================================================================
--- oodt/trunk/catalog/src/main/resources/logging.properties (original)
+++ oodt/trunk/catalog/src/main/resources/logging.properties Tue Apr 30 15:33:59 2013
@@ -45,7 +45,7 @@ httpclient.wire.level = INFO
# airs dom loggin
sun.rmi.level = INFO
-# spring logging
+# spring framework logging
org.springframework.beans.level = SEVERE
org.springframework.core.level = SEVERE
org.springframework.level = SEVERE
Modified: oodt/trunk/crawler/src/main/resources/logging.properties
URL: http://svn.apache.org/viewvc/oodt/trunk/crawler/src/main/resources/logging.properties?rev=1477690&r1=1477689&r2=1477690&view=diff
==============================================================================
--- oodt/trunk/crawler/src/main/resources/logging.properties (original)
+++ oodt/trunk/crawler/src/main/resources/logging.properties Tue Apr 30 15:33:59 2013
@@ -53,6 +53,7 @@ org.apache.commons.httpclient.level = IN
httpclient.wire.header.level = INFO
httpclient.wire.level = INFO
+# spring framework logging
org.springframework.beans.level = SEVERE
org.springframework.core.level = SEVERE
org.springframework.level = SEVERE
Modified: oodt/trunk/filemgr/src/main/resources/logging.properties
URL: http://svn.apache.org/viewvc/oodt/trunk/filemgr/src/main/resources/logging.properties?rev=1477690&r1=1477689&r2=1477690&view=diff
==============================================================================
--- oodt/trunk/filemgr/src/main/resources/logging.properties (original)
+++ oodt/trunk/filemgr/src/main/resources/logging.properties Tue Apr 30 15:33:59 2013
@@ -70,4 +70,6 @@ org.springframework.level = SEVERE
org.springframework.beans.factory.level = SEVERE
org.springframework.beans.factory.config.level = SEVERE
org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.level = SEVERE
+org.apache.oodt.cas.crawl.util.CasPropertyPlaceholderConfigurer.level = SEVERE
+sun.net.level = SEVERE
Modified: oodt/trunk/resource/src/main/resources/logging.properties
URL: http://svn.apache.org/viewvc/oodt/trunk/resource/src/main/resources/logging.properties?rev=1477690&r1=1477689&r2=1477690&view=diff
==============================================================================
--- oodt/trunk/resource/src/main/resources/logging.properties (original)
+++ oodt/trunk/resource/src/main/resources/logging.properties Tue Apr 30 15:33:59 2013
@@ -65,3 +65,5 @@ org.springframework.level = SEVERE
org.springframework.beans.factory.level = SEVERE
org.springframework.beans.factory.config.level = SEVERE
org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.level = SEVERE
+org.apache.oodt.cas.crawl.util.CasPropertyPlaceholderConfigurer.level = SEVERE
+sun.net.level = SEVERE
Modified: oodt/trunk/workflow/src/main/resources/logging.properties
URL: http://svn.apache.org/viewvc/oodt/trunk/workflow/src/main/resources/logging.properties?rev=1477690&r1=1477689&r2=1477690&view=diff
==============================================================================
--- oodt/trunk/workflow/src/main/resources/logging.properties (original)
+++ oodt/trunk/workflow/src/main/resources/logging.properties Tue Apr 30 15:33:59 2013
@@ -66,3 +66,5 @@ org.springframework.level = SEVERE
org.springframework.beans.factory.level = SEVERE
org.springframework.beans.factory.config.level = SEVERE
org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.level = SEVERE
+org.apache.oodt.cas.crawl.util.CasPropertyPlaceholderConfigurer.level = SEVERE
+sun.net.level = SEVERE
[ https://issues.apache.org/jira/browse/OODT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann reassigned OODT-408:
--------------------------------------
Assignee: Chris A. Mattmann (was: Brian Foster)
> Drop Spring logging levels from WARNING to SEVERE
> -------------------------------------------------
>
> Key: OODT-408
> URL: https://issues.apache.org/jira/browse/OODT-408
> Project: OODT
> Issue Type: Improvement
> Components: catalog, crawler, file manager, resource manager, workflow manager
> Affects Versions: 0.4
> Environment: none
> Reporter: Brian Foster
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.6
>
> Attachments: OODT-408.patch
>
>
> change logging.properties to:
> org.springframework.beans.level = SEVERE
> org.springframework.core.level = SEVERE
> org.springframework.level = SEVERE
> org.springframework.beans.factory.level = SEVERE
> org.springframework.beans.factory.config.level = SEVERE
> org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.level = SEVERE
> org.apache.oodt.cas.crawl.util.CasPropertyPlaceholderConfigurer.level = SEVERE
> sun.net.level = SEVERE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann reassigned OODT-581:
--------------------------------------
Assignee: Chris A. Mattmann
> Update and upgrade usage of Lucene core dependency to write File Manager catalogs
> ----------------------------------------------------------------------------------
>
> Key: OODT-581
> URL: https://issues.apache.org/jira/browse/OODT-581
> Project: OODT
> Issue Type: Improvement
> Components: catalog, file manager
> Reporter: Lewis John McGibbney
> Assignee: Chris A. Mattmann
> Priority: Minor
> Fix For: 0.6
>
> Attachments: OODT-581-notes.txt, OODT-581.patch, OODT-581.patch
>
>
> As recently explained on the user@ list [0], FM could so with an upgrade of the lucene-core
library for improved writing of catalogs.
> We can discuss which new features we can leverage from lucene-core 4.X
> [0] http://www.mail-archive.com/user%40oodt.apache.org/msg00603.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645665#comment-13645665
]
Chris A. Mattmann commented on OODT-581:
----------------------------------------
Thanks Lewis. I'll take a look at this this weekend.
> Update and upgrade usage of Lucene core dependency to write File Manager catalogs
> ----------------------------------------------------------------------------------
>
> Key: OODT-581
> URL: https://issues.apache.org/jira/browse/OODT-581
> Project: OODT
> Issue Type: Improvement
> Components: catalog, file manager
> Reporter: Lewis John McGibbney
> Priority: Minor
> Fix For: 0.6
>
> Attachments: OODT-581-notes.txt, OODT-581.patch, OODT-581.patch
>
>
> As recently explained on the user@ list [0], FM could so with an upgrade of the lucene-core
library for improved writing of catalogs.
> We can discuss which new features we can leverage from lucene-core 4.X
> [0] http://www.mail-archive.com/user%40oodt.apache.org/msg00603.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644308#comment-13644308
]
Rishi Verma commented on OODT-605:
----------------------------------
Hey Chris, Ross,
I would me more than happy to. Let me look into the process. Chris, if you have any direct
pointers, do let me know.
Thanks guys, looking forward to making OODT-605 a success!
rishi
> Upgrade the CAS-Product web application to use JAX-RS
> -----------------------------------------------------
>
> Key: OODT-605
> URL: https://issues.apache.org/jira/browse/OODT-605
> Project: OODT
> Issue Type: New Feature
> Components: product server
> Affects Versions: 0.6
> Reporter: Ross Laidlaw
> Assignee: Ross Laidlaw
> Labels: gsoc2013
> Fix For: 0.6
>
> Original Estimate: 3,360h
> Remaining Estimate: 3,360h
>
> This is the parent JIRA issue for adding JAX-RS support to the CAS-Product web application
(webapp/fmprod).
> The primary goal is to use Apache CXF's JAX-RS implementation to provide all of the functionality
of the existing RSS, RDF and data servlets in the CAS-Product web application, i.e. to provide
various ways of accessing File Manager products and product sets using JAX-RS.
> After completing the primary goal, a secondary goal would be to extend the service to
provide additional ways of accessing File Manager products (e.g. providing different output
formats for metadata, and using additional parameters to find and filter lists of products
and product groups).
> I'd like to volunteer to work on this and I'm hoping to do it as a Google Summer of Code
project.
> I'll use this JIRA issue to record the schedule and plans for the project. I'm hoping
that if other members of the OODT community are interested they can find information here
and make comments, suggestions, etc. and see how everything's progressing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.apache.org/jira/browse/OODT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated OODT-408:
--------------------------------------
Attachment: OODT-408.patch
Patch for trunk
> Drop Spring logging levels from WARNING to SEVERE
> -------------------------------------------------
>
> Key: OODT-408
> URL: https://issues.apache.org/jira/browse/OODT-408
> Project: OODT
> Issue Type: Improvement
> Components: catalog, crawler, file manager, resource manager, workflow manager
> Affects Versions: 0.4
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.6
>
> Attachments: OODT-408.patch
>
>
> change logging.properties to:
> org.springframework.beans.level = SEVERE
> org.springframework.core.level = SEVERE
> org.springframework.level = SEVERE
> org.springframework.beans.factory.level = SEVERE
> org.springframework.beans.factory.config.level = SEVERE
> org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.level = SEVERE
> org.apache.oodt.cas.crawl.util.CasPropertyPlaceholderConfigurer.level = SEVERE
> sun.net.level = SEVERE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira