[JBossWS] - jbossws-1.0.3.GA released
by heiko.braun＠jboss.com
As of this post I am happy to anounce that jbossws-1.0.3.GA is released. It is a drop in replacement for jbossws-1.0.x.GA in JBossAS-4.0.4.GA and also works in standalone Tomcat. This allows you to develop standard portable J2EE-1.4 web service endpoints in Tomcat that can be deployed to JBoss whenever full app server support is required.
http://labs.jboss.org/file-access/default/members/jbossws/downloads/Insta...
http://labs.jboss.com/portal/jbossws/user-guide/en/html/installation.html
What's new
----------
Feature Requests
* [JBWS-1160] - XOP Inline base64 for doc/lit requests
* [JBWS-1090] - preventing override of webservices.xml when multiple web services are processed with wstools
* [JBWS-1106] - java.io.NotSerializableException: org.jboss.ws.wsse.SimplePrincipal
* [JBWS-1119] - Add support for fault signing and encryption
Bugs
* [JBWS-482] - SOAPContentElement caches stale data
* [JBWS-983] - Configure SOAPAction on the Call object
* [JBWS-993] - JSR-181 POJO deploy fails using existing WSDL
* [JBWS-996] - JSR181 Handler config throws MalformedURLException
* [JBWS-1097] - Using the UsernameToken profile a keystore and truststore is still required.
* [JBWS-1107] - Spaces around the class specified in servlet-class of the POJO endpoint causes ClassNotFound exception.
* [JBWS-1110] - MTOM request send from .NET do fail with "invalid stream header"
* [JBWS-1117] - Client configured for UsernameToken but doesn't provide the username or password causes a NullPointerException
* [JBWS-1121] - Client security configuration not loaded when client deployed with issolated classloader.
* [JBWS-1125] - Support doc/lit with empty soap body elements
* [JBWS-1131] - NullPointer if no port type found in wsdl.
* [JBWS-1138] - DOMEnvelopeBuilder misses global namespace declaration
* [JBWS-1144] - Soapaction field not populated in wsdl for annotation based webservices
* [JBWS-1145] - SOAP faults contain multiple faultcode and faultstring elements
* [JBWS-1146] - DOM child methods on SOAPBodyImpl do not handle faults correctly
Tasks
* [JBWS-831] - Describe release procedure and hand over to QA
* [JBWS-1044] - Release jbossws-1.0.3.GA binary
* [JBWS-1067] - Add "Endpoint Config" to documentation
* [JBWS-1124] - Scoped class loading domains for WS endpoints
For details see the change log.
http://jira.jboss.com/jira/browse/JBWS?report=com.atlassian.jira.plugin.s...
--
Have fun,
the JBossWS Team
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968591#3968591
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968591
19 years, 7 months
[JBoss Seam] - Problem: Custom validate methods in EJBs crash
by bfo81
Well, custom validators belong to a real-life JSF web apllication like coffee to a good start into the day ;).
Let's take an example (there are many occurences of such a situation in my current app, but I love easy examples *g*):
- Entity Person
- has a n:m relation to multiple other persons (friends)
- has a relation to one specific person (best_friend)
When editing/creating a person you pick his/her friends from a list of persons (SelectManyMenu) and the best friend, too, (but from a SelectOneMenu).
So far so good, that was easy. BUT: There is an important constraint: The best_friend must be one of your friends, of course. So it's important to check this before saving.
There are two possibilities:
- In the action method ("store"): If best_friend is not contained in friends, add an error message, mark the transaction as rollback-only and redisplay the page (empty outcome: return null). Works, but it's UGLY
- In a custom JSF validator: BEAUTIFUL :)
Problem: The custom validator (that would be added to the best friend's SelectOneMenu) needs not only be aware of the best friend, but also of the list of friends. It's a "complex" validator (if I may call it like this), since it needs more information than only the status of the field it belongs to.
Possible Solution: Add a validateBestFriend(FacesContext, UIComponent, Object) method to the PersonEditorBean (SFSB), which holds the state of the edited person. So there the validator method has access to all the information it needs and can perform the check. If you select a "non-friend" as best friend, it throws a ValidatorException.
New problem: The ValidatorException is caught by the Stateful Bean and the app crashed with an exception report. The ValidatorException is not passed through to JSF as EJB3 intervenes. DAMN!
So any idea how to make EJB3 ignore the Exception and pass it through? Or how to have such a "complex" validation performed in an other way?
I'd be thankful for any answer :).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968586#3968586
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968586
19 years, 7 months
[Persistence, JBoss/CMP, Hibernate, Database] - Hibernate Annotations or xml SQL-Mapping?
by commy
Hi there!
I have a Problem with a project. We use Hibernate to store and manage persistent objects. At the moment, we use xml mapping files. But I'm not sure if it satisfies our needs.
The problem is: we use JSF. Saving new data is no problem, but edit allready stored data? I can't get it to work.
I tried the following:
The resource.java is mapped with a normal xml file, no problem with that.
Here's a jsf table with all the resources.
| <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
| <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
|
| <f:view>
| <h:form>
| <f:verbatim>
| <b>Resources
| </f:verbatim>
| <h:dataTable value="#{resourceutil.resources}" var="resource">
| <h:column>
| <f:facet name="header">
| <h:outputText value="id" />
| </f:facet>
| <h:outputText value="#{resource.id}" />
| </h:column>
| <h:column>
| <f:facet name="header">
| <h:outputText value="name" />
| </f:facet>
| <h:outputText value="#{resource.name}" />
| </h:column>
| <h:column>
| <f:facet name="header">
| <h:outputText value="desc" />
| </f:facet>
| <h:outputText value="#{resource.description}" />
| </h:column>
| <h:column>
| <f:facet name="header">
| <h:outputText value="edit" />
| </f:facet>
| <h:commandLink action="#{resource.edit}" value="edit"><f:param name="id" value="#{resource.id}"/></h:commandLink>
| </h:column>
| </h:dataTable>
| <br />
| </h:form>
| <h:form>
| <h:commandButton action="addResource" value="Add" />
| </h:form>
| </f:view>
|
By clicking edit, i'd like to het on a page to edit the data stored in the resources.
resource.edit() returns a value, and we are navigate (by jsf navigation rules) to the following page:
| <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
| <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
|
| <f:view>
| <div align="left">
| <h:form>
| <f:verbatim>
| <b>Add or Edit a Resource
| </f:verbatim>
| <h:panelGrid columns="2">
| <h:outputText styleClass="portlet-font" value="Resource Name:" />
| <h:inputText value="#{resource.name}" align="center" required="true" />
| <h:outputText styleClass="portlet-font" value="Resource Description:" />
| <h:inputText value="#{resource.description}" align="center"
| required="true" />
| </h:panelGrid>
| <br />
| <h:commandButton action="#{resource.save}" value="Add" />
| </h:form>
| <h:form>
| <h:commandButton action="viewResources" value="View Resources" />
| </h:form>
| </div>
| </f:view>
|
How can i tell jsf which object it has to display? Or can I only do this if i use annotations / ejb?
I'm very thankfull for every information
Greetings, Markus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968583#3968583
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968583
19 years, 7 months