Hi,

When I tried the dropping 2010 into the JAX-B section of the pom, I did also droped in the xsd files. I cannot remember the exact issues but I didn't make any progress :-(

2 issues lead me to use a local copy of the wsdl and xsd files, 1) the missing endpoint and 2) access to the wsdl (at build time, although JAX-WS seems to also need access at runtime).

I did have success with the JAX-WS maven plugin, but struggled when actually using it.

On the negative side, I don't "think" that the EWSJavaAPI supports impersonation. This might be an issue for folks who do not have access to the users password.

Cheers,
Anthony.


On 10/11/11 15:03, Jen Bourey wrote:
You actually don't really need a local WSDL; we added it to the project
because the one that's deployed in a lot of Microsoft implementations by
default is missing a key XML snippet and doesn't actually work. If your
WSDL works, you could just point it to the live one. My understanding is
that 2007 and 2010 are actually very close. If there are differences,
you might need to update the two XSD files with the ones on your server.
If you're interested in trying to get that working against your campus
server, let me know if there's anything we can do to help.

Anyway, about the MS dependency: It's great to hear that that's easy to
use. I took a look at the license, and it looks like the Microsoft
license is on our A list, so including it in the project wouldn't be an
issue from a licensing perspective.

- Jen

On Thu, Nov 10, 2011 at 9:32 AM, Anthony Colebourne
<[email protected]
<mailto:[email protected]>> wrote:

    Hi,

    I believe the current Jasig Exchange integrations are Exchange2008
    not 2010? (I dropped my local version of the 2010 wsdl into the
    calendar's maven config but things went badly wrong).

    I too have a JAX-WS generated implementation of the webservice, but
    found it very complicated to use.

    In contrast the EWSJavaAPI is "ridiculously simple". Within
    practically 10 mins on a test bed I was able to pull all the data I
    needed from Email, Calendar, Tasks and Contacts with no local wsdl
    or maven plugin to manage.

    -- Anthony.


    On 10/11/11 14:22, Jen Bourey wrote:

        Hey Anthony,

        The calendar portlet actually already has an Exchange adapter
        out of the
        box. It uses spring-ws to connect to the services, which seems
        not too
        require too much custom code. I know Nick is also currently
        doing some
        EWS integration into the Scheduler too. Maybe there's an
        opportunity to
        create some documentation and best practices around Exchange
        integration? How've you found the Java library your'e using to
        be so far?

        - Jen

        On Thu, Nov 10, 2011 at 9:21 AM, Jen Bourey
        <[email protected] <mailto:[email protected]>
        <mailto:jennifer.bourey@gmail.__com
        <mailto:[email protected]>>> wrote:

        Hey Anthony,

        The calendar portlet actually already has an Exchange adapter out of
        the box. It uses spring-ws to connect to the services, which seems
        not too require too much custom code. I know Nick is also currently
        doing some EWS integration into the Scheduler too. Maybe there's an
        opportunity to create some documentation and best practices around
        Exchange integration? How've you found the Java library your'e using
        to be so far?

        - Jen



        On Nov 9, 2011, at 7:31 PM, Anthony Colebourne wrote:

            cc: [email protected] <mailto:[email protected]>
            <mailto:[email protected] <mailto:[email protected]>>


            Hi,

            I want to contribute some Exchange 2010 adapters (development in
            progress).
            * CalendarPortlet
            * NotificationsPortlet
            Also in future
            * ContactsPortlet
            * EmailPreviewPortlet
            * ScheduleAssistant

            The jar is available form
            
http://archive.msdn.microsoft.__com/ewsjavaapi/Release/__ProjectReleases.aspx?__ReleaseId=5754
            
<http://archive.msdn.microsoft.com/ewsjavaapi/Release/ProjectReleases.aspx?ReleaseId=5754>

            Would it be possible to get this into Jasig's Maven repo?

            It has the following dependencies:
            Apache Commons HttpClient 3.1
            Apache Commons Codec 1.4
            Apache Commons Logging 1.1.1
            JCIFS 1.3.15

            JCIFS is available from http://maven.jahia.org/maven2/
            Others available in Maven central.

            Could these dependencies also be made available?

            Thanks,
            Anthony.

            --
            You are currently subscribed to [email protected]
            <mailto:[email protected]>
            <mailto:[email protected]__sig.org
            <mailto:[email protected]>> as:
            [email protected] <mailto:[email protected]>
            <mailto:jennifer.bourey@gmail.__com
            <mailto:[email protected]>>

            To unsubscribe, change settings or access archives, see
            http://www.ja-sig.org/wiki/__display/JSG/uportal-dev
            <http://www.ja-sig.org/wiki/display/JSG/uportal-dev>





        --
        Jen Bourey

        --

        You are currently subscribed to [email protected]
        <mailto:[email protected]> as:
        anthony.colebourne@manchester.__ac.uk
        <mailto:[email protected]>

        To unsubscribe, change settings or access archives, see
        http://www.ja-sig.org/wiki/__display/JSG/uportal-dev
        <http://www.ja-sig.org/wiki/display/JSG/uportal-dev>




--
Jen Bourey

--

You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


--
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Reply via email to