...complex stuff, when there is time I try to follow your approach. At the moment I do this investigations in my leisure time.

...you write that you test "HTTP invoker" - usually HTTP is known as bottleneck and request response coupled?? did you receive an acceptable performance?

You speak about loading the right bundle

• If you want have Fat Client you have "Services API" + "Services Implementation" bundles in your OSGi container.
  
• If you want have Client/Server architecture you have :
  
  
  
  
  1. on the Client Side "Services API" + ("Services REST Client" or "Services Spring HttpInvoker importer").
     
  2. on the Server Side "Services API" + ("Services REST Services" or "Services Spring HttpInvoker exporter").
     
  
  

and that your problem is now:
"My big problem for the moment is to serialize the Spring Data structure used for pagination (Page+Pageable interface) in our service."
What-#s your goal when you serialize Spring Data structure?

package org.dynaresume.services;

import org.dynaresume.domain.hr.Resume;
import org.springframework.data.domain.Page;
import org.springframework.data.domain.Pageable;

public interface ResumeService {
        Iterable<Resume> findAll();

        Resume findById(long id);

        Resume save(Resume resume);
        
        long count();

        Page<Resume> findByFirstNameAndLastName(String firstName,
                        String lastName, Pageable pageable);
}