November 2006 - jboss-user - Jboss List Archives

[JBoss Eclipse IDE (users)] - Re: JBoss Eclipse IDE, Eclipse 3.1 and upcoming WTP versions

by srockny05

Hi - I was using MyEclipse with tomcat, but have just switched to JBoss 2.0.0.Beta2 running JBoss 4.0.5 with EJB3 support. I created 3 projects, app.har, appejb.jar and app.war and have successfully deployed to Jboss, and the ejb and web modules benig published in the JBoss Server View. The har file contains all my hibernate code. I love the product, the only complaint I have compared to MyEcplipse is I can't figure out how to make changes to my css, jsp, and javascript files and have them hot deploy without a server restart. I was able to do so with MyEclipse and tomcat. Is this possible to do with Jboss Eclipse IDE? If not this is a major disappointment for me. This really slows down my front end guys who are just working with the css, javascript. Thanks, Steve Rock View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987637#3987637 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987637

19 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: Local server is not initialized error when calling a met

by fmi2

Hi thanks for your input. I'm pretty sure that it is installed, I have the jboss-ejb3-all.jar in the project. Is this what you mean, I'm not sure why its not starting. Could it be something to do with my confirguration? Is there a wiki topic or documentation somewhere that has any more details about setting up SEAM in a Tomcat environment? thnx View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987636#3987636 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987636

19 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: Concerning nested conversation

by gavin.king＠jboss.com

BTW, the debug page will show you exactly what long-running conversations exist. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987635#3987635 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987635

19 years, 5 months

1
0
0 / 0

[JBossWS] - Creating keystore/truststore files

by osganian

Hi I'm having trouble creating my own server keystore and client truststore files. Using the wsse.keystore and wsse.truststore files that comes with the jbossws-samples-1.0.4.GA samples work fine. But when I use the procedure described in: http://docs.jboss.org/ejb3/app-server/reference/build/reference/en/html/t... to produce the keystore and truststore files my outgoing messages from my web services client is radically different (no headers in soap message) which results in a NPE in the WSSecurityDispatcher.handleInbound() method. How is the sample keystore/truststore files generated that is different than using the 3 keytool commands described in the above resource? Any help would be greatly appreciated, Mike View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987634#3987634 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987634

19 years, 5 months

1
0
0 / 0

[Beginners Corner] - Re: How not to use cluster environment

by nmohanbabu

In the deploy folder of jboss, there are four files which have an ''ip_mcast'' setting. 1. cluster-service.xml 2. tc5-cluster-service.xml 3. ejb3-clustered-sfsbcache-service.xml 4. ejb3-entity-cache-service.xml In each file, set ip_mcast="false" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987633#3987633 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987633

19 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: Concerning nested conversation

by gavin.king＠jboss.com

anonymous wrote : 1.1.0 CR1 solved some issues I was having with this There was a bug in previous versions that meant that if you encountered @Begin(join=true) after @End, the nested conversation stayed alive. http://jira.jboss.com/jira/browse/JBSEAM-511 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987632#3987632 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987632

19 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: Concerning nested conversation

by gavin.king＠jboss.com

anonymous wrote : Does calling an @End annotated method on an outer conversation guarantee that all nested conversations will be killed? Yes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987631#3987631 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987631

19 years, 5 months

1
0
0 / 0

[JBossWS] - Re: jbossws 1.0.4GA - wstools fail on a webervice

by ste

Using an AXIS2 WSDL I fall in a slight variation the error: 17:29:35,379 WARN [WSDL11Reader] Unprocessed extension element: {http://schemas.xmlsoap.org/wsdl/http/}address Exception in thread "main" org.jboss.ws.WSException: String passed is null | at org.jboss.ws.metadata.wsdl.WSDLUtils.firstLetterUpperCase(WSDLUtils.java:455) | at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:138) | at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:114) | at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:658) | at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:651) | at org.jboss.ws.tools.WSDLToJava.unwrapResponse(WSDLToJava.java:291) | at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:540) | at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:342) | at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:486) | at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:518) | at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:161) | at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:303) | at org.jboss.ws.tools.WSTools.process(WSTools.java:138) | at org.jboss.ws.tools.WSTools.generate(WSTools.java:120) | at org.jboss.ws.tools.WSTools.main(WSTools.java:61) with this WSDL: anonymous wrote : <wsdl:definitions xmlns:axis2="http://axisversion.sample" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns0="http://axisversion.sample/xsd" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:ns1="http://org.apache.axis2/xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://axisversion.sample"> | <wsdl:documentation>Version</wsdl:documentation> | - <wsdl:types> | - <xs:schema xmlns:ns="http://axisversion.sample/xsd" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://axisversion.sample/xsd"> | - <xs:element name="getVersionFault"> | - <xs:complexType> | - <xs:sequence> | <xs:element name="getVersionFault" type="xs:anyType" /> | </xs:sequence> | </xs:complexType> | </xs:element> | - <xs:element name="getVersionResponse"> | - <xs:complexType> | - <xs:sequence> | <xs:element name="return" nillable="true" type="xs:string" /> | </xs:sequence> | </xs:complexType> | </xs:element> | </xs:schema> | </wsdl:types> | <wsdl:message name="getVersionMessage" /> | - <wsdl:message name="getVersionResponse"> | <wsdl:part name="part1" element="ns0:getVersionResponse" /> | </wsdl:message> | - <wsdl:message name="getVersionFault"> | <wsdl:part name="part1" element="ns0:getVersionFault" /> | </wsdl:message> | - <wsdl:portType name="VersionPortType"> | - <wsdl:operation name="getVersion"> | <wsdl:input xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" message="axis2:getVersionMessage" wsaw:Action="urn:getVersion" /> | <wsdl:output message="axis2:getVersionResponse" /> | <wsdl:fault message="axis2:getVersionFault" name="getVersionFault" /> | </wsdl:operation> | </wsdl:portType> | - <wsdl:binding name="VersionSOAP11Binding" type="axis2:VersionPortType"> | <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> | - <wsdl:operation name="getVersion"> | <soap:operation soapAction="urn:getVersion" style="document" /> | - <wsdl:input> | <soap:body use="literal" /> | </wsdl:input> | - <wsdl:output> | <soap:body use="literal" /> | </wsdl:output> | - <wsdl:fault name="getVersionFault"> | <soap:body use="literal" /> | </wsdl:fault> | </wsdl:operation> | </wsdl:binding> | - <wsdl:binding name="VersionSOAP12Binding" type="axis2:VersionPortType"> | <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> | - <wsdl:operation name="getVersion"> | <soap12:operation soapAction="urn:getVersion" style="document" /> | - <wsdl:input> | <soap12:body use="literal" /> | </wsdl:input> | - <wsdl:output> | <soap12:body use="literal" /> | </wsdl:output> | - <wsdl:fault name="getVersionFault"> | <soap12:fault use="literal" name="getVersionFault" /> | </wsdl:fault> | </wsdl:operation> | </wsdl:binding> | - <wsdl:binding name="VersionHttpBinding" type="axis2:VersionPortType"> | <http:binding verb="POST" /> | - <wsdl:operation name="getVersion"> | <http:operation location="getVersion" /> | - <wsdl:input> | <mime:content type="text/xml" /> | </wsdl:input> | - <wsdl:output> | <mime:content type="text/xml" /> | </wsdl:output> | </wsdl:operation> | </wsdl:binding> | - <wsdl:service name="Version"> | - <wsdl:port name="VersionSOAP11port_http" binding="axis2:VersionSOAP11Binding"> | <soap:address location="http://127.0.0.1:8080/axis2/services/Version" /> | </wsdl:port> | - <wsdl:port name="VersionSOAP12port_http" binding="axis2:VersionSOAP12Binding"> | <soap12:address location="http://127.0.0.1:8080/axis2/services/Version" /> | </wsdl:port> | - <wsdl:port name="VersionHttpport1" binding="axis2:VersionHttpBinding"> | <http:address location="http://127.0.0.1:8080/axis2/rest/Version" /> | </wsdl:port> | </wsdl:service> | </wsdl:definitions> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987630#3987630 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987630

19 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: What do you guys think of this idea?

by gavin.king＠jboss.com

I don't really see it as a good idea, no :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987629#3987629 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987629

19 years, 5 months

1
0
0 / 0

[JBoss Seam] - Concerning nested conversation

by antispart

Does calling an @End annotated method on an outer conversation guarantee that all nested conversations will be killed? I'm trying to use nested conversations to manage a hierarchy of selections (perhaps I shouldnt use conversations for this?) and am finding problems with nested conversations living past their parent conversation (or at least that seems to be the issue). Example select category A - first conversation select subcategory B - nested conversation select sub-subcategory C - 2nd nested conversation call @End deselect subcategory B -> this kills conversation B and C so now only A is selected. I'm having issues where C will stay selected even after deselecting B. 1.1.0 CR1 solved some issues I was having with this, some issues still persist and I'm wondering if I should not use conversations to manage this type of thing or if perhaps there's something else wrong. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987628#3987628 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987628

19 years, 5 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 November 2006