October 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by thomas.diesler＠jboss.com

Please link to the jira issue that pertains to this post if there is one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978775#3978775 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978775

19 years, 5 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Metadata rewrite

by kabir.khan＠jboss.com

I don't think anything has been done on this yet? A few of my AOP-MC tasks depends on this. If you want I can take a look, but a few pointers would be appreciated :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978766#3978766 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978766

19 years, 5 months

1
0
0 / 0

[Design of JBoss Collaboration Server] - Re: Current status of Project

by herthie57

Looking in the repository (http://fisheye.jboss.org/browse/JBoss/jboss-mail) it seems that there is no more development activity since end of July. Is this project dead? Is there a chance this promising project bring back? Do we have a chance to see the 1.0 final one day? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978760#3978760 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978760

19 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by maeste

I'm sorry, but I didn't understand. What you link on jira is a patch I already submitted, but this message is about another issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978755#3978755 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978755

19 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: General message receive functionality

by mark.little＠jboss.com

This certainly sounds interesting. It has some cross-over with transformation services and content based routing. It would be interesting to discuss this further, but our roadmap for our first GA release is quite tight, so you would probably have to put up with some periods of silence from us during the conversations. Best place for them would be in this forum though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978749#3978749 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978749

19 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - General message receive functionality

by derry

Hello! I am working for a company that does integration (besides other stuff) between buyers (>100) and suppliers (>800) for orders, change orders, order responses, invoices, ... What I have learned is that many smaller companies have problems programming to a specific interface (SOAP, simple HTTP request, ...) because their IT department is there to run their daily business. They have no staff that is dedicated to integration things. So far we have not found any commercial product that serves our needs. So we have a lot of automation in our products to come over this weaknesses. What we do is the following: * Try to find the envelope type of the message (SOAP, MML, MIME,...). This is based on regular expressions and XPATH queries. Then we disassemble the message based on this information. * Try to find what format the business documents have (xCBL, EDIfact, ebXML, ...). Again we use regular expressions and XPATH queries for that. * Try to find out what type of transaction (order, invoice, ...) this documents describe. * Convert the documents to a canonical format for further processing. But we always have the original format attached to the document for reference. * Look into the master-data registry (see below) if the communication partner is allowed to send a business document to the destination that is written inside the business document (we have many companies that send business documents on behalf of another company). * Push the documents to the right processing queue for the given type of transaction. To support the further processing we have a master-data registry that has all needed information about communication partners (for example their preferred outbound format) Is this something that is only needed by our company only or is this of general interest? If there is general interest I would love to design such a service with you together on top of JBossESB. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978748#3978748 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978748

19 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1133 - Exploded JSR-181 POJO Deployment Fails Redep

by darran.lofthouse＠jboss.com

Yes the main problem is that at the time of deployment we do not have access to the parameters passed to the servlet, we need the parameters as it is one of those that contains the class name of the endpoint. Option 1 was an option so that JBossAS could pass JBossWS all of the configured parameters within the 'org.jboss.metadata.WebMetaData' so we can easily access it. Option 3 is that we read the web.xml ourselves to extract the parameters. Option 2 was just an alternative we could follow if we wanted to leave the original web.xml alone so for each deployment we would start with a clean web.xml so JBossWS wouldn't need to be coded to cope with first and second deployments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978741#3978741 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978741

19 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1133 - Exploded JSR-181 POJO Deployment Fails Redep

by thomas.diesler＠jboss.com

Ok, sorry I missed the point. In that case, since we already can detect that a web.xml is modified we know the endpoint bean class. This bean should then be passed through the same logic that detected the JSR181 endpoint on first time deployment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978737#3978737 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978737

19 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1093 - normal servlets the web.xml is modified as i

by darran.lofthouse＠jboss.com

Its Ok I already fixed that last night (JBWS-1305), I haven't run the testsuite against it yet but I have deployed a web service and can access it's WSDL without error now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978734#3978734 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978734

19 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1133 - Exploded JSR-181 POJO Deployment Fails Redep

by darran.lofthouse＠jboss.com

It is the fact that we don't modify the web.xml again that is the problem for the JSR-181 deployments. For JSR-109 deployments we do not have a problem because we have a webservices.xml that lists which servlets are actually endpoints. However for JSR-181 deployments to identify which servlets are actually endpoints we check all of the servlets to see if they are annotated with @WebService, as the JBossWS servlet is not annotated with @WebService the deployment of the JSR-181 endpoint is skipped for all subsequent deployments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978733#3978733 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978733

19 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2006