Dashboard > WSO2 ESB > Home > Planning and Review meeting - 20~21 Feb 2007
  WSO2 ESB Log in | Register   View a printable version of the current page.  
  Planning and Review meeting - 20~21 Feb 2007
Added by Asankha Perera , last edited by Asankha Perera on Feb 23, 2007  (view change)
Labels: 
(None)

Issue Description JIRA?
Target
Closed?
1 Use NIO SSL transport to host admin console instead of Jetty or Tomcat
ESBJAVA-76 1.0 y
2
Include a link to a getting started guide from the home page of the ESB
ESBJAVA-77 1.0
y
3
Support role based administration for the ESB
  > 1.0
FUTURE
4
Add proxy service should support giving a WSDL URL or browsing one off the
file system, then inline it (cache) and create a proxy for it. The endpoint address and policy etc

should be picked from the WSDL  
  1.0 TODO
5 Specify the Proxy Service name on the first page of the wizard
done 1.0
y
6 Reorder menu items as Proxy Svcs, Endpoints, Sequences and Registry
ESBJAVA-77 1.0
y
7
Use a UI library to render the add mediator popup and any other elements
    FUTURE
8 Remove JSON, POX etc.. and clean up mediators
done   y
9 Provide message stating "No data available" when pie charts cannot be shown
ESBJAVA-77 1.0
y
10
Fold 'add mediator' button to right hand button bar. After/before to be set with shift up/down
done 1.0
y
11
Proxy services should be able to load balance and/or fail over without an external sequence
Proxy services should support inline in/out and fault sequences and inline wsdl and endpoint definitions
Proxy services should support the specification of both in/out/fault sequeces AND endpoints
SYNAPSE-58   y
12
WSDL endpoints - pick policy, RM, Sec from it
SYNAPSE-59
  y
13
Commit throttle, LB and FO mediators to Synapse - keeping the throttle code from our commons
SYNAPSE-60
SYNAPSE-61  
  y
14
Remove marketing stuff from login page and make it simple
ESBJAVA-77 1.0
y
15
Start script
- admin services and UI
- allow only localhost access
- detached console (only admin services)
    - read only access (i.e. to view logs, look at stats etc. but not make any config changes)
- no admin services. file configuration only           
    FUTURE
16 Make Send not stop the current sequence
SYNAPSE-57 1.0
y
17
Inline WSDL, Endpoint and even Sequences within Proxies
  1.0
*
18
Rename proxy service 'property' as 'parameter'
SYNAPSE-58 1.0
y

Fix JMS transport to not have parameters within parameters
 
TODO
20
Extend endpoints as follows:
<endpoint name="string" [address="url"] [key="string"] protocol="soap|pox">
    <loadbalance policy="roundrobin">
       <address>*
       <wsdl>*

       <failover policy="exponentialretry">*
          <address>*
          <wsdl>*
          ... extensibility
       </failover>

       .... extensibility.....
    <loadbalance>
    .. extensibility ..


    <enableRM [policy="something"]/>?
    <enableSec [policy="key"]/>?
    <enableAddressing/>?
    .. extensibility ..
 </endpoint>

SYNAPSE-59   y
21 Replace
<definitions>
  <set-property name="string" [value="string"] [src="url" ] [key="string"]>
       <inline-xml/>?
  <set-property/>
</definitions>

with
<definitions>
   <!- local keys ALWAYS override remote keys ->
  <registry-entry key="string"  [src="url" ]>
       string? |  <inline-xml/>?
  <registry-entry/>
</definitions>

<endpoint key="string"/>
The concept of properties would be replaced by a consistent registry interface. It is possible to define
registry-entries within a synapse configuration, to override any existing keys off the remote registry.
Thus a user does not always have to define a registry key through another level of indirection.
    TODO
22 Replace 'property' within registry element to parameter. Support only one single registry.

<registry provider="string"/>
  <parameter name="string">value</parameter>
</registry>
    TODO
23 Support transactional resources as follows: Once a key is looked up from a remote registry during message
processing, always keep a reference (i.e. similar to copying it) to it from the local message context property bag.
This way we are making sure that any subsequent reads for the same key will not fetch a newer version off the
remote registry as we will always pick the local reference. Make sure that any responses also see the same 
keys seen by the request in a similar manner.
SYNAPSE-62   y
24 Replace <endpoint ref=".."> and <sequence ref="..."> with <endpoint key=".."> and <sequence key="..">     TODO
         
         
         
         
         

Powered by a free Atlassian Confluence Open Source Project License granted to WSO2 Inc.. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators