June 2008 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: @WebServiceRef default name

by emuckenhuber

Hmm yes, as the serviceRefName is used for jndi binding this could lead to a conflict. I mean i think decalaringClass / name makes more sense and would avoid this. And as you mentioned that the spec is unclear on this, we maybe should use the default naming like it was in beta4!? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160115#4160115 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160115

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by alessio.soldano＠jboss.com

"wolfc" wrote : It didn't make ejb3-core 0.1.5, so it's coming in 0.1.6. Yes, I know, I tested it doing a local 0.1.6-SNAPSHOT. Thank you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160026#4160026 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160026

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - @WebServiceRef default name

by alessio.soldano＠jboss.com

This is related to http://jira.jboss.com/jira/browse/JBMETA-64. Well, considering the api doc says the default name should be as is now in trunk, I was thinking it's probably better to close the issue as "won't fix" (thus changing the behavior we had in Beta4). On my side I would have changed the tests, in order not to use the default name (i.e. I'll always use the name attribute) to pass on both containers. My only concern now is that the old naming default was probably used to cope with cases of multiple class having different attribute annotated with @WebServiceRef with the same name: ... public class A { @WebServiceRef private ServiceOne prettyService; ... } ... public class B { @WebServiceRef private ServiceTwo prettyService; ... } What do you think about this Emanuel? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160024#4160024 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160024

17 years, 3 months

1
0
0 / 0

[Fwd: Re: TCK5 status (06/20)]

by Scott Stark

17 years, 3 months

2
3
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by wolfc

It didn't make 0.1.5, so it's coming in 0.1.6. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159931#4159931 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159931

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by alessio.soldano＠jboss.com

"alex.loubyansky(a)jboss.com" wrote : I just committed a fix. Could you please verify in the WS testsuite that all is good? Thanks. I've just tried your fix and the related tests are passing. Thank you again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159877#4159877 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159877

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by alex.loubyansky＠jboss.com

Yes, a new one, since the EJBTHREE-1424 is in the release notes already. I just committed a fix. Could you please verify in the WS testsuite that all is good? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159851#4159851 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159851

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: VirtualFileAdaptor behavior seems incorrect

by scott.stark＠jboss.org

I see you added a test that did not show the problem. I went through the server code to see exactly how the VirtualFile being passed to the ws VirtualFileAdaptor was being created. The issue is that a VirtualFile with a DelegatingHandler pointing to the client jar is asked for itself using getChild(""), and its this VirtualFile that is passed to the VirtualFileAdaptor. It is this file that | public void testVirtualFileAdaptorEarInnerJar() throws Exception | { | URL rootURL = getResource("/vfs/test/interop_W2JREMarshallTest_appclient_vehicle.ear"); | VFS vfs = VFS.getVFS(rootURL); | VirtualFile file = vfs.getChild("interop_W2JREMarshallTest_appclient_vehicle_client.jar"); | assertNotNull(file); | VirtualFile file2 = file.getChild(""); | assertNotNull(file2); | VirtualFileAdaptor adaptor = new VirtualFileAdaptor(file2); | // serialize | adaptor = serializeDeserialize(adaptor, VirtualFileAdaptor.class); | VirtualFileAdaptor child = adaptor.findChild("MarshallTest.xml"); | assertNotNull(child); | } | | java.io.IOException: Child not found interop_W2JREMarshallTest_appclient_vehicle_client.jar for ZipEntryHandler@15675922[path= context=vfszip:/Users/svn/JBossAS/projects/vfs/trunk/target/test-classes/vfs/test/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar real=vfszip:/Users/svn/JBossAS/projects/vfs/trunk/target/test-classes/vfs/test/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar], available children: [ZipEntryHandler@12612903[path=META-INF context=vfszip:/Users/svn/JBossAS/projects/vfs/trunk/target/test-classes/vfs/test/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar real=vfszip:/Users/svn/JBossAS/projects/vfs/trunk/target/test-classes/vfs/test/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar/META-INF], ZipEntryHandler(a)4945063[path=MarshallTest.xml context=vfszip:/Users/svn/JBossAS/projects/vfs/trunk/target/test-classes/vfs/test/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar real=vfszip:/Users/svn/JBossAS/projects/vfs/trunk/target/test-classes/vfs/test/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar/MarshallTest.xml], ZipEntryHandler@14126576[path=com context=vfszip:/Users/svn/JBossAS/projects/vfs/trunk/target/test-classes/vfs/test/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar real=vfszip:/Users/svn/JBossAS/projects/vfs/trunk/target/test-classes/vfs/test/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar/com]] | at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:409) | at org.jboss.test.virtual.support.VirtualFileAdaptor.getFile(VirtualFileAdaptor.java:83) | at org.jboss.test.virtual.support.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:91) | at org.jboss.test.virtual.test.JARSerializationUnitTestCase.testVirtualFileAdaptorEarInnerJar(JARSerializationUnitTestCase.java:264) | See http://jira.jboss.com/jira/browse/JBVFS-36. The current testVirtualFileAdaptorEarInnerJar should have other tests that validate basic navigation assertations as serialization really is not the issue here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159738#4159738 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159738

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by alessio.soldano＠jboss.com

"alex.loubyansky(a)jboss.com" wrote : Yes, that's the one. It's in the release now. I assumed the reference should always have an injection target (field or method). | So, how should it the reference in on the class be handled in this case? I think no injection is supposed to happen for this kind of references; we have the reference bound to jndi but no injection. For instance our testcase simply does the lookup for those references. Btw can I reopen EJBTHREE-1424 or you prefer me to create a new issue? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159736#4159736 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159736

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - VirtualFileAdaptor behavior seems incorrect

by scott.stark＠jboss.org

The current problem with the cts test serialization has to due with the behavior of the VirtualFileAdaptor. A VirtualFileAdaptor is created with a VirtualFile whose underlying handler is a ZipEntryHandler is created that has a path interop_W2JREMarshallTest_appclient_vehicle_client.jar, and a uri of vfszip:/Users/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.CR1/server/cts/tmp/jsr88/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar: ZipEntryHandler(a)2656127[path=interop_W2JREMarshallTest_appclient_vehicle_client.jar context=vfszip:/Users/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.CR1/server/cts/tmp/jsr88/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar real=vfszip:/Users/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.CR1/server/cts/tmp/jsr88/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar] When the VirtualFileAdaptor that wraps the associated VirtualFile, ends up writing out the path and rootURL as interop_W2JREMarshallTest_appclient_vehicle_client.jar and vfszip:/Users/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.CR1/server/cts/tmp/jsr88/interop_W2JREMarshallTest_appclient_vehicle.ear/interop_W2JREMarshallTest_appclient_vehicle_client.jar. | private void writeObject(ObjectOutputStream out) throws IOException, URISyntaxException | { | URL url = rootUrl; | if (url == null) | { | VFS vfs = getFile().getVFS(); | url = vfs.getRoot().toURL(); | } | String pathName = path; | if (pathName == null) | pathName = getFile().getPathName(); | | ObjectOutputStream.PutField fields = out.putFields(); | fields.put("rootUrl", url); | fields.put("path", pathName); | out.writeFields(); | } | This will not work when deserialized with the VirtualFileAdaptor.getFile() implementation. The only way this could work is if the following code used to return the root URL of the ear previously: | VFS vfs = getFile().getVFS(); | url = vfs.getRoot().toURL(); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159656#4159656 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159656

17 years, 3 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 June 2008