[ http://jira.jboss.com/jira/browse/JBESB-432?page=all ]
Kevin Conner updated JBESB-432:
-------------------------------
Assignee: (was: Kurt Stam)
> Contract definition language
> ----------------------------
>
> Key: JBESB-432
> URL: http://jira.jboss.com/jira/browse/JBESB-432
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Reporter: Mark Little
> Fix For: 5.0
>
>
> A non-WSDL based contract definition language for the ESB and services is essential.
--
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
[ http://jira.jboss.com/jira/browse/JBESB-413?page=all ]
Kevin Conner updated JBESB-413:
-------------------------------
Assignee: (was: Kurt Stam)
> Static routers
> --------------
>
> Key: JBESB-413
> URL: http://jira.jboss.com/jira/browse/JBESB-413
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Content Based Routing
> Affects Versions: 4.2 Milestone Release 2
> Reporter: Mark Little
> Fix For: 5.0
>
>
> Multicast, Chain, Static Recipient List, XML Splitter, List/String Splitter, Exception Router, Filtering on object type router
--
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
[ http://jira.jboss.com/jira/browse/JBESB-419?page=all ]
Kevin Conner updated JBESB-419:
-------------------------------
Assignee: (was: Kurt Stam)
> Advanced splitter
> -----------------
>
> Key: JBESB-419
> URL: http://jira.jboss.com/jira/browse/JBESB-419
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Content Based Routing
> Affects Versions: 4.2 Milestone Release 2
> Reporter: Mark Little
> Priority: Minor
> Fix For: 5.0
>
>
> Driven by Smooks/Rules/jBPM
--
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
[ http://jira.jboss.com/jira/browse/JBESB-355?page=all ]
Kevin Conner updated JBESB-355:
-------------------------------
Assignee: (was: Kurt Stam)
> Registering EPRs should be optional
> -----------------------------------
>
> Key: JBESB-355
> URL: http://jira.jboss.com/jira/browse/JBESB-355
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Affects Versions: 4.0 CR1
> Reporter: Mark Little
> Fix For: 5.0
>
>
> Currently registering EPRs with the Registry is mandatory (within the code). It should be an optional choice for developers/deployers. Plus, the failure to register shouldn't necessarily mean the service should exit: that may be an implementation choice too.
--
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
[ http://jira.jboss.com/jira/browse/JBESB-233?page=all ]
Kevin Conner updated JBESB-233:
-------------------------------
Assignee: (was: Kurt Stam)
> Message Store access via CBR?
> -----------------------------
>
> Key: JBESB-233
> URL: http://jira.jboss.com/jira/browse/JBESB-233
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Rosetta, Registry and Repository
> Reporter: Mark Little
> Fix For: 5.0
>
>
> Does it make sense to tie the Message Store into the system via CBR, i.e., a CBR dispatcher/handler in each process that routes messages to the store based on specific rules (wildcard support to catch "route all" messages)?
--
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
[ http://jira.jboss.com/jira/browse/JBESB-426?page=all ]
Kevin Conner updated JBESB-426:
-------------------------------
Assignee: (was: Kurt Stam)
> Events interceptor
> ------------------
>
> Key: JBESB-426
> URL: http://jira.jboss.com/jira/browse/JBESB-426
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Rosetta
> Reporter: Mark Little
> Fix For: 5.0
>
>
> Splice in and steal a message from within Struts, Spring & Hibernate silo.
--
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
jUDDI using BRMS as repository
------------------------------
Key: JBESB-1486
URL: http://jira.jboss.com/jira/browse/JBESB-1486
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2.1
Reporter: Mark Little
Assigned To: Kurt Stam
Fix For: 5.0
--
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
Review Programmers Guide
------------------------
Key: JBESB-1716
URL: http://jira.jboss.com/jira/browse/JBESB-1716
Project: JBoss ESB
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.2.1 CP2, 4.2.1 CP1
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
Fix For: 4.3
--
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
wsonsume doesn't like the contract app URLs (http://localhost:8080/contract)
----------------------------------------------------------------------------
Key: JBESB-1719
URL: http://jira.jboss.com/jira/browse/JBESB-1719
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.2.1 CP2
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
The WSDL URL for ESB based webservices are of the form "http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory&...". The wsconsume tool doesn't like them. See the example below. Might be a JBossWS specific issue at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:190).
wsconsume -v -k -o /Jboss/ESB/trunk/product/samples/quickstarts/webservice_producer/build/wsclient http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory&...
parsing WSDL...
[ERROR] Content is not allowed in prolog.
line 12 of http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory
[ERROR] Failed to read the WSDL document: http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory, because 1) could not find the document; /2) the document could not be read; 3) the root element of the document is not <wsdl:definitions>.
unknown location
Failed to parse the WSDL.
Failed to invoke WsImport
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:190)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:216)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:79)
'serviceName' is not recognized as an internal or external command,
operable program or batch file.
'protocol' is not recognized as an internal or external command,
operable program or batch file.
--
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