Nabble - Metro

Re: jax-ws deployment

2009-12-03T15:59:49Z

I don't know but I have found that it relies on that file to determine the endpoint URL of the web service:

http://www.jroller.com/gmazza/entry/creating_a_wsdl_first_web1#WFstep7
http://www.jroller.com/gmazza/entry/creating_a_wsdl_first_web1#notes (Note #2)

Glen

metro-3 wrote:

Hi,

Is sun-jaxws.xml a mandatory if I want to deploy jax-ws webservices onto tomcat 6. Using java 6 .

thanks in advance.
[Message sent by forum member 'sks1' ]

From forum: Metro - Users

Re: Simple STS Problem

2009-12-03T15:38:05Z

Get the latest GF v3 and try:

jhttp://download.java.net/glassfish/v3/promoted/
[Message sent by forum member 'jdg6688' ]

http://forums.java.net/jive/thread.jspa?messageID=374644

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Simple STS Problem

2009-12-03T13:54:30Z

hi jdg6688,

I changed my project to NetBeans 6.8 with metro 2.0, and when I deploy the STS to Glassfish, I got some new errors.

SEVERE: com.sun.enterprise.deployment.annotation.context.WebBundleContext cannot be cast to com.sun.enterprise.deployment.annotation.context.EjbContext
SEVERE: Exception while deploying the app
java.lang.IllegalStateException: com.sun.enterprise.deployment.annotation.context.WebBundleContext cannot be cast to com.sun.enterprise.deployment.annotation.context.EjbContextat org.glassfish.apf.AnnotationInfo@d6a3d1
at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:478)
at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:420)
at com.sun.enterprise.deployment.archivist.Archivist.readRestDeploymentDescriptors(Archivist.java:396)
at com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Archivist.java:373)
at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:238)
at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:247)
at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:208)
at com.sun.enterprise.deployment.archivist.ApplicationFactory.openArchive(ApplicationFactory.java:148)
at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:155)
at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:78)
at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:612)
at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:554)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:262)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365)
at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:204)
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166)
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.enterprise.deployment.annotation.context.WebBundleContext cannot be cast to com.sun.enterprise.deployment.annotation.context.EjbContextat org.glassfish.apf.AnnotationInfo@d6a3d1
at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:360)
at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:368)
at org.glassfish.apf.impl.AnnotationProcessorImpl.processAnnotations(AnnotationProcessorImpl.java:282)
at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:188)
at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:129)
at com.sun.enterprise.deployment.archivist.Archivist.processAnnotations(Archivist.java:581)
at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:433)
... 39 more
Caused by: java.lang.ClassCastException: com.sun.enterprise.deployment.annotation.context.WebBundleContext cannot be cast to com.sun.enterprise.deployment.annotation.context.EjbContext
at org.glassfish.webservices.annotation.handlers.WebServiceProviderHandler.processAnnotation(WebServiceProviderHandler.java:137)
at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:337)
... 45 more
[Message sent by forum member 'liaw' ]

http://forums.java.net/jive/thread.jspa?messageID=374635

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: how to skip a method in JAX-WS?

2009-12-03T13:21:11Z

I don't normally take the Java-first approach, but since there haven't been any other responses I'll toss this out there. Try annotating the methods you want to skip with:

@WebMethod(exclude=true)
[Message sent by forum member 'kschneid' ]

http://forums.java.net/jive/thread.jspa?messageID=374630

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: WS Eventing with WS Addressing wsa:Action problemheaderqname

2009-12-03T12:57:44Z

Thank you for posting this! I'm trying to implement a web service that receives these subscription requests. Can you please post some sample code on your service? I noticed your subscribe operation expects Subscribe and returns SubscribeResponse object...what API is that from?
[Message sent by forum member 'htriggs' ]

http://forums.java.net/jive/thread.jspa?messageID=374629

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Thread safety of web service objects/proxies/ports

2009-12-03T11:44:29Z

Hi!

I googled and found this:
http://forums.java.net/jive/thread.jspa?messageID=328373

quote: "We need to know whether the service objects generated by
wsimport (JAX-WS RI 2.0.1 and later versions), as well as the port
objects returned by the getPort() methods of those service objects are
thread-safe."

So is there a definitive answer?

I am doing a cleanup in our project and want to know:
- can I reuse the same proxy object returned by a single getPort()
call in multiple threads?
or
- can I at least call the getPortName() method javax.xml.ws.Service
child from mulriple threads?

We use tomcat 6.0.20 and jaxws-api-2.1.jar jaxws-rt-2.1.4.jar
jaxws-tools-2.1.5.jar

Regards,
David

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

how to skip a method in JAX-WS?

2009-12-03T11:36:26Z

Hi there,

I have a class annotated with @WebService

but I have one method in this class to not be exposed in the generated WSDL ?

some methods I annotated as @WebMethod, others not... so I want these
non-annotated methods to not be included in the wsdl..............

------------------------------------------
Felipe Gaúcho
10+ Java Programmer
CEJUG Senior Advisor

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Metro 1.5 + STS issued token with SAML2.0 attribute statements

2009-12-03T10:58:22Z

> Hi
>
> I've implemented my own STSAttributeProvider to write
> SAML2 assertions in my STS issued tokens. However, I
> have some questions on how to customise the attribute
> statements:
> 1) is there a way to set the Attribute's FriendlyName
> (which is an optional attribute of the element)?
> 2) And is it possible to replace the token's
> autogenerated saml2:Assertion ID with my own custom
> value?

No with by default. The only way is you have a custom STSTokenProvider.
[Message sent by forum member 'jdg6688' ]

http://forums.java.net/jive/thread.jspa?messageID=374609

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Metro 1.5 + STS issued token with SAML2.0 attribute statements

2009-12-03T10:57:03Z

This was a bug in 1.5. It is fixed with Metro 2.0.
[Message sent by forum member 'jdg6688' ]

http://forums.java.net/jive/thread.jspa?messageID=374608

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

jax-ws deployment

2009-12-03T10:53:42Z

Hi,

Is sun-jaxws.xml a mandatory if I want to deploy jax-ws webservices onto tomcat 6. Using java 6 .

thanks in advance.
[Message sent by forum member 'sks1' ]

http://forums.java.net/jive/thread.jspa?messageID=374607

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: WSDL Query

2009-12-03T09:03:50Z

--
Jeff

On Dec 3, 2009, at 10:47 AM, Martin Grebac wrote:

> Jeffrey Haynes wrote:
>> On Dec 2, 2009, at 11:31 AM, Fabian Ritzmann wrote:
>>
>>
>>> On 2.12.2009 19:24, Harold Carr wrote:
>>>
>>>>> Does that give you what you are asking for?
>>>>> Perhaps"attribute" was the wrong term in the Metro universe.
>>>>> Essentially, these additions allow more information to be sent to the
>>>>> web service.
>>>>>
>>>> Ah, the schema has additional elements added. Our JAXB expert should
>>>> give the definitive answer, but the old clients should continue to work
>>>> - the new info will be ignored.
>>>>
>>>> Try it out and let us know the results.
>>>>
>>> This article gives a decent introduction to versioning web services [1]:
>>> http://www.ibm.com/developerworks/webservices/library/ws-version/
>>>
>>
>> OK. In my case, there are not any namespace differences, only new elements. So it sounds like the only way to be able to use the new elements in a wsdl is to generate a new Java binding. Is that correct?
>>
>> Big picture; If possible, I want to remove the requirement to generate a new java binding when new schema elements are added to the wsdl.
>>
>> 1: Is there a way to use the Java binding for the latest wsdl, but somehow check for the existence of the element at runtime? (before actually attempting to set value for the element?
>>
>> 2: Is there a way that a java binding generated from an older version of a wsdl can interrogate the new wsdl and set values for the new elements?
>>
> Hi,
> from JAXB side I don't see a way how this can be done without any change of the binding, or without providing extensive customization on the binding by either using DOM approach which would change the way of accessing all the attributes, or providing xmljavatypeadapter.
> MartiNG

Thanks for the information.

Can you provide me a pointer to the xmljavatypeadapter information?

I had another idea as well. Is there a way to query the elements that are available to be set? For example, is there a way to query the web service for the elements that can be set as arguments to that service?

Otherwise, I guess I could use reflection on the argument object to figure out what arguments are available.

Jeff

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: WSDL Query

2009-12-03T08:47:48Z

Jeffrey Haynes wrote:

> On Dec 2, 2009, at 11:31 AM, Fabian Ritzmann wrote:
>
>
>> On 2.12.2009 19:24, Harold Carr wrote:
>>
>>>> Does that give you what you are asking for?
>>>> Perhaps"attribute" was the wrong term in the Metro universe.
>>>> Essentially, these additions allow more information to be sent to the
>>>> web service.
>>>>
>>> Ah, the schema has additional elements added. Our JAXB expert should
>>> give the definitive answer, but the old clients should continue to work
>>> - the new info will be ignored.
>>>
>>> Try it out and let us know the results.
>>>
>> This article gives a decent introduction to versioning web services [1]:
>> http://www.ibm.com/developerworks/webservices/library/ws-version/
>>
>
> OK. In my case, there are not any namespace differences, only new elements. So it sounds like the only way to be able to use the new elements in a wsdl is to generate a new Java binding. Is that correct?
>
> Big picture; If possible, I want to remove the requirement to generate a new java binding when new schema elements are added to the wsdl.
>
> 1: Is there a way to use the Java binding for the latest wsdl, but somehow check for the existence of the element at runtime? (before actually attempting to set value for the element?
>
> 2: Is there a way that a java binding generated from an older version of a wsdl can interrogate the new wsdl and set values for the new elements?
>

Hi,
from JAXB side I don't see a way how this can be done without any
change of the binding, or without providing extensive customization on
the binding by either using DOM approach which would change the way of
accessing all the attributes, or providing xmljavatypeadapter.
MartiNG

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Metro 1.5 + STS issued token with SAML2.0 attribute statements

2009-12-03T06:29:03Z

Hi I need to qualify the question on setting the Attribute's Name (not FriendlyName):

I followed the example given in(http://docs.oasis-open.org/security/saml/v2.0/saml-schema-assertion-2.0.xsd). See code fragement:
-----
Map<QName, List<String>> attrs = new HashMap<QName, List<String>>();

QName testQName = new QName("http://my.com","location_country");
List<String> defaultAttrs = new ArrayList<String>(); //List of attributeValues
defaultAttrs.add("USA");
defaultAttrs.add("North Korea");

attrs.put(testQName, defaultAttrs);
---
and I get this in the token:
--
<saml2:Attribute AttributeName="location_country" AttributeNamespace="http:my.com" Name="">
<saml2:AttributeValue>USA</saml2:AttributeValue>
<saml2:AttributeValue>North Korea</saml2:AttributeValue>
</saml2:Attribute>
--

As you can see from the SAML attribute statement, the Name attribute is blank. This is a required attribute according to the SAML xsd.

Thanks

S
[Message sent by forum member 'syc17' ]

http://forums.java.net/jive/thread.jspa?messageID=374537

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

The name value of @XmlElementRef is ignored

2009-12-03T05:08:49Z

Hi
I have some problem with @XmlElementRef declaration: it seems that 'name' value: 
For example, for declaration: 
[i] @XmlElementRefs({ 
 @XmlElementRef(name = "my_t1", namespace = "", type = T1.class), 
 @XmlElementRef(name = "my_t2", namespace = "", type = T2.class ) 
}) 
protected Tbase myT; 
 [/i]
schemagen generates: 
 
[i] <xs:choice> 
 <xs:element ref="t1"/> 
 <xs:element ref="t2"/> 
 </xs:choice> [/i]
 
i.e., element names created basing its types and not provided names. 
Anybody has faced it? 
 
Greatly appreciating any inputs 
J.
[Message sent by forum member 'jabberw' ]

http://forums.java.net/jive/thread.jspa?messageID=374528

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Metro 1.5 + STS issued token with SAML2.0 attribute statements

2009-12-03T05:05:43Z

Hi

I've implemented my own STSAttributeProvider to write SAML2 assertions in my STS issued tokens. However, I have some questions on how to customise the attribute statements:
1) is there a way to set the Attribute's FriendlyName (which is an optional attribute of the element)?
2) And is it possible to replace the token's autogenerated saml2:Assertion ID with my own custom value?

Thanks in advance

S
[Message sent by forum member 'syc17' ]

http://forums.java.net/jive/thread.jspa?messageID=374527

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

How do I handle a empty abstract class generated from wsdl

2009-12-03T01:47:43Z

In my wsdl I have this
<xs:complexType name="AbstractGetRequestAttributeType" abstract="true" />
<xs:element name="GetRequestMODefinition" type="AbstractGetRequestAttributeType" abstract="true" />
<xs:element name="MOAttributes" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element ref="GetRequestMODefinition" />
</xs:sequence>
</xs:complexType>
</xs:element>

After wsimport I get this class:
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "AbstractGetRequestAttributeType")
public abstract class AbstractGetRequestAttributeType {
}

I want to generate SOAP like this. How Do I do it with the empty abstract class above?
<Param name="MOAttributes"><![CDATA[
<getDNSSubscription msisdn="tel:+46841076018" xmlns="http://schemas.ericsson.com/ema/UserProvisioning/IPWorks/5.0/">
<subscriberId>AA3@...</subscriberId>
</getDNSSubscription> ]]></Param>
[Message sent by forum member 'astast69' ]

http://forums.java.net/jive/thread.jspa?messageID=374475

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Using UsernameToken wth SymmetricBinding?

2009-12-02T21:57:17Z

it is working fine in my case.. please try with latest metro builds.

the namespace
[i]http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Always[/i]
is working fine my my case.
and
i dont see any exception when i use SignedSupportingTokens policy assertion for the UsernameToken

try the sample atached and let me know ..
Thanks
Suresh
[Message sent by forum member 'sm228678' ]

http://forums.java.net/jive/thread.jspa?messageID=374439

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Using UsernameToken wth SymmetricBinding?

2009-12-02T21:24:53Z

are you using metro 2.0 version or older?
Thanks
Suresh

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Policy configuration that could be used on client and server sides?

2009-12-02T21:23:58Z

Hi!

It seems that, to use things like authentication/signatures, one has to provide configuration information that might be different on client vs. server sides. As an example, I wanted to set up a CallbackHandlerConfiguration on the WSDL that the client will use, but a ValidatorHandler configuration on the server side, instead. I thought I could just put both of these policy assertions within the same policy, with ExactlyOne, so that the server would pick one "branch", while the client would use the other. I will attach an example of what I mean to this note.

But it seems that, when the server reads this policy, it throws an exception (assertion not supported) when it reads the client configuration policy assertion, and then gives up.
Shouldn't it just ignore that policy assertion, rather than aborting - at least when it is inside of am ExactlyOne that has other choices?

This way, I would not need to write two WSDL files (one for client, one for server) with the two policy assertions one each...

Or - is there another way to do this?

Thank you!
[Message sent by forum member 'mlejter' ]

http://forums.java.net/jive/thread.jspa?messageID=374436

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Order in which objects in a collection will be Marshalled?

2009-12-02T17:37:05Z

Good Folk,

I read in the 2.1 JAXB Spec
Appendix B
3 "Unmarshalling"
3.4 "Element Information Item" the following text:

If EII.property is collection type:

a. add EII.boundtype to the end of the collection.

NOTE: Adding JAXBElement instance or a type to the end of the
collection preserves document order. And document order could be
different from the order in XML Scheme if the instance contains invalid
XML content.

This is (if I understand correctly) assuring us that the order XML elements are encountered is the order in which corresponding objects will appear in the appropriate collection property after unmarshalling.

Suppose I wanted to be assured the other side of this issue:

The order in which objects appear in a collection property is the order they will be written as the appropriate XML element at marshalling time.

Where would I find this assurance in the spec? It seemed natural to look in section B.5 "Marshalling" for this kind of assurance, but if the assurance is there, I'm not comprehending it. B.5 does not seem to speak to collection properties at all.

If the spec doesn't actually assure this, is there anything that can be said about order of Marshalling? I do not think this is about the propOrder property of the @XmlType annotation, that orders *properties*: I am looking for any information on the order of the objects in a collection property.

Any ideas on this? Is this so obvious I've missed it?

cheers,
Nigel
[Message sent by forum member 'nigel_kerr0' ]

http://forums.java.net/jive/thread.jspa?messageID=374405

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Using different SSL Listeners on the same domain

2009-12-02T14:56:14Z

try:

http://forums.java.net/jive/forum.jspa?forumID=56
[Message sent by forum member 'jdg6688' ]

http://forums.java.net/jive/thread.jspa?messageID=374393

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Metro + OpenSSO STS

2009-12-02T14:54:48Z

Yes, it is the right approach.

Seems that the versions of trust don't match.

1. Check the versions of ws-securitypolicy and ws-trust used for STS and service.
"http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
or
"http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702"

2. In the client configuration, you set:
wstVersion="http://schemas.xmlsoap.org/ws/2005/02/trust"
which matches "http://schemas.xmlsoap.org/ws/2005/07/securitypolicy".

But I guess you use "http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702"
for sts. That where the problem comes.

3. Check the log on the STS side.

Thanks!

Jiandong
[Message sent by forum member 'jdg6688' ]

http://forums.java.net/jive/thread.jspa?messageID=374392

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

complexType creation [newbie]

2009-12-02T14:26:07Z

Hi,
this is my first post here, so please be lenient.

I need to parse, modify and rewrite an xml file.
I have no control over its format since it s produced by another application and the modified thing needs to be compatible with it.

The original file has no xsd/DTD, so I wrote a .xsd for it.
I attach the whole .xsd for reference.

I managed to make it work, but I fear I'm simply not using JAXB in the "RightWay".

When i scan the list of "Scenes" i need the following code, otherwise I get string elements (blanks) intermixed with the "good" nodes:

CHAPTER ch = (CHAPTER) pe;
SceneList scs = ch.getScenes();
for (Serializable e : scs.getContent()) {
if (e instanceof JAXBElement<?>) {
JAXBElement<?> xe = (JAXBElement<?>) e;
Object xo = xe.getValue();
if (xo instanceof Integer) {
Integer id = (Integer) xo;
SCENE sc = findScene(id);
ol.add(sc);
}
}
}

If I use the generated ObjectFactory to get new nodes I have very little support over plain "new", In particular:
- no creation of required child nodes (e.g.: the lists needed to hold children).
- no enforcement of the default=xxx attribute.

The generated Element classes seem very rough. In particular:
- no methods to add/search/extract items from lists.
- no way to do automatic casting of JAXBElement<T> ti the "right" (T) value.

What am I doing wrong?
Where can I get some more information?

Thanks in Advance
ZioNemo
[Message sent by forum member 'zionemo' ]

http://forums.java.net/jive/thread.jspa?messageID=374389

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Simple STS Problem

2009-12-02T14:09:21Z

Get Nebeans 6.8
to work with Glassfish V3:
http://download.netbeans.org/netbeans/6.8/rc/

Sounds to like there is a Metro version conflict.
[Message sent by forum member 'jdg6688' ]

http://forums.java.net/jive/thread.jspa?messageID=374387

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Issues with Validation using schemas and ValidationEventHandler

2009-12-02T12:55:09Z

Here are some scenarios we are dealing with and the observations/questions for the same. We are trying to un marshall the XML and make sure that it is valid before consuming the Java objects.
1. When using the validation using custom Event Handler for validation we could catch the errors such as unexpected element in the source XML but it did not catch the errors for the attributes. e.g. Even when the attribute was a required attribute un-marshaling did not complain missing attribute.
2. The default event handler does not provide errors or stop the processing although the documentation says that the default handler will stop processing on error. We need to use the ValidationEventCollector.
3. When the instance inserted new elements from namespace other then the target namespace the -nv option of xjc compiler to do Lax validation did not help.
There are two issues here one is not able to handle the attribute level validation and secondly problem with the default event handler as well as ability to do Lax validation if necessary.

When we used the setSchema approach we were able to catch the attribute level issues but still could not use the -nv option as intended.
Clearly there is difference between validating the incoming XML with schemas and without schemas. I think it is un-fair to expect the schema files will always be available especially when we already habe the Java objects derived from them.

comments/suggestions?
thanks,
Prasad
[Message sent by forum member 'prasadmp' ]

http://forums.java.net/jive/thread.jspa?messageID=374378

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: Using UsernameToken wth SymmetricBinding?

2009-12-02T12:40:56Z

Well - I am a step further :-).
I also needed to add a SignedSupportingTokens policy assertion for the UsernameToken.
I've attached the updated wsdl file.

However, not I get this exception:
SEVERE: WSS1701: Sign operation failed.
com.sun.xml.wss.XWSSecurityException: Unsupported Key Binding:UsernameTokenBinding::
when actually trying to use call the service...

Moises
[Message sent by forum member 'mlejter' ]

http://forums.java.net/jive/thread.jspa?messageID=374377

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

boolean beforeMarshal(Marshaller, Object parent) return value

2009-12-02T12:32:34Z

Hi all
I didn't find anywhere what is meaning of boolean return value of[i] beforeMarshal() [/i]callback, which may be defined by object (http://java.sun.com/javase/6/docs/api/javax/xml/bind/Marshaller.html, "Marshal Event Callbacks")
May be anybody knows?

Thanx for any inputs
Sincerely
J.
[Message sent by forum member 'jabberw' ]

http://forums.java.net/jive/thread.jspa?messageID=374376

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: WSDL Query

2009-12-02T12:14:58Z

On Dec 2, 2009, at 11:31 AM, Fabian Ritzmann wrote:

> On 2.12.2009 19:24, Harold Carr wrote:
>>
>>> Does that give you what you are asking for?
>>> Perhaps"attribute" was the wrong term in the Metro universe.
>>> Essentially, these additions allow more information to be sent to the
>>> web service.
>>
>> Ah, the schema has additional elements added. Our JAXB expert should
>> give the definitive answer, but the old clients should continue to work
>> - the new info will be ignored.
>>
>> Try it out and let us know the results.
>
> This article gives a decent introduction to versioning web services [1]:
> http://www.ibm.com/developerworks/webservices/library/ws-version/

OK. In my case, there are not any namespace differences, only new elements. So it sounds like the only way to be able to use the new elements in a wsdl is to generate a new Java binding. Is that correct?

Big picture; If possible, I want to remove the requirement to generate a new java binding when new schema elements are added to the wsdl.

1: Is there a way to use the Java binding for the latest wsdl, but somehow check for the existence of the element at runtime? (before actually attempting to set value for the element?

2: Is there a way that a java binding generated from an older version of a wsdl can interrogate the new wsdl and set values for the new elements?

Thanks,

Jeff

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Using UsernameToken wth SymmetricBinding?

2009-12-02T11:57:17Z

Hi! I am trying to set up a web service that will just digitally sign messages.
I thought I could this to work using a UsernameToken for the ProtectionToken, via SymmetricBinding (which I thought was now supported in Metro, if I read this right: http://blogs.sun.com/SureshMandalapu/entry/passwordderivedkeys_support_in_metro ).

I've attached the relevant WSDL file.

It seems to generate all necessary artifacts ok - but when I try to run the client, I get this error:
com.sun.xml.wss.XWSSecurityException: java.lang.UnsupportedOperationException: http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Always not supported yet as IncludeToken policy

Any hints as to what I might be doing wrong?

Thank you!

Moises
[Message sent by forum member 'mlejter' ]

http://forums.java.net/jive/thread.jspa?messageID=374360

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

URL Patterns are not honored, WSDL location attribute value not honored

2009-12-02T11:46:12Z

At provider end, i was able to map the WSDL using jax-ws-catalog.xml configuration. See below the scenario

web.xml
-----------

<url-pattern>/addnumbers/service1</url-pattern>
<url-pattern>/addnumbers/service2</url-pattern>

sun-jax-ws.xml
---------------------

<endpoint
name="catalog"
interface="catalog.server.AddNumbersPortType"
implementation="catalog.server.AddNumbersImpl"
wsdl="WEB-INF/wsdl/AddNumbers.wsdl"
service="{http://example.com}AddNumbersService"
port="{http://example.com}AddNumbersPort"
url-pattern="/addnumbers/*" />

jax-ws-catalog.xml
--------------------------

<system systemId="http://localhost:8080/jaxws-catalog/addnumbers/service1?wsdl"
uri="../AddNumbers.wsdl"/>

<system systemId="http://localhost:8080/jaxws-catalog/addnumbers/service2?wsdl"
uri="../AddNumbers2.wsdl"/>

Now if you hit

http://localhost:8080/jaxws-catalog/addnumbers/service1?wsdl

although jax-ws runtime picks up specified WSDL but still it modifies
the location attribute to the value that is mapped in end point url-pattern attribute

<soap:address location="http://localhost:8080/jaxws-catalog/addnumbers?wsdl" />

Although web.xml, sun-jaxws.xml accepts wildcards in url-pattern attribute the
location attribute value remain

http://localhost:8080/jaxws-catalog/addnumbers?wsdl?
I see several problems here

1. url-pattern should not be an attribute in sun-jaxws.xml, it should be tag similar to web.xml
2. If url-pattern accepts a wildcard then the generated wsdl's location attribute value need to reflect the processed uri
3. I can get around this issue by cloning the enpoint tag and give a different value for the name attribute but the problem is it is creating 2 instance of Endpoint implementation
[Message sent by forum member 'smurugu' ]

http://forums.java.net/jive/thread.jspa?messageID=374358

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: WSDL Query

2009-12-02T10:24:18Z

> Yes, the old clients will work, but a new client with an old service will not I presume. Do I understand that correctly?

A new client/old service combo will probably result in the new client getting
null values for the new attributes.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Using different SSL Listeners on the same domain

2009-12-02T10:23:14Z

Hi all,

I don't know if this forum is the most suitable for this question. It is not about Metro, but at least it's about security :-)

I've configured two different SSL listeners on the same Glassfish instance/domain, one of them without client authentication (port 443), and the other with client authentication (mutual certificate exchange, on port 4433).

On the other hand, I have two different Web Applications (two .WAR files) installed on that Glassfish instance. I've configured each web.xml file with the CONFIDENTIAL flag, that indicates that a SSL connector is required (on both applications).

The problem is, how could I specify that one applications must work only on port 443 (without client authentication), and the other application must work only on port 4433 (with client authentication) ?

Is running two different Glassfish instances/domains the only solution? Has anyone experience with that?

Thanks!
Ernesto.
[Message sent by forum member 'ernestojpg' ]

http://forums.java.net/jive/thread.jspa?messageID=374340

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: WSDL Query

2009-12-02T09:47:01Z

On Dec 2, 2009, at 11:24 AM, Harold Carr wrote:

>
>> Does that give you what you are asking for?
>> Perhaps"attribute" was the wrong term in the Metro universe. Essentially, these additions allow more information to be sent to the web service.
>
> Ah, the schema has additional elements added. Our JAXB expert should give the definitive answer, but the old clients should continue to work - the new info will be ignored.

Yes, the old clients will work, but a new client with an old service will not I presume. Do I understand that correctly?

Fabian sent me a link to versioning services. I'll check that out.

Thanks

>
> Try it out and let us know the results.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: WSDL Query

2009-12-02T09:31:18Z

On 2.12.2009 19:24, Harold Carr wrote:

>
>> Does that give you what you are asking for?
>> Perhaps"attribute" was the wrong term in the Metro universe.
>> Essentially, these additions allow more information to be sent to the
>> web service.
>
> Ah, the schema has additional elements added. Our JAXB expert should
> give the definitive answer, but the old clients should continue to work
> - the new info will be ignored.
>
> Try it out and let us know the results.

This article gives a decent introduction to versioning web services [1]:
http://www.ibm.com/developerworks/webservices/library/ws-version/

Fabian

[1] Never mind the irrelevant excursion to UDDI at the end.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users

Re: WSDL Query

2009-12-02T09:24:30Z

> Does that give you what you are asking for?
> Perhaps"attribute" was the wrong term in the Metro universe. Essentially, these additions allow more information to be sent to the web service.

Ah, the schema has additional elements added. Our JAXB expert should give the
definitive answer, but the old clients should continue to work - the new info
will be ignored.

Try it out and let us know the results.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Metro - Users