Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Seba P
    @sebap
    hi
    Seba P
    @sebap
    Hi I am getting this error
    Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors.
    Tracing compile failure path for type 'io.reinert.requestor.RequestDispatcherImpl'
    [ERROR] Errors in 'io/reinert/requestor/RequestDispatcherImpl.java'
    [ERROR] Line 79: The constructor Request(XMLHttpRequest, int, RequestCallback) is not visible
    [ERROR] Line 88: The method fireOnResponseReceived(RequestCallback) from the type Request is not visible
    [ERROR] Hint: Your source appears not to live underneath a subpackage called 'client'; no problem, but you'll need to use the <source> directive in your module to make it accessible
    Unification traversed 19119 fields and methods and 1797 types. 1761 are considered part of the current module and 1761 had all of their fields and methods traversed.
    Any ideas what could I be missing?
    Danilo Reinert
    @reinert
    hi @sebap
    that's because the compiler is not seeing my implementation of the com.google.gwt.http.client.Request class
    I had to override two modifiers of this class to properly use it
    And the only possible way was overwriting it c
    changing the constructor e the referred method to public access
    and*
    so
    Danilo Reinert
    @reinert
    in order to the compiler consider my implementation instead of GWT original one, the declaration of Requestor dependencies must precede the declaration of the GWT dependencies
    This was already in Getting Started section, but now I gave greater emphasis
    I updated it to be more clear in this explanation
    Seba P
    @sebap
    Nice, thanks! will give it a try now
    Danilo Reinert
    @reinert
    Ok. I am here now, ask me anything if you need.
    @kerbymart
    @kerbymart
    Still active?
    Danilo Reinert
    @reinert
    Sure!
    how can I help you?
    @kerbymart
    @kerbymart
    Just checking out requestor
    Cool project
    Danilo Reinert
    @reinert
    thanks!
    @kerbymart
    @kerbymart
    What's your motivation for the project?
    Danilo Reinert
    @reinert
    a bunch of things
    I find requesting in GWT too trouble
    and it shouldn't be this way
    @kerbymart
    @kerbymart
    I see, how do you handle POJO mapping, when sending and receiving data from endpoints
    Danilo Reinert
    @reinert
    Requestor has a very decoupled API
    Everything in it is thought to be implemented apart
    so it's with serialization
    you can integrate any serialization library with requestor
    I already provided two options for it
    serialization by AutoBeans (JavaBean interfaces only)
    and serialization by gwt-jackson (POJO mapping)
    @kerbymart
    @kerbymart
    Serialization/Deserialization is quite cumbersome with plain GWT, right now we use Restlet GWT to handle that, I think you should add this feature
    Danilo Reinert
    @reinert
    it's already there
    working
    ;)
    did you checkout the showcase?
    let me put some links here...
    there's the documentation about POJO mappin
    as you can see there
    if you enable requestor-gwtjackson in your project
    and annotate your pojos with @Json
    then des/serialization for they will be enabled
    Danilo Reinert
    @reinert
    I realized that showcase don't have an example of using gwt-jackson
    maybe I should create some examples for serialization specifically
    @kerbymart
    @kerbymart
    @reinert cool, will try this