9:16 a.m.
One thing I forgot to mention is that you don't need to create a fork of the core
console like SwitchYard is doing. The as7-core project in Switchyard is simply a holding
place for the extensibility features. If that project is current enough for you (it
currently pulls in the console code used in 7.1.Final), you should be able to use it as
your "core" dependency (i.e. you would only have to worry about your extension).
The dependency information is:
org.switchyard.console:switchyard-console-as7-core:0.4.0-SNAPSHOT.
Note, this is only temporary until the extension mechanism is in the core console itself.
At that point, the as7-core project in SwitchYard will go away.
Best,
Rob
----- Original Message -----
What Rob describe is what we encourage everyone todo: build on the
extension mechanism. This has several benefits:
- no duplicate web interfaces on AS7: which means everything will be
accessed from the same place
- retain the ability to build standalone interfaces: if needed you
could still compile a stripped down console, customized for your
project
- leverage all the goodies we already have: layout, look&feel, error
handling, authentication, logging, etc: you certainly don't want to
duplicate this part.
- consistent user experience: executing management in one place only
and the way you are used to it.
We don't yet have the extension mechanism merged with the core
codebase, but this should not prevent you from getting started.
Follow the outline Rib has send around and we'll gladly assist you in
building the picketlink extensions.
Please let me know if you have any questions.
/Heiko
On Mar 5, 2012, at 6:52 PM, Rob Cernich wrote:
> Hey Anil,
>
> SwitchYard has successfully integrated the SY console into the core
> AS7 console as an extension. We did have to tweak the core
> console to support extensions, but I believe that support will be
> part of the core console at some point. Here are some links that
> might help:
>
> Tweaks to the core console:
> https://github.com/jboss-switchyard/console/tree/master/as7-core
> SwitchYard extension:
> https://github.com/jboss-switchyard/console/tree/master/gwt
> Integrated console:
> https://github.com/jboss-switchyard/console/tree/master/app
>
> The basic extension mechanism is exemplified here:
> https://github.com/rcernich/fools-errands/tree/master/modular-mvp
> (at some point, this will be moved into the ballroom project)
>
> The drawback to this approach is that the "final" console
> application needs to incorporate all extensions (OBJ style). For
> example, if PL was implemented as an extension and SY was also
> included in the distro, there would need to be a project that
> includes AS core, PL and SY into the final JAR. The piece that is
> still missing is how to do this as part of the install (i.e.
> dynamically). (Then again, the console disables/hides
> functionality that is not supported by the runtime, so,
> eventually, there could be a single project that simply bundles
> everything together.)
>
> Best,
> Rob
>
> ----- Original Message -----
>> Heiko,
>> wanted your opinion on this.
>>
>> Pedro Silva is working on a PicketLink Console using GWT and uses
>> Ballroom (https://community.jboss.org/wiki/BallroomLookFeel).
>> Since
>> PL
>> jars are shipped as part of JBoss AS7.1.x, users will definitely
>> like
>> a
>> console to configure PL SSO etc.
>>
>> So we are debating around: a) developing a standalone PL console
>> or
>> b)
>> try to have it as an *extension* of the AS admin console to give a
>> consistent user experience.
>>
>> If we develop a standalone PL console, it will come packaged in a
>> AS7
>> instance.
>>
>> Any guidance for console writers who are integrating with AS7.
>>
>> Regards,
>> Anil
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev