[JBossWS] - Re: Cannot access web service with HTTP Basic Authentication
by jeff norton
That FAQ does indeed cover my case and the solution works for me. I'm now a happy camper. Microsoft should feel intense embarrassment about the state of their HTTP implementation.
Might be good if someone updated http://jbws.dyndns.org/mediawiki/index.php?title=Authentication to point out the need to secure only POST and leave GET open to access the WSDL as well as put in a link to the problems with .NET clients. I tried to edit it but was not able.
As for wsconsume when I run it I do point it to a local wsdl file. I was always mystified as to why it needed the wsdl url at runtime since the client should have been generated with everything it needed (that's the way my .NET client works -- no WSDL needed at runtime). There seem to be two static methods (constructors) on Service. When I use the form that doesn't use the WSDL URL I get:
[exec] WARN - Cannot get port meta data for: {http://processlibrary.resonant.com/}RawDocumentRepositoryPort
| [exec] javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not setHow do you create an endpoint without the WSDL at runtime?
Anyway thanks for all the help. I'm now up and running!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119463#4119463
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119463
18 years, 3 months
[JBoss Seam] - Re: DataModel changes not reflected in view [possible newbie
by giannidoe
Yes clicking a letter (A-Z) on the repeat performs the search and then each row of the search results has an edit link which invokes editSite() on a conversation-scoped bean 'siteManager'.
@Stateful
| @Name("siteManager")
| public class WebsiteManagerBean implements WebsiteManager {
|
| @In(required = false)
| @Out(required = false)
| private Website website;
|
| @In
| private EntityManager entityManager;
|
| private boolean editMode;
|
| private boolean siteFound;
|
| @RequestParameter
| Integer id;
|
| public WebsiteManagerBean() {
| }
|
| @Begin
| public void editSite() {
| this.editMode = true;
| if (!findSite()) {
| facesMessages.addFromResourceBundle("website.not-found");
| log.error("Website not found for id " + id);
| }
| }
|
| private boolean findSite() {
| if (id == null) {
| return false;
| }
| this.website = entityManager.find(Website.class, id);
| siteFound = (null != website) ? true : false;
| return siteFound;
| }
|
|
| //@RaiseEvent("websiteUpdated")
| public void updateSite() {
| facesMessages.addFromResourceBundle("website.updated");
| log.info("Updated website details #{website.id}");
| }
I'm not doing anything particular to persist the changes, clicking 'save' on the edit page invokes updateSite() and the modifications are flushed to the database. I then click a link to return to the search results.
Initially the search results do not contain the modifications as they are held in the session-scoped bean and I'm not yet updating that when updateSite() is invoked (hence the @RaiseEvent being commented out).
The thing perplexing me is that when I invoke the original search again it seems to query the database but the changes to the entity do not appear in the search results, even though they are present in the DataModel.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119461#4119461
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119461
18 years, 3 months