[JBoss JIRA] Closed: (JBESB-19) Create HTTP listener/receiver
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-19?page=all ]
Mark Little closed JBESB-19.
----------------------------
> Create HTTP listener/receiver
> -----------------------------
>
> Key: JBESB-19
> URL: http://jira.jboss.com/jira/browse/JBESB-19
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Distribution
> Reporter: Mark Little
> Assigned To: Johan Kumps
> Fix For: 4.0
>
> Attachments: AbstractConnectorServlet.java, NoEndpointSpecifiedException.java, RestConnectorServlet.java
>
> Time Spent: 1 day
> Remaining Estimate: 0 minutes
>
> Either create one or leverage something that already exists (though for inclusion with JBossESB it should have a small footprint, i.e., not drag in a load of other non-essential classes).
> What this means is that we need an HTTP-server side stack so that clients can send HTTP requests (PUT, POST, GET) and the ESB will interpret them appropriately. Currently JDK libraries provide only the client-side to HTTP interactions and no server-side.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month
[JBoss JIRA] Closed: (JBESB-42) Remove hard-coded dependencies in existing code
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-42?page=all ]
Mark Little closed JBESB-42.
----------------------------
> Remove hard-coded dependencies in existing code
> -----------------------------------------------
>
> Key: JBESB-42
> URL: http://jira.jboss.com/jira/browse/JBESB-42
> Project: JBoss ESB
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: ESB Core
> Reporter: Mark Little
> Assigned To: Esteban Schifman
> Fix For: 4.0 Alpha 1
>
> Time Spent: 2 days
> Remaining Estimate: 0 minutes
>
> The connection to the centralized services was almost hardcoded instead of providing factory classes that could be configured at run time (the good news is that it was hardcoded to a JBoss application server). Same situation with the persistence method for storing parameters, which is a key element of Rosetta. The only persistent storage for run time configuration parameters was an LDAP repository, with a hardcoded root path, username and password.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month