Lucas Holmquist lholmquist

HMM

//create a basic notifier with some settings

AeroGear.Notifier({
name: "notifications",
settings: {
    connectURL:  "/eventbus",
    autoConnect: true,

onConnect: function() {

 //Auth enroll
 
 if ( options.contentType ) {
        extraOptions.contentType = options.contentType;
    } else if ( agAuth ) {
        extraOptions.contentType = "application/json";
    }
    if ( options.dataType ) {
        extraOptions.dataType = options.dataType;

} else if ( agAuth ) {

I was trying out the js paging stuff with github and i noticed something that i think is a bug.

Here is the pipeline/pipe setup

var pipeline = AeroGear.Pipeline(
    {
        name: "githubcommits",
        settings: {

baseURL: "https://api.github.com/repos/lholmquist/aerogear-js/",

Custom Aerogear.js Builder

Prototype here: http://aerogearjsbuilder-lholmqui.rhcloud.com/

myrepo: [email protected]:lholmquist/aerogearjsbuilder.git

There is still a couple of minor tweaks that i need, like better error handling and CORS support possible. although it uses an iframe, so maybe not

This is the way it works.

I wonder if we could put the AeroGear.isArray function in the aerogear.core.js file. for some reason i feel like it used to be there

currently it is in the aerogear.utilities.js file which also has the aerogear.ajax function. if some one makes a custom build of just datamanager, which needs the isArray function but not the ajax stuff, they are getting a little bit of extra code that they don't need.

Actually the core file needs the isArray function, and since everything depends on the core, there will be situations where custom builds will get more than they need.

The size difference is proabably trivial, but smaller is better in mobile

I know we really haven't talked about cordova plugins to much, but i want to just get this thought down so i didn't forget about it.

would it make sense to have a cordova plugin for accessing the core data stuff from our iOS libs, that is once it's ready.

I know cordova has a storage api, but it looks like it is just based on the W3C web storage/web sql specs

i guess i was thinking this is how it would work:

Possibley have an aerogear.js datamanager plugin for the front end that then calls the aerogear ios libs coredata plugin

I'm not sure if this is possible yet, but i'm trying to do a POST to the aerogear-controller-demo from our js libs

$( function() {
var pipeline = AeroGear.Pipeline(
    {
        name: "controllerPipe",
        settings: {
            baseURL: "http://localhost:8080/aerogear-controller-demo",

endpoint: "/cars"

Modified this route, and was successful

route()
    .from("/delorean")
    .on(RequestMethod.GET).produces(MediaType.JSON.toString())
    .to(Home.class).anotherPage();

Kept getting the same error with this one though

	Title: Open Source Libraries for Mobile Connectivity

	Persistence, Security, Connectivity. All 3 are an important part of an enterprise application.
	But how does this translate to the mobile environment. With a range a technologies to support
	and develop with, things can get messy quickly. In this session you will see how
	AeroGear solves these concerns and how it allows developers
	to access server side components using a common API across multiple platforms

	INFO \| New I/O worker #4 \| ID-lincolnhawk-home-49880-1365533783487-0-3 >>> (user-registration) from(vertx://demo.user-registration) --> stomp://queue:/user-registration <<< Pattern:InOnly, Headers:{breadcrumbId=ID-lincolnhawk-home-49880-1365533783487-0-4}, BodyType:org.vertx.java.core.buffer.Buffer, Body:{"platform":"gplus","identifier":"106194804223969570536","profile_pic_url":"https://lh6.googleusercontent.com/-DyAOK5CbWJU/AAAAAAAAAAI/AAAAAAAAAhY/GclqjWxj0-g/photo.jpg","name":"Lucas Holmquist","email":"[email protected]"}
	WARN \| New I/O worker #4 \| Cannot determine specific JmsMessage type to use from body class. Will use generic JmsMessage. Body class: org.vertx.java.core.buffer.Buffer. If you want to send a POJO then your class might need to implement java.io.Serializable, or you can force a specific type by setting the jmsMessageType option on the JMS endpoint.
	INFO \| New I/O worker #4 \| ID-lincolnhawk-home-49880-1365533783487-0-3 >>> (user-registration) from(vertx://demo.user-registration)