i just noticed that grizzly-http-server-jaxws 2.2.5 was released also
(and the snapshot was removed from the server).
tested and works also.
On Sat, Apr 14, 2012 at 9:03 PM, Gonfi den Tschal
<gonfidentschal_at_gmail.com> wrote:
> it works with grizzly-http-server 2.2.5 and the 2.2.5 snapshot of
> grizzly-http-server-jaxws.
> jdk and grizzly now work the same. thanks!
>
>
>
> On Wed, Apr 11, 2012 at 8:47 PM, Gonfi den Tschal
> <gonfidentschal_at_gmail.com> wrote:
>> behavior is different, but doesn't work for me.
>>
>> here is what i did:
>>
>> i changed the version in the dependency from 2.2.4 to the snapshot
>>
>> <dependency>
>> <groupId>org.glassfish.grizzly</groupId>
>> <artifactId>grizzly-http-server-jaxws</artifactId>
>> <version>2.2.5-20120411.070627-1</version>
>> </dependency>
>>
>> and added the maven snapshot server
>>
>> <repositories>
>> <repository>
>> <id>snapshot-repository.java.net</id>
>> <name>Java.net Snapshot Repository for Maven</name>
>> <url>https://maven.java.net/content/repositories/snapshots/</url>
>> <layout>default</layout>
>> <snapshots><enabled>true</enabled></snapshots>
>> </repository>
>> </repositories>
>>
>> after also adding the dependency
>>
>> <dependency>
>> <groupId>org.glassfish.grizzly</groupId>
>> <artifactId>grizzly-http-server</artifactId>
>> <version>2.2.4</version>
>> </dependency>
>>
>> the code compiles again.
>>
>> i published several web services, one of them is /soap/v1/foo (they
>> all start with /soap/v1)
>>
>> now i test several urls in the browser. here is the output:
>>
>> /soap
>> Web Services
>> No JAX-WS context information available.
>>
>> /soap?wsdl
>> Not Found
>> Resource identified by path '/soap', does not exist.
>> Grizzly/2.2.4
>>
>> /soap?blahblah
>> Web Services
>> No JAX-WS context information available.
>>
>> /soap/v1/foo
>> Web Services
>> No JAX-WS context information available.
>>
>> /soap/v1/foo?wsdl
>> Not Found
>> Resource identified by path '/soap/v1/foo', does not exist.
>> Grizzly/2.2.4
>>
>> /soap/v1/foo?blahblah
>> Web Services
>> No JAX-WS context information available.
>>
>> /soap/blahblah (no such service published)
>> Web Services
>> No JAX-WS context information available.
>>
>> /blahblah (no such service published)
>> Not Found
>> Resource identified by path '/blahblah', does not exist.
>> Grizzly/2.2.4
>>
>> am i doing something wrong? isn't there any example anywhere that uses
>> more than just the path "/add"?
>>
>>
>>
>>
>> On Wed, Apr 11, 2012 at 5:01 PM, Oleksiy Stashok
>> <oleksiy.stashok_at_oracle.com> wrote:
>>> pls. try Grizzly 2.2.5-SNAPSHOT from the maven repository
>>> https://maven.java.net/content/repositories/snapshots/
>>>
>>> and let us know if it works for you.
>>>
>>> Thanks.
>>>
>>>
>>> WBR,
>>> Alexey.
>>>
>>> On 04/11/2012 03:01 AM, gonfidentschal_at_gmail.com wrote:
>>>>
>>>> (cross-post from
>>>> http://stackoverflow.com/questions/10098530/grizzly-jaxws-schemalocatio
>>>> n )
>>>>
>>>> i'm publishing a soap ws api from within my java app.
>>>> so far i've used the jdk built-in http server, like so:
>>>>
>>>> Endpoint.publish("http://www.example.com:80/soap/v1/foo",
>>>> myWebService);
>>>>
>>>> and all worked fine.
>>>>
>>>> now switching to grizzly. my code is based on the official example from
>>>> http://grizzly.java.net/nonav/docs/docbkx2.0/html/jaxws-samples.html
>>>>
>>>> thus something like
>>>> httpServer.getServerConfiguration().addHttpHandler(httpHandler,
>>>> "/soap/v1/foo");
>>>>
>>>> the wsdl is available for both under the expected url
>>>> http://www.example.com:80/soap/v1/foo?wsdl but with grizzly the
>>>> generated wsdl looks different. the schmemaLocation is shortened in all
>>>> places in that the "/v1/foo" part is removed, it only points to /soap.
>>>> this is the case for all services that i publish (multiple). and the
>>>> result is that the methods can't be called.
>>>
>>>