[JBoss JIRA] Created: (JBIDE-7281) Wizards should not allow user to select unsupported JAX-WS spec version
by Lukas Jungmann (JIRA)
Wizards should not allow user to select unsupported JAX-WS spec version
-----------------------------------------------------------------------
Key: JBIDE-7281
URL: https://jira.jboss.org/browse/JBIDE-7281
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.Beta1
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
-create a dynamic web project with target runtime set to JBossAS6-M5
-create a ws client there with JAX-WS spec set to 2.1 and finish the wizard
=> generated code is of JAX-WS version 2.2
default ws stack in JBossAS6-M5 does not seem to allow user to set JAX-WS spec version. Even though the wsconsume's output says it is generating JAX-WS 2.1 code, it in fact the generated code is of version 2.2
jlukas@lukas-laptop:~/latest/jboss-6.0.0.20100911-M5/bin$ ./wsconsume.sh --target=2.2 -o /tmp/fff -k http://footballpool.dataaccess.eu/data/info.wso?WSDL
Could not find log4j.xml configuration, logging to console.
WSConsume (CXF) does not allow to setup the JAX-WS specification target, using JAX-WS 2.1.
log4j:WARN No appenders could be found for logger (org.apache.cxf.common.logging.LogUtils).
log4j:WARN Please initialize the log4j system properly.
Loading FrontEnd jaxws ...
Loading DataBinding jaxb ...
wsdl2java -compile -exsh false -d /tmp/fff -verbose -classdir /tmp/fff -allowElementReferences http://footballpool.dataaccess.eu/data/info.wso?WSDL
wsdl2java - Apache CXF 2.2.10
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBIDE-8198) Support @Exact annotation
by Alexey Kazakov (JIRA)
Support @Exact annotation
-------------------------
Key: JBIDE-8198
URL: https://issues.jboss.org/browse/JBIDE-8198
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi (jsr-299)
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.x
2.2. @Exact
Annotating an injection point with @Exact allows you to select an exact implementation of the injection point type to inject. For example:
interface PaymentService {
...
}
class ChequePaymentService implements PaymentService {
...
}
class CardPaymentService implements PaymentService {
...
}
class PaymentProcessor {
@Inject @Exact(CardPaymentService.class)
PaymentService paymentService;
...
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBIDE-8200) Support @FullyQualified annotation
by Alexey Kazakov (JIRA)
Support @FullyQualified annotation
----------------------------------
Key: JBIDE-8200
URL: https://issues.jboss.org/browse/JBIDE-8200
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdi (jsr-299)
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.x
2.5. @FullyQualified bean names
According to the CDI standard, the @Named annotation assigns a name to a bean equal to the value specified in the @Named annotation or, if a value is not provided, the simple name of the bean class. This behavior aligns is with the needs of most application developers. However, framework writers should avoid trampling on the "root" bean namespace. Instead, frameworks should specify qualified names for built-in components. The motivation is the same as qualifying Java types. The @FullyQualified provides this facility without sacrificing type-safety.
Seam Solder allows you to customize the bean name using the complementary @FullyQualified annotation. When the @FullyQualified annotation is added to a @Named bean type, producer method or producer field, the standard bean name is prefixed with the name of the Java package in which the bean resides, the segments separated by a period. The resulting fully-qualified bean name (FQBN) replaces the standard bean name.
package com.acme;
@FullyQualified @Named
public class NamedBean {
public String getAge() {
return 5;
}
}
The bean in the previous code listing is assigned the name com.acme.namedBean. The value of its property age would be referenced in an EL expression (perhaps in a JSF view template) as follows:
#{com.acme.namedBean.age}
The @FullyQualified annotation is permitted on a bean type, producer method or producer field. It can also be used on a Java package, in which case all @Named beans in that package get a bean name which is fully-qualified.
@FullyQualified
package com.acme;
If you want to use a different Java package as the namespace of the bean, rather than the Java package of the bean, you specify any class in that alternative package in the annotation value.
package com.acme;
@FullyQualified(ClassInOtherPackage.class) @Named
public class CustomNamespacedNamedBean {
...
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months