NetBeans Forums

 FAQFAQ   SearchSearch   MemberlistMemberlist   RegisterRegister   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
  

Re: cannot generate WSDL for EE6 WS that is session bean

 
Post new topic   Reply to topic    NetBeans Forums -> Java EE Users
View previous topic :: View next topic  
Author Message
Jeff Rubinoff
Posted via mailing list.
PostPosted: Tue Jun 22, 2010 10:42 pm    Post subject: Re: cannot generate WSDL for EE6 WS that is session bean Reply with quote
It looks like the GlassFish people changed how service URLs are built,
between b20 when I created this service and FCS.
Note in your output where it says

FlowerAlbumService1 listening at address at
http://localhost:8080/FlowerServiceService/FlowerService

but the error message says

Unable to open web service tester page:
http://localhost:8080/FlowerAlbumService1/FlowerServiceService?Tester

Well, the web service is not listening at .../FlowerServiceService, it's listening at .../FlowerServiceService/FlowerService, so if you enter
http://localhost:8080/FlowerServiceService/FlowerService?tester into a browser address field, you'll get the tester.
However, at the moment I cannot get the customized WSDL to appear, only the default WSDL. So I have to consult with some engineers and figure out what's up.

Jeff



chrishuang wrote:

Quote:
Hi, Jeff,
I downloaded the complete sample of the web service fromthe NebBeans Samples
Catalog and tried to test the web service. I got the sample error.

any idea? many thanks
Chris


Back to top
Jeff Rubinoff
Posted via mailing list.
PostPosted: Tue Jun 22, 2010 11:43 pm    Post subject: Re: cannot generate WSDL for EE6 WS that is session bean Reply with quote
Chris,
Download and use the old b20 version of GlassFish available at
http://dlc.sun.com.edgesuite.net/glassfish/3.0.1/promoted/. (You know
how to register a server with NetBeans, right? In the Services tab.
Pretty self-explanatory.) Change the Run properties of your project to
use that server instead of the 3.0.1 shipped with NB 6.9. Everything
should then work fine. Just tested it.

Jeff

chrishuang wrote:

Quote:
Sorry Jeff,
I mean I got the same error.
Chris


Back to top
Jeff Rubinoff
Posted via mailing list.
PostPosted: Wed Jun 23, 2010 1:18 pm    Post subject: Re: cannot generate WSDL for EE6 WS that is session bean Reply with quote
I can't reproduce the error in generating the WSDL. Generates fine for me.
Did you create a fresh userdir when you installed 6.9, or did you import
settings from 6.8? That's often a culprit. Just rename the 6.9 userdir
and NB will create a new one when you launch it again.
Also, what JDK are you using?
You can work around the problem by commenting out @Stateless and @EJB,
generating the WSDL, and then uncommenting the annotations again.
However this should not be necessary.

Jeff

chrishuang wrote:

Quote:
Sorry Jeff,
I mean I got the same error.
Chris


Back to top
Jeff Rubinoff
Posted via mailing list.
PostPosted: Wed Jun 23, 2010 8:17 pm    Post subject: Re: cannot generate WSDL for EE6 WS that is session bean Reply with quote
If you had an earlier version of NB installed, when you installed NB
6.9, a dialog would have appeared asking if you wanted to import a user
directory from an earlier version of NetBeans. If you said no, the
installer created a fresh user directory.
Regarding which b20 to install: I'm pretty sure the smaller, web version
would work, but maybe install the full version to be safe.
Regarding ZIP vs EXE: ZIP is a ZIP directory. It's preconfigured. You
download it and unzip it to wherever you want it to be on your hard drive.
EXE is a Windows executable file. In this case, it's a Windows
installer. Note that the NetBeans program you installed was an .exe file
that launched a Windows installer.
It's up to you where you install these files or whether you unpack a ZIP
or run the Windows installer. However, I prefer to install
GlassFish--and all application servers--to a root directory. In any
case, better not to install to a path with spaces (such as the default
Windows /Program Files).

Jeff

chrishuang wrote:

Quote:
I did not create my own userdir when I installed 6.9 and I did not import
setting from 6.8 or 6.5. I am using JDK that comes with 6.9 which is
jdk.6.0_11.
I just tried again. Here is the info I got when I deployed:

Jun 23, 2010 9:08:17 AM com.sun.enterprise.glassfish.bootstrap.ASMain main
INFO: Launching GlassFish on Felix platform
Welcome to Felix
================
INFO: Perform lazy SSL initialization for the listener 'http-listener-2'
INFO: Starting Grizzly Framework 1.9.18-o - Wed Jun 23 09:09:04 PDT 2010
INFO: Starting Grizzly Framework 1.9.18-o - Wed Jun 23 09:09:04 PDT 2010
INFO: Grizzly Framework 1.9.18-o started in: 109ms listening on port 8181
INFO: Grizzly Framework 1.9.18-o started in: 109ms listening on port 4848
INFO: GlassFish Server Open Source Edition 3.0.1 (22) startup time :
Felix(46301ms) startup services(1123ms) total(47424ms)
INFO: Grizzly Framework 1.9.18-o started in: 156ms listening on port 8080
INFO: Grizzly Framework 1.9.18-o started in: 47ms listening on port 7676
INFO: Grizzly Framework 1.9.18-o started in: 78ms listening on port 3700
INFO: Binding RMI port to *:8686
INFO: Hibernate Validator bean-validator-3.0-JBoss-4.0.2
INFO: Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: JMXStartupService: Started JMXConnector, JMXService URL =
service:jmx:rmi://192.168.1.100:8686/jndi/rmi://192.168.1.100:8686/jmxrmi
INFO: Grizzly Framework 1.9.18-o started in: 16ms listening on port 8080
INFO: Using
com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate as
the delegate
INFO: Perform lazy SSL initialization for the listener 'http-listener-2'
INFO: Grizzly Framework 1.9.18-o started in: 32ms listening on port 8181
INFO: [Thread[GlassFish Kernel Main Thread,5,main]] started
INFO: {felix.fileinstall.poll (ms) = 5000, felix.fileinstall.dir =
C:\Program Files\glassfish-3.0.1\glassfish\modules\autostart,
felix.fileinstall.debug = 1, felix.fileinstall.bundles.new.start = true,
felix.fileinstall.tmpdir =
C:\Users\CHRISH~1\AppData\Local\Temp\fileinstall--3204500212694243107,
felix.fileinstall.filter = null}
INFO: SEC1002: Security Manager is OFF.
INFO: Security startup service called
INFO: SEC1143: Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.
INFO: Realm admin-realm of classtype
com.sun.enterprise.security.auth.realm.file.FileRealm successfully created.
INFO: Realm file of classtype
com.sun.enterprise.security.auth.realm.file.FileRealm successfully created.
INFO: Realm certificate of classtype
com.sun.enterprise.security.auth.realm.certificate.CertificateRealm
successfully created.
INFO: Security service(s) started successfully....
INFO: Created HTTP listener http-listener-1 on port 8080
INFO: Created HTTP listener http-listener-2 on port 8181
INFO: Created HTTP listener admin-listener on port 4848
INFO: Created virtual server server
INFO: Created virtual server __asadmin
INFO: Installed C:\Program
Files\glassfish-3.0.1\glassfish\modules\autostart\org.apache.felix.fileinstall-autodeploy-bundles.cfg
INFO: {felix.fileinstall.poll (ms) = 5000, felix.fileinstall.dir =
C:\Users\Chris Huang\.netbeans\6.9\config\GF3\domain1\autodeploy\bundles,
felix.fileinstall.debug = 1, felix.fileinstall.bundles.new.start = true,
felix.fileinstall.tmpdir =
C:\Users\CHRISH~1\AppData\Local\Temp\fileinstall--6754574491463314248,
felix.fileinstall.filter = null}
INFO: Virtual server server loaded system default web module
INFO: Installed C:\Program
Files\glassfish-3.0.1\glassfish\modules\autostart\org.apache.felix.scr.jar
INFO: Installed C:\Program
Files\glassfish-3.0.1\glassfish\modules\autostart\osgi-web-container.jar
INFO: Started bundle:
file:/C:/Program%20Files/glassfish-3.0.1/glassfish/modules/autostart/org.apache.felix.scr.jar
INFO: Started bundle:
file:/C:/Program%20Files/glassfish-3.0.1/glassfish/modules/autostart/osgi-web-container.jar
INFO: WSTX-COMMON-2007: Map CMT EJB web method
'org.flower.service.FlowerService'.'getFlower' with effective transaction
attribute of 'REQUIRED' to wsdl bounded operation
'{http://service.flower.org/}FlowerServicePort':'getFlower' with WS-AT
policy assertion(s) 'FlowerServicePortBinding_getFlower_WSAT_Policy'
INFO: WSTX-COMMON-2007: Map CMT EJB web method
'org.flower.service.FlowerService'.'getThumbnails' with effective
transaction attribute of 'REQUIRED' to wsdl bounded operation
'{http://service.flower.org/}FlowerServicePort':'getThumbnails' with WS-AT
policy assertion(s) 'FlowerServicePortBinding_getThumbnails_WSAT_Policy'
INFO: Metro monitoring rootname successfully set to:
amx:pp=/mon/server-mon[server],type=WSEndpoint,name=FlowerServiceService-FlowerServicePort
WARNING: Container org.glassfish.webservices.JAXWSContainer@37fdd2 doesn't
support class com.sun.xml.ws.api.server.Module
INFO: WELD-000900 1.0.1 (SP3)
INFO: Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
INFO: WS00019: EJB Endpoint deployed
FlowerAlbumService listening at address at
http://localhost:8080/FlowerServiceService/FlowerService
INFO: Loading application FlowerAlbumService at /FlowerAlbumService
INFO: FlowerAlbumService was successfully deployed in 14,289 milliseconds.
INFO: Server shutdown initiated
INFO: JMXStartupService: Stopped JMXConnectorServer:
service:jmx:rmi://192.168.1.100:8686/jndi/rmi://192.168.1.100:8686/jmxrmi
Jun 23, 2010 9:11:26 AM com.sun.enterprise.glassfish.bootstrap.ASMain main
INFO: Launching GlassFish on Felix platform
Welcome to Felix
================

Chris




Jeff Rubinoff wrote:


Quote:
I can't reproduce the error in generating the WSDL. Generates fine for me.
Did you create a fresh userdir when you installed 6.9, or did you import
settings from 6.8? That's often a culprit. Just rename the 6.9 userdir
and NB will create a new one when you launch it again.
Also, what JDK are you using?
You can work around the problem by commenting out @Stateless and @EJB,
generating the WSDL, and then uncommenting the annotations again.
However this should not be necessary.

Jeff

chrishuang wrote:



Quote:
Sorry Jeff,
I mean I got the same error.
Chris










Back to top
Jeff Rubinoff
Posted via mailing list.
PostPosted: Wed Jun 23, 2010 8:20 pm    Post subject: Re: cannot generate WSDL for EE6 WS that is session bean Reply with quote
After you install GlassFish 3.0.1 b20, you register it with NetBeans
IDE. There are a couple ways. I go to the Services window and
right-click the Servers node, then open the Add Server wizard. The
wizard is pretty self-explanatory.

Jeff

chrishuang wrote:

Quote:
Sorry I have never done this before, I need more instruction on add server.
first, which file I need to download?
glassfish-3.0.1-b20-windows.exe, or glassfish-3.0.1-b20.zip, or
glassfish-3.0.1-web-b20-windows.exe or glassfish-3.0.1-web-b20.zip

second, which directory should I downloaded to? And what's the rest of
instruction?

Chris


Jeff Rubinoff wrote:


Quote:
Chris,
Download and use the old b20 version of GlassFish available at
http://dlc.sun.com.edgesuite.net/glassfish/3.0.1/promoted/. (You know
how to register a server with NetBeans, right? In the Services tab.
Pretty self-explanatory.) Change the Run properties of your project to
use that server instead of the 3.0.1 shipped with NB 6.9. Everything
should then work fine. Just tested it.

Jeff

chrishuang wrote:



Quote:
Sorry Jeff,
I mean I got the same error.
Chris










Back to top
Display posts from previous:   
Post new topic   Reply to topic    NetBeans Forums -> Java EE Users All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum


Powered by phpBB
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo