[Design of JBoss Web Services] - Re: JBossWS Deployers Integration
by alessio.soldano＠jboss.com
"richard.opalka(a)jboss.com" wrote : "alessio.soldano(a)jboss.com" wrote :
| | Btw, would it still be possible (if reasonable of course) for a non-ws deployer to be plugged in between two instances of WSDeploymentDeployer without touching anything of the current architecture?
| | Is the case Anil mentioned here before addressed by the current architecture? (just to be sure)
| |
| I bet you mean WSDeploymentAspectDeployer ;)
|
Exactly, sorry for the typo.
anonymous wrote :
| Sure, this was one of the requirements that affected our current AS IL implementation.
| So to answer your question: Yes Anil usecase is supported now
| (although I din't fix it in JBossAS Branch_5_x and trunk yet).
|
Good (I assume your answers are positive for both questions) :-)
Regarding Anil's issue, please see if you can fix that on trunk/branch_5_x by the 3.2.0 ws release date. Thanks!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248401#4248401
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248401
16 years, 5 months
[Design of JBoss Web Services] - Baby steps: test suite problems
by karypid
Hi,
JBossWS development 101:
Step 1: Checkout / compile according to http://jbossws.jboss.org/mediawiki/index.php?title=Building_From_Source.... DONE.
Step 2: Run the test suites according to http://jbossws.jboss.org/mediawiki/index.php?title=Running_The_Test_Suite.... FAILED.
Here is the output:
generate-sources:
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD ERROR
| [INFO] ------------------------------------------------------------------------
| [INFO] An Ant BuildException has occured: The following error occurred while executing this line:
| D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests\scripts\antrun-wstools.xml:44: The following error occurred while executing this line:
| D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests\scripts\antrun-wstools.xml:99: Error running jbossws:
|
| Cannot load wsdl: D\:\\aiq\\jbossws\\work\\jbossws-native\\modules\\testsuite\\native-tests\\target/test-resources/../wstools/resources/jaxrpc/samples/wsbpel/hello/WEB-INF/wsdl/hello-service.wsdl
Here is some more context:
D:\aiq\jbossws\work\jbossws-native>mvn -Psmoketest,jboss510 test
|
| ...
| wsconsume:
| [wsconsume] Consuming wsdl: D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests/src/test/resources/benchmark/jaxws/doclit/WEB-INF/wsdl/BenchmarkWebService.wsdl
| [wsconsume] Consuming wsdl: D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests/src/test/resources/interop/soapwsdl/BaseDataTypesDocLitB/WEB-INF/wsdl/service.wsdl
| [wsconsume] Consuming wsdl: D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests/src/test/resources/interop/soapwsdl/BaseDataTypesDocLitW/WEB-INF/wsdl/service.wsdl
| [wsconsume] Consuming wsdl: D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests/src/test/resources/interop/soapwsdl/BaseDataTypesRpcLit/WEB-INF/wsdl/service.wsdl
| [wsconsume] Consuming wsdl: D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests/src/test/resources/jaxws/samples/wssecuritypolicy/WEB-INF/wsdl/HelloService.wsdl
| [wsconsume] Consuming wsdl: D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests/src/test/resources/jaxws/samples/wssecurityAnnotatedpolicy/META-INF/wsdl/HelloService.wsdl
| [wsconsume] Consuming wsdl: D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests/src/test/resources/jaxws/samples/wssecurity/META-INF/wsdl/HelloService.wsdl
| [INFO] Executed tasks
| [INFO] [build-helper:add-test-source {execution: add-source}]
| [INFO] Test Source directory: D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests\target\wsconsume\java added.
| [INFO] [resources:resources {execution: default-resources}]
| [WARNING] Using platform encoding (Cp1253 actually) to copy filtered resources, i.e. build is platform dependent!
| [INFO] skip non existing resourceDirectory D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests\src\main\resources
| [INFO] [compiler:compile {execution: default-compile}]
| [INFO] No sources to compile
| [INFO] [resources:testResources {execution: default-testResources}]
| [WARNING] File encoding has not been set, using platform encoding Cp1253, i.e. build is platform dependent!
| [WARNING] Using platform encoding (Cp1253 actually) to copy filtered resources, i.e. build is platform dependent!
| [INFO] Copying 3 resources
| [INFO] Copying 7 resources to ../test-classes
| [INFO] Copying 1725 resources to ../test-resources
| [INFO] Copying 582 resources to ../test-resources
| [INFO] [compiler:testCompile {execution: default-testCompile}]
| [INFO] Compiling 90 source files to D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests\target\test-classes
| [INFO] [antrun:run {execution: wstools}]
| [INFO] Executing tasks
|
| generate-sources:
| [INFO] ------------------------------------------------------------------------
| [ERROR] BUILD ERROR
| [INFO] ------------------------------------------------------------------------
| [INFO] An Ant BuildException has occured: The following error occurred while executing this line:
| D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests\scripts\antrun-wstools.xml:44: The following error occurred while executing this line:
| D:\aiq\jbossws\work\jbossws-native\modules\testsuite\native-tests\scripts\antrun-wstools.xml:99: Error running jbossws:
|
|
| Cannot load wsdl: D\:\\aiq\\jbossws\\work\\jbossws-native\\modules\\testsuite\\native-tests\\target/test-resources/../wstools/resources/jaxrpc/samples/wsbpel/hello/WEB-INF/wsdl/hello-service.wsdl
| [INFO] ------------------------------------------------------------------------
| [INFO] For more information, run Maven with the -e switch
| [INFO] ------------------------------------------------------------------------
| [INFO] Total time: 42 seconds
| [INFO] Finished at: Thu Aug 06 12:38:46 EEST 2009
| [INFO] Final Memory: 52M/94M
| [INFO] ------------------------------------------------------------------------
Can somebody help? I am using:
- Sun JDK 1.6.0_14
- Ant 1.7.0
- Maven 2.2.0
- JBoss AS 5.1.0.GA (not head of development trunk, the release tag)
- JBossWS-Native 3.2.0 (head of development trunk).
Here is verification that the stack was installed successfully in the server I built:
12:20:50,599 INFO [ServerImpl] Starting JBoss (Microcontainer)...
| 12:20:50,599 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200908042216)
| ...
| 12:20:56,066 INFO [ServerInfo] Java version: 1.6.0_14,Sun Microsystems Inc.
| 12:20:56,066 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
| 12:20:56,066 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.0-b16,Sun Microsystems Inc.
| 12:20:56,066 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
| ...
| 12:21:22,588 INFO [AbstractServerConfig] JBoss Web Services - Native Server
| 12:21:22,588 INFO [AbstractServerConfig] 3.2.0-SNAPSHOT
| 12:21:24,368 INFO [AttributeCallbackItem] Owner callback not implemented.
| ...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248398#4248398
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248398
16 years, 5 months
[Design of JBoss Web Services] - Re: JBossWS Deployers Integration
by alessio.soldano＠jboss.com
"richard.opalka(a)jboss.com" wrote : "alessio.soldano(a)jboss.com" wrote :
| | Basically, we had a abstraction to support AS4.2 deployment in a similar way to AS 5.x, now most of that additional abstraction is gone, why DA are still there? Can't we simply move each of them in a different deployer? (considering the WSDeploymentDeployer seems to me just something like a wrapper of the DAs)
| |
| Yes, DA abstraction is still there and will probably stay there ;)
| There are two main reasons why we're wrapping JBossWS DAs:
|
| we can't replace DAs with Deployers, otherwise our stacks would be tightly coupled with AS internals. To separate all supported SOAP stacks from different AS versions we have AS IL (JBoss AS Integration Layer) that does that abstraction job.
OK... there's actually not much of that abstraction left, anyway I see your point of view of keeping the DA concept for generic deployment (see point below).
Btw, would it still be possible (if reasonable of course) for a non-ws deployer to be plugged in between two instances of WSDeploymentDeployer without touching anything of the current architecture?
Is the case Anil mentioned here before addressed by the current architecture? (just to be sure)
anonymous wrote :
| we will need to implement Endpoint.publish() in near future (this will use DAs via DAManager - DAManager will be used as the replacement of deployers chain on Java client side)
|
|
OK, I agree on this.
anonymous wrote :
| IMHO the JBDEPLOY-201 title is self descriptive. Regarding that issue Ales Justin just wrote me:
|
| Currently there is no rush for it.
| Hence I don't see the point of cutting new release,
| as I have already done them too many.
| I rather wait and get any additional fixes in (e.g. recent 208, 209).
|
| I'll at least try to port the changes to Branch_2_0 asap,
| so you can easily run a 2.0.9-SNAPSHOT version to test your stuff.
|
|
| I just asked him to port the changes to JBDeploy Branch_2_0 branch so we can test the fix using 2.0.9-SNAPSHOT
Thanks for the update.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248390#4248390
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248390
16 years, 5 months