January 2008 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: EntityManager trouble

by gduq

I don't know if this helps. but I vaguely recall having to make some changes to get tests to run inside eclipse via the TestNG plugin (not sure if this is even what you are trying to do) one of the things I remember having to do was add the \resources folder to the build path. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119288#4119288 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119288

18 years, 3 months

1
0
0 / 0

[Beginners Corner] - Re: Referencing EJBs from Scheduler w/JBOSS 4.2.2GA

by mjhammel

Okay, so it seems that injection doesn't work in anything other than session beans (that means not in Web Services or MBeans) according to this thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107353 So at least I know I should stop looking for why injection doesn't work in 4.2.2GA. But if I try to use the same mechanism I used in the Web Service in my schedulable, I get errors because I can't get a UserTransaction. I *must* have a transaction to use the EntityManager. So how do I get a transaction? Or do I need to stop using the EntityManager with my schedulable? If so, how do I get to my EJBs and Entity Beans? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119287#4119287 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119287

18 years, 3 months

1
0
0 / 0

[JBossWS] - Re: Can wsconsume do custom namespaces to package mapping?

by alessio.soldano＠jboss.com

"Brad Marshall" wrote : I need to map the various namespaces in our WSDL to different packages during code generation using wsconsume. With the Axis Wsdl2Java tool, I place my mappings in an NsToPkg.properties file and the tool picks them up. | | Can a JAXB or JAX-WS binding file accomplish this with wsconsume? I have not created one of these binding files before. Is there an example of a binding file that illustrates how to map a namespace to a package? | | It is critical to our business model that our one WSDL can be consumed by all our customers. Axis services and clients based on this WSDL have been in production for quite a while. | | | Here is a link to the binding customization authoritative documentation: http://jbws.dyndns.org/mediawiki/index.php?title=JBossWS_JAX-WS_Tools#JAX... ...and here is the wsconsume doc, please note the --binding option http://jbws.dyndns.org/mediawiki/index.php?title=Wsconsume View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119286#4119286 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119286

18 years, 3 months

1
0
0 / 0

[JBossWS] - How can I change mustUnderstand attribute of wsse:security e

by mariovvl

Hi, I'm writing a client for a webservice that requires message signing. I've configured it in the jboss-wsse-client.xml. Hence the generated soap envelope header contains something like: | <wsse:Security env:mustUnderstand='1' ...></wsse:Security> | Question: how can I set mustUnderstand to 0 (as is required by the webservice I'm calling) or put differently: how can I change the security element generated by JBoss? I thought I could modify it in a soap handler (configured in the application-client.xml), but the soapHeader doesn't seem to have the wsse:Security childElements at that time. My soap handler extends javax.xml.rpc.handler.GenericHandler. Thanks, Mario View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119285#4119285 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119285

18 years, 3 months

1
0
0 / 0

[JBossWS] - Re: More soap:address problems

by alessio.soldano＠jboss.com

"justinkwaugh" wrote : I glanced at the code, and it plainly just ignores the incoming request protocol. Why is this? If I am accessing it via an https:// URL, why would it not rewrite it using https://? | You might want to create a JIRA issue for this. anonymous wrote : | 2. The path to the endpoint is plain wrong. | | I have a context root specified in the jboss-web.xml of my war, and that is all it uses no matter what. It simply ignores the servlet name and rewrites the path with just the context-root even when I specify my own WSDL in the @WebService annotation. My servlet is specified in the web.xml as follows.. | | | | <servlet> | | <servlet-name>MyWebservice</servlet-name> | | <servlet-class>com.mycompany.webservices.MyWebservice</servlet-class> | | </servlet> | | <servlet-mapping> | | <servlet-name>MyWebservice</servlet-name> | | <url-pattern>/*</url-pattern> | | </servlet-mapping> | | | | My jboss-web.xml has the following: | | | | <jboss-web> | | <context-root>webservice</context-root> | | </jboss-web> | | | | The correct endpoint should be | https://myhost:443/webservice/MyWebservice | | but no matter what I do, it rewrites it to just | https://myhost:443/webservice | This is the right behaviour IMHO. You should use this to get the path /webservice/MyWebservice: | <servlet> | <servlet-name>MyWebservice</servlet-name> | <servlet-class>com.mycompany.webservices.MyWebservice</servlet-class> | </servlet> | <servlet-mapping> | <servlet-name>MyWebservice</servlet-name> | <url-pattern>/MyWebservice</url-pattern> | </servlet-mapping> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119284#4119284 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119284

18 years, 3 months

1
0
0 / 0

[JBossWS] - Re: Changing of soap:address location

by alessio.soldano＠jboss.com

"memema" wrote : I have a more complex situation: one internal JBoss server with the web service, and several forwards from externals apache web servers (sorry for my bad english). Different customers have different access points thought differents urls and domains (the customer A access to http://serverA/ws, customer B to http://serverB/ws, etc), but the internal web service and jboss are the same. The annotation solution doesn't work in my case. Another idea? | Not sure if this is exactly your use case, however you could comment out this | <property name="webServiceHost">${jboss.bind.address}</property> | in your jbossws.beans/META-INF/jboss-beans.xml file (leave modifySOAPAddress to true). This way the engine should rewrite the soap:address using the host/port used to invoke the servlet providing you the wsdl. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119283#4119283 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119283

18 years, 3 months

1
0
0 / 0

[JBossWS] - Re: web service endpoint dissappeared after restart

by alessio.soldano＠jboss.com

Accrding to the application server JIRA road map it is scheduled for 29/Feb/08. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119281#4119281 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119281

18 years, 3 months

1
0
0 / 0

[JBossWS] - Re: WS-Attachment on jbossws

by alessio.soldano＠jboss.com

With JBossWS you can use either MTOM or SOAP Attachments (SwA), WS-Attachments (DIME) is not supported. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119280#4119280 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119280

18 years, 3 months

1
0
0 / 0

[JBossWS] - Re: Cannot access web service with HTTP Basic Authentication

by alessio.soldano＠jboss.com

You should either protect the service only (allowing unauthenticated access to the wsdl contract, for example using secureWSDLAccess=false in your @WebContext annotation) or let your client consume a local copy of the wsdl you previously downloaded manually providing username & password. Please note that this also increase performance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119279#4119279 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119279

18 years, 3 months

1
0
0 / 0

[JBossWS] - Re: Cannot access web service with HTTP Basic Authentication

by PeterJ

Web service calls are done using POST, while the wsdl is access using GET. Change your web.xml to secure only POST messages, then your wsdl will be accessible once more (of course, it will be accessible to anyone) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119277#4119277 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4119277

18 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user January 2008