Suresh, Mark,
We will need to plan for this. We need to take this up for discussion at
admin iteam meeting. Jane/Prashanth, please add it to agenda.
Few questions though:
- Some of the JBI admin commands were added in core GlassFish V2
offering, while the new proposed commands are to be added as
addons. Is that acceptable or would you like to have all the
JBI commands integrated as addon in a future JBI release?
- What about admin console screens for the functionality corresponding
to new commands?
- Is there a tentative schedule for your next release?
- Kedar
Suresh Potiny wrote:
> Kedar,
>
> We need a solution for v2. We are okay modifying this strategy for v3
> (we have to look at a number
> of things for v3 anyway).
>
> Suresh
>
> Kedar Mhaswade wrote:
>> Hi Mark,
>>
>> This is available in some shape and form and we need to finalize it
>> before
>> making it a public interface. Personally, I prefer to call it the admin
>> addons. This is because what is true with commands is also true with
>> admin
>> console or any programmatic interface that an addon would like to
>> provide.
>>
>> Unfortunately, we are still trying to decide what the best way forward
>> is,
>> because we have to look for promise of V3 in this regard. There are
>> differences
>> in how you would do in V2 and V3.
>>
>> Is your next release planned along with V3 release? If it is, then we
>> will
>> certainly have a way to do this. If not, we might have to do some work in
>> releasing a solution that may not work with V3.
>>
>> Please let me know ...
>>
>> Regards,
>> Kedar
>>
>> Mark S White wrote:
>>> Hello,
>>>
>>> I am the engineering manager for the team responsible for the JBI /
>>> Open ESB runtime and
>>> the associated ant, asadmin, and admin console support. Our runtime
>>> is integrated into the
>>> GlassFish runtime, and in the past we have added new ant tasks,
>>> asadmin commands, and
>>> admin console screens to support our product.
>>>
>>> For our next release, we need to add a number of new commands to
>>> asadmin. We understand
>>> that some work has been done to create an extension mechanism for
>>> asadmin whereby
>>> commands can be added dynamically without changes to the base asadmin
>>> code. We would
>>> very much like to use this mechanism to add asadmin commands in
>>> support of our next release.
>>>
>>> Could someone provide us information on whether or not this mechanism
>>> exists or is planned,
>>> and how we might be able to use it? This is a critical issue for
>>> allowing us to implement new
>>> functionality in a time frame that aligns with our product release
>>> schedule.
>>>
>>> thanks very much,
>>> Mark White
>>>
>