"akfs" wrote : I am sending Soap request to SQL Server 2005 Webservices, but I tested it on JBoss, it works fine on the JBoss hosted WS's. Also the jar file jbossesb-soap needs to be replaced in the jbossws.sar
Thanks... just thinking that perhaps we should look at putting hooks in there such that integration issues like this can be worked around without having to pull at the guts of the code in the way you had too. Sorry about that :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111543#4111543
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111543
Configuring the URLSelectorStrategy right now will provide the user to customize the FIALOVER logic.
http://anonsvn.jboss.org/repos/jbossas/trunk/connector/src/main/org/jboss...
While implementing the Datasource load balancing logic in the URLSelectorStrategy I could make that it will not work unless there is the change in the matchManagedConnection(..)/createManagedConnection() .
Right now the createManagedConnection is using the URLSelectorStrategy implementation to find the the appropriate URL to be used in creation of ManagedConnection , for loadbalancing the matchManagedConneciton() too needs modification .
Before I start thinking about about the implementation of loadbalancing at Jboss DS side in detail I wanted to make sure if this would be a good feature to add on .
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111542#4111542
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111542
The reason the JACC tests were failing were due to:
| for(MethodPermissionMetaData perm : perms)
| {
| MethodsMetaData methods = perm.getMethods();
| if(methods != null)
| for(org.jboss.metadata.ejb.spec.MethodMetaData mmd : methods)
| {
| String[] params = {};
| if(mmd.getMethodParams() != null)
| params = mmd.getMethodParams().toArray(params);
| else
| params = null; <= I ADDED THIS NULL
|
Because the an empty array implies method with zero arguments, whereas a null array means all methods.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111521#4111521
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111521
BAM Vs BI, Jasper Vs BIRT. This is all irrelevant for now.
The following has to happen, we need to provide a dynamic reporting engine that can connect to any reporting tool to attract a larger audience. The end-users, business analysts or developers have the opportunity to use their favorite framework.
On another topic, while BAM deals with real-time data and BI with historical data, both of them are provided in the proposed solution. Whatever is real-time now is history in few seconds, so bottom line, the ability to pull out historical data is there.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111516#4111516
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111516
Your example is perfectly valid as well. My point is with the example I gave is that users would like to query about completed process instances. If you say this is not part of a BAM product and our BAM product won't support it, then users will look to other solutions to provide this type of information. So the real question is whether historical data (data about completed process instances) is included in the BAM requirements and will our BAM solution address these requirements?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111505#4111505
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111505