[Design of JBoss Web Services] - Re: Endpoint redeployment
by richard_opalka
We've got the following problem:
Thomas want to support the following usecase:
* User will provide the web.xml which looks like:
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
| version="2.4">
|
| <!-- Test that we can deploy an already modified web.xml -->
| <servlet>
| <servlet-name>Hello</servlet-name>
| <servlet-class>org.jboss.wsf.stack.jbws.EndpointServlet</servlet-class>
| <init-param>
| <param-name>jboss.ws.endpoint</param-name>
| <param-value>org.jboss.test.ws.jaxrpc.jbws124.HelloJavaBean</param-value>
| </init-param>
| </servlet>
| <servlet-mapping>
| <servlet-name>Hello</servlet-name>
| <url-pattern>/*</url-pattern>
| </servlet-mapping>
| </web-app>
REQUIREMENT: Such web.xml should be detected as webservice archive.
If I will consider server side deployment implementation how it works now then
this requirement is in collision with the following usecase:
1) EJB archive is detected as webservice deployment
2) web.xml file is generated for all EJB webservices
3) web.xml file is modified in the same way as the above example (probably to not be detected as webservice deployment by non EJB deployer hooks in current implementation)
4) War deployer hooks are called for created war deployment
If I'll consider the above requirement that such web archives should be recognized as
webservice deployments then this archive will be recognized as webservices
archive and JBossWS war deployer hook will try to redeploy it. This redeployment will of course fail because the endpoint registry already have already registered EJB beans).
Questions to be answered during this discussion:
* How could non EJB deployers detect that deployment work had been already done by EJB deployers and nothing should be done for such archives?
* Do we really want to support the above requirement?
NOTE: In memory changes only are not possible, because we're talking about JBoss 4.x. So there's no workaround to creation of web.xml files on the file system.
Richard
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088446#4088446
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088446
17 years, 3 months
[Design of JBossXB] - Re: JBossXB-2.0.0.CR5
by alex.loubyansky＠jboss.com
The following collection bindings are wrong, so I am commenting them. They started to cause errors after Scott's fix.
Index: src/test/java/org/jboss/ejb/metadata/spec/MethodPermissionMetaData.java
| ===================================================================
| --- src/test/java/org/jboss/ejb/metadata/spec/MethodPermissionMetaData.java (revision 2575)
| +++ src/test/java/org/jboss/ejb/metadata/spec/MethodPermissionMetaData.java (working copy)
| @@ -103,7 +103,7 @@
| *
| * @param roles the roles.
| */
| - @XmlElement(name="role-name", type=NonNullLinkedHashSet.class)
| + @XmlElement(name="role-name"/*, type=NonNullLinkedHashSet.class*/)
| public void setRoles(Set<String> roles)
| {
| this.roles = roles;
| Index: src/test/java/org/jboss/javaee/metadata/spec/ResourceInjectionMetaData.java
| ===================================================================
| --- src/test/java/org/jboss/javaee/metadata/spec/ResourceInjectionMetaData.java (revision 2575)
| +++ src/test/java/org/jboss/javaee/metadata/spec/ResourceInjectionMetaData.java (working copy)
| @@ -122,7 +122,7 @@
| * @throws IllegalArgumentException for a null injectionTargets
| */
| //@SchemaProperty(name="injection-target", impl=NonNullLinkedHashSet.class, mandatory=false)
| - @XmlElement(name="injection-target", type=NonNullLinkedHashSet.class, required=false)
| + @XmlElement(name="injection-target", /*type=NonNullLinkedHashSet.class,*/ required=false)
| public void setInjectionTargets(Set<ResourceInjectionTargetMetaData> injectionTargets)
| {
| if (injectionTargets == null)
It seems like there is no way to say which Collection impl we want to use with the standard JAXB annotations. The spec says:
"jaxb2.0" wrote : If the property or field type is a parametric collection type, then
| @XmlElement.type() must be DEFAULT.class or
| collectionitem.class (since the type of the collection is already
| known).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088390#4088390
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088390
17 years, 3 months
[Design the new POJO MicroContainer] - Re: docbook build error
by alesj
Added that to settings, but now my docs build hangs at 18K of pdf file being produced.
| [INFO] Scanning for projects...
| [INFO] Reactor build order:
| [INFO] JBossMC Getting Started Guide (en_US)
| [INFO] JBossMC Getting Started Guide (aggregator)
| [INFO] JBossMC Reference Guide (en_US)
| [INFO] JBossMC Reference Guide (aggregator)
| [INFO] JBoss Microcontainer Docs
| WAGON_VERSION: 1.0-beta-2
| [INFO] ----------------------------------------------------------------------------
| [INFO] Building JBossMC Getting Started Guide (en_US)
| [INFO] task-segment: [install]
| [INFO] ----------------------------------------------------------------------------
| [INFO] [jdocbook:resources]
| [INFO] [jdocbook:generate]
| [INFO] building formatting result [C:\projects\microcontainer\docs\gettingstarted\en-US\target\docbook\pdf\gettingstarted.pdf]
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088389#4088389
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088389
17 years, 3 months