October 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Problems getting WS into ESB

by thomas.diesler＠jboss.com

anonymous wrote : | I still don't know whether the SP2 release includes this fix or not, you owe me an answer on that one ;) | Yes it does. When you say anonymous wrote : | ESB is currently based on AS4.2.1 | do you mean #1 there is a fork AS4.2.1 that we maintain in SVN http://path_to_some_branch #2 we use the AS4.2.1 binary relase In both cases installing jbossws-2.0.1.SP2 is not trivial because the AS container integration has moved to Branch_4_2 after the AS4.2.1 release. Please show me exactly how you attempted to install jbossws-2.0.1.SP2 from that I can probably see how it should be done properly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099042#4099042 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099042

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Problems getting WS into ESB

by Kevin.Conner＠jboss.com

I believe the EAP is also based on 4.2.1 at this point in time but Trevor may be able to comment further on this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098961#4098961 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098961

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Problems getting WS into ESB

by Kevin.Conner＠jboss.com

ESB is currently based on AS4.2.1 and will be for our 4.2.1 release (in less than one weeks time). A subsequent release will support AS 4.2.2. We are currently using WS2.0.0 in the ESB as 2.0.1 was not backwardly compatible with our code. I believe this may have been fixed in a recent CP release but we cannot use those in the project. I still don't know whether the SP2 release includes this fix or not, you owe me an answer on that one ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098960#4098960 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098960

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Problems getting WS into ESB

by thomas.diesler＠jboss.com

For jbossws-2.0.1.SP2, which was targeted jor jboss-4.2.2 the container integration lives in the AS code base. We probably first need to understand how the ESB is related to the AS. i.e. does it use an AS release or is it a fork of the AS code base? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098853#4098853 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098853

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Problems getting WS into ESB

by thomas.diesler＠jboss.com

Trevor sais anonymous wrote : | When trying to integrate the WS CP into the ESB I hit problems with | jbossws-jboss42.jar not having the required classes. Since WS SP2 this | jar is no longer shipped as part of WS see | http://jira.jboss.org/jira/browse/JBWS-1851. We need some method of | getting this jar into the ESB. | | Comments please. | | Trev | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098849#4098849 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098849

17 years, 2 months

1
0
0 / 0

Re: ws classloader problem

by Thomas Diesler

The container integration jbossws-jboss42.jar is missing. Please tell me exactly what you did so I can reproduce this. cheers -thomas On Wed, 2007-10-24 at 17:48 +0100, trevor kirby wrote: > *getting loads of errors in the esb version along the following lines, > ws was added using your deploy target. Any suggestions? > > Trev > > java.lang.ClassNotFoundException: No ClassLoaders found for: > org.jboss.wsf.container.jboss42.ContainerMetaDataDeploymentAspect > java.lang.ClassNotFoundException: No ClassLoaders found for: > org.jboss.wsf.container.jboss42.DefaultWebAppDesciptorModifierImpl > java.lang.ClassNotFoundException: No ClassLoaders found for: > org.jboss.wsf.container.jboss42.DeploymentAspectHttpServer > java.lang.ClassNotFoundException: No ClassLoaders found for: > org.jboss.wsf.container.jboss42.EJBArchiveMetaDataAdapterEJB21 > java.lang.ClassNotFoundException: No ClassLoaders found for: > org.jboss.wsf.container.jboss42.EJBArchiveMetaDataAdapterEJB3 > java.lang.ClassNotFoundException: No ClassLoaders found for: > org.jboss.wsf.container.jboss42.JAXRPCDeployerHookPostJSE > > * -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBoss equivalent of clientGen of WL

by alessio.soldano＠jboss.com

Please do no post user question in the Design forum; use the user forum instead (as you actually did after posting here ;-)) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098675#4098675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098675

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - JBoss equivalent of clientGen of WL

by JBoss_82

Hi, I am using the top-down approach by starting with the WSDL. I am trying to figure out a mechanism in JBoss 4.2.2 with jbossws-native2.0.1 which is equivalent of WL's clientgen. Objective is to generate a client-jar which can be used by the client program to consume the web service. Sample WL clietgen task: | <taskdef name="clientgen" classname="weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask" | classpathref="clientgen.class.path"/> | | <target name="McAfee"> | <clientgen wsdl="macafeeAdapterContract.wsdl" | packageName="com.covad.vendororder" | typePackageName="com.covad.vendororder.xsd" | clientJar=".\mcafeeadapter-client.jar"> | <classpath refid="clientgen.class.path" /> | </clientgen> | </target> | anonymous wrote : I know there is a crude way of using the client artifacts generated by "wsconsume", zip those class files and create a client-jar, but I want to know if there's a better way to do this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098618#4098618 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098618

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBAS-4890:EJBAccessException: Caller unauthorized

by anil.saldhana＠jboss.com

"scott.stark(a)jboss.org" wrote : That was what my TODO question was about. Yeah, we still push a null runas (as per my latest change). Wonder why u pushed an "anonymous", rather than a null? RunAs takes preference in authorization and programmatic security (isUserxxx. isCallerXXX, getCallerP). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098550#4098550 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098550

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBAS-4890:EJBAccessException: Caller unauthorized

by scott.stark＠jboss.org

That was what my TODO question was about. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098540#4098540 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098540

17 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev October 2007