Medrec tutorial 10

Hi ,
I am facing problems with the Med rec tutorial 10 , the output of ejbgen is
as follows, please help
E:\Work\JAVAPROJECTS\medrec_tutorial\src\physicianEar\physSessionEjbs\com\be
a\medrec\controller>java weblogic.tools.ejbgen.EJ
BGen PhysicianSessionEJB.java -d
E:\work\javaprojects\medrec_tutorial\build\physicianEar\physSessionEjbs -des
criptorDir E:\wo
rk\javaprojects\medrec_tutorial\build\physicianEar\physSessionEjbs\META-INF
Loading source file PhysicianSessionEJB.java...
Constructing Javadoc information...
PhysicianSessionEJB.java:3: package com.bea.medrec.utils does not exist
import com.bea.medrec.utils.MedRecUtils;
^
PhysicianSessionEJB.java:4: package com.bea.medrec.value does not exist
import com.bea.medrec.value.Record;
^
PhysicianSessionEJB.java:5: package com.bea.medrec.value does not exist
import com.bea.medrec.value.RecordsSummary;
^
PhysicianSessionEJB.java:6: package com.bea.medrec.value does not exist
import com.bea.medrec.value.Search;
^
PhysicianSessionEJB.java:7: package com.bea.medrec.webservices does not
exist
import com.bea.medrec.webservices.*;
^
PhysicianSessionEJB.java:14: package org.apache.log4j does not exist
import org.apache.log4j.Logger;
^
PhysicianSessionEJB.java:37: cannot resolve symbol
symbol : class Logger
location: class com.bea.medrec.controller.PhysicianSessionEJB
private static Logger logger =
^
PhysicianSessionEJB.java:42: cannot resolve symbol
symbol : class MedRecWebServicesPort
location: class com.bea.medrec.controller.PhysicianSessionEJB
private MedRecWebServicesPort port;
^
PhysicianSessionEJB.java:76: cannot resolve symbol
symbol : class Record
location: class com.bea.medrec.controller.PhysicianSessionEJB
public void addRecord(Record pRecord)
^
PhysicianSessionEJB.java:111: cannot resolve symbol
symbol : class Record
location: class com.bea.medrec.controller.PhysicianSessionEJB
public Record getRecord(Integer pId) throws RemoteException
^
PhysicianSessionEJB.java:152: cannot resolve symbol
symbol : class RecordsSummary
location: class com.bea.medrec.controller.PhysicianSessionEJB
public RecordsSummary getRecordsSummary(Integer pId)
^
PhysicianSessionEJB.java:192: cannot resolve symbol
symbol : class Search
location: class com.bea.medrec.controller.PhysicianSessionEJB
public Collection searchPatients(Search pSearch) throws RemoteException
^
PhysicianSessionEJB.java:295: cannot resolve symbol
symbol : class MedRecWebServicesPort
location: class com.bea.medrec.controller.PhysicianSessionEJB
private MedRecWebServicesPort getMedRecWebServicesPort()
^
EJBGen 2.13beta
Creating
E:\work\javaprojects\medrec_tutorial\build\physicianEar\physSessionEjbs\com\
bea\medrec\controller\PhysicianSessi
onHome.java
Creating
E:\work\javaprojects\medrec_tutorial\build\physicianEar\physSessionEjbs\com\
bea\medrec\controller\PhysicianSessi
on.java
javadoc: In doclet class weblogic.tools.ejbgen.EJBGen, method start has
thrown an exception java.lang.reflect.InvocationTarg
etException
weblogic.tools.ejbgen.EJBGenException: Error: Couldn't create directory
"E:\work\javaprojects\medrec_tutorial\build\physicia
nEar\physSessionEjbs\E:\work\javaprojects\medrec_tutorial\build\physicianEar
\physSessionEjbs\META-INF\"
at weblogic.tools.ejbgen.Utils.error(Utils.java:171)
at weblogic.tools.ejbgen.Utils.errorNoLineNumber(Utils.java:176)
at weblogic.tools.ejbgen.Utils.createDir(Utils.java:438)
at weblogic.tools.ejbgen.Utils.getPrintWriter(Utils.java:375)
at
weblogic.tools.ejbgen.DDGenerator.generateCode(DDGenerator.java:28)
at weblogic.tools.ejbgen.EJBGen.start(EJBGen.java:330)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:193)
at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:92)
at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:301)
at com.sun.tools.javadoc.Start.begin(Start.java:120)
at com.sun.tools.javadoc.Main.execute(Main.java:41)
at com.sun.tools.javadoc.Main.main(Main.java:31)
at weblogic.tools.ejbgen.EJBGen.main(EJBGen.java:685)
1 error
13 warnings
Thanks & regards,
Amit Mawkin

Please refer to reply post to topic "Med Rec - Tutorial 10, Procedure 2,
Step 4". Thank you.
"Weblogic" <[email protected]> wrote in message
news:[email protected]...
Hi ,
I am facing problems with the Med rec tutorial 10 , the output of ejbgenis
as follows, please help
E:\Work\JAVAPROJECTS\medrec_tutorial\src\physicianEar\physSessionEjbs\com\be
a\medrec\controller>java weblogic.tools.ejbgen.EJ
BGen PhysicianSessionEJB.java -d
E:\work\javaprojects\medrec_tutorial\build\physicianEar\physSessionEjbs -des
criptorDir E:\wo
rk\javaprojects\medrec_tutorial\build\physicianEar\physSessionEjbs\META-INF
Loading source file PhysicianSessionEJB.java...
Constructing Javadoc information...
PhysicianSessionEJB.java:3: package com.bea.medrec.utils does not exist
import com.bea.medrec.utils.MedRecUtils;
^
PhysicianSessionEJB.java:4: package com.bea.medrec.value does not exist
import com.bea.medrec.value.Record;
^
PhysicianSessionEJB.java:5: package com.bea.medrec.value does not exist
import com.bea.medrec.value.RecordsSummary;
^
PhysicianSessionEJB.java:6: package com.bea.medrec.value does not exist
import com.bea.medrec.value.Search;
^
PhysicianSessionEJB.java:7: package com.bea.medrec.webservices does not
exist
import com.bea.medrec.webservices.*;
^
PhysicianSessionEJB.java:14: package org.apache.log4j does not exist
import org.apache.log4j.Logger;
^
PhysicianSessionEJB.java:37: cannot resolve symbol
symbol : class Logger
location: class com.bea.medrec.controller.PhysicianSessionEJB
private static Logger logger =
^
PhysicianSessionEJB.java:42: cannot resolve symbol
symbol : class MedRecWebServicesPort
location: class com.bea.medrec.controller.PhysicianSessionEJB
private MedRecWebServicesPort port;
^
PhysicianSessionEJB.java:76: cannot resolve symbol
symbol : class Record
location: class com.bea.medrec.controller.PhysicianSessionEJB
public void addRecord(Record pRecord)
^
PhysicianSessionEJB.java:111: cannot resolve symbol
symbol : class Record
location: class com.bea.medrec.controller.PhysicianSessionEJB
public Record getRecord(Integer pId) throws RemoteException
^
PhysicianSessionEJB.java:152: cannot resolve symbol
symbol : class RecordsSummary
location: class com.bea.medrec.controller.PhysicianSessionEJB
public RecordsSummary getRecordsSummary(Integer pId)
^
PhysicianSessionEJB.java:192: cannot resolve symbol
symbol : class Search
location: class com.bea.medrec.controller.PhysicianSessionEJB
public Collection searchPatients(Search pSearch) throws RemoteException
^
PhysicianSessionEJB.java:295: cannot resolve symbol
symbol : class MedRecWebServicesPort
location: class com.bea.medrec.controller.PhysicianSessionEJB
private MedRecWebServicesPort getMedRecWebServicesPort()
^
EJBGen 2.13beta
Creating
E:\work\javaprojects\medrec_tutorial\build\physicianEar\physSessionEjbs\com\
bea\medrec\controller\PhysicianSessi
onHome.java
Creating
E:\work\javaprojects\medrec_tutorial\build\physicianEar\physSessionEjbs\com\
bea\medrec\controller\PhysicianSessi
on.java
javadoc: In doclet class weblogic.tools.ejbgen.EJBGen, method start has
thrown an exception java.lang.reflect.InvocationTarg
etException
weblogic.tools.ejbgen.EJBGenException: Error: Couldn't create directory
"E:\work\javaprojects\medrec_tutorial\build\physicia
nEar\physSessionEjbs\E:\work\javaprojects\medrec_tutorial\build\physicianEar
\physSessionEjbs\META-INF\"
at weblogic.tools.ejbgen.Utils.error(Utils.java:171)
at weblogic.tools.ejbgen.Utils.errorNoLineNumber(Utils.java:176)
at weblogic.tools.ejbgen.Utils.createDir(Utils.java:438)
at weblogic.tools.ejbgen.Utils.getPrintWriter(Utils.java:375)
at
weblogic.tools.ejbgen.DDGenerator.generateCode(DDGenerator.java:28)
at weblogic.tools.ejbgen.EJBGen.start(EJBGen.java:330)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:193)
atcom.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:92)
at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:301)
at com.sun.tools.javadoc.Start.begin(Start.java:120)
at com.sun.tools.javadoc.Main.execute(Main.java:41)
at com.sun.tools.javadoc.Main.main(Main.java:31)
at weblogic.tools.ejbgen.EJBGen.main(EJBGen.java:685)
1 error
13 warnings
Thanks & regards,
Amit Mawkin

Similar Messages

Med Rec medrec tutorial 10 deployments-- EJB Modules EJB is not shown

This note adds missing steps in the Med Rec (medrec) Tutorial 10
The tutorial shows how to use EJBGEN to generate EJB classes (incl java source) from .ejb files.
Unfortunately it is missing a few key details. These are described below.
Many thanks to Chris Wall for supplying the answers and hints.
Q: The tutorial includes deploying the manually generated physSessionEjb’s. After doing the step that generates the PhysSession*.java files, onefinds that when trying to deploy that there are no class files – nothing has been built. Are the class files supposed to be generated by the ejbgen step?
[Chris] No, EJBGen just generates the local and remote interfaces and descriptors only. An additional step should be added to explain how to build the newly generated EJBs. I believe you are correct in calling “src/physicianEar$ ant –f build.xml build”.
Q: Manually built the class files using ‘ant –f build.xml build’ in the physicianEar src dir – but that failed in the acc.split.dir step with class not found /org/apache/struts/action/ActionForm.
Obviously did not get the struts jars on the classpath. But as much of the build as completed did include creating the class files.
[Chris] Yes, it looks like struts.jar is not in the classpath. Is this the “build.split.dir” or “appc.split.dir” target? In either case, wlcompile and wlappc should recognized all libs in "${app-inf.dest.lib}" and append them to the compile/appc classpath automatically. The libs should have been copied during the “prepare” target. Can you make sure that struts.jar exists in c:/medrec_tutorial/build/physicianEar/APP-INF/lib? If not, re-run the target with verbose: “src/physicianEar$ ant -verbose -f build.xml build”, and make sure that the libs are copied in the “prepare” target.
Q: When doing the deploy step, we get no errors but on the console window and do not see the tutorial_deployment item under DeploymentsàEJB Modules. There is something under Deployments-->Applications --> tutorial_deployment. It appears the deploy failed since there’s nothing under Deployments --> EJB Modules, and what is there is ‘left over’ from deploying the jar (the ear?) that contains the stuff deployed by the deploy step at the start of tutorial 10.
[Chris] Once the build is successful, you must deploy the EAR. This is done by executing : “src/physicianEar$ ant -f build.xml redeploy.physician.ear”. Again, a step that was left out. Yes, you should be looking at Deployments--> Applications--> tutorial_deployment. So, to summarize: generated the local and remote and descriptors for the EJB, compile the EJB and package the EAR, deploy the EAR, and then view the deployment in the console.

This note adds missing steps in the Med Rec (medrec) Tutorial 10
The tutorial shows how to use EJBGEN to generate EJB classes (incl java source) from .ejb files.
Unfortunately it is missing a few key details. These are described below.
Many thanks to Chris Wall for supplying the answers and hints.
Q: The tutorial includes deploying the manually generated physSessionEjb’s. After doing the step that generates the PhysSession*.java files, onefinds that when trying to deploy that there are no class files – nothing has been built. Are the class files supposed to be generated by the ejbgen step?
[Chris] No, EJBGen just generates the local and remote interfaces and descriptors only. An additional step should be added to explain how to build the newly generated EJBs. I believe you are correct in calling “src/physicianEar$ ant –f build.xml build”.
Q: Manually built the class files using ‘ant –f build.xml build’ in the physicianEar src dir – but that failed in the acc.split.dir step with class not found /org/apache/struts/action/ActionForm.
Obviously did not get the struts jars on the classpath. But as much of the build as completed did include creating the class files.
[Chris] Yes, it looks like struts.jar is not in the classpath. Is this the “build.split.dir” or “appc.split.dir” target? In either case, wlcompile and wlappc should recognized all libs in "${app-inf.dest.lib}" and append them to the compile/appc classpath automatically. The libs should have been copied during the “prepare” target. Can you make sure that struts.jar exists in c:/medrec_tutorial/build/physicianEar/APP-INF/lib? If not, re-run the target with verbose: “src/physicianEar$ ant -verbose -f build.xml build”, and make sure that the libs are copied in the “prepare” target.
Q: When doing the deploy step, we get no errors but on the console window and do not see the tutorial_deployment item under DeploymentsàEJB Modules. There is something under Deployments-->Applications --> tutorial_deployment. It appears the deploy failed since there’s nothing under Deployments --> EJB Modules, and what is there is ‘left over’ from deploying the jar (the ear?) that contains the stuff deployed by the deploy step at the start of tutorial 10.
[Chris] Once the build is successful, you must deploy the EAR. This is done by executing : “src/physicianEar$ ant -f build.xml redeploy.physician.ear”. Again, a step that was left out. Yes, you should be looking at Deployments--> Applications--> tutorial_deployment. So, to summarize: generated the local and remote and descriptors for the EJB, compile the EJB and package the EAR, deploy the EAR, and then view the deployment in the console.

Can't compile the medrec tutorial

I can't build the medrec tutorial. Following the Tutorial 10: Exposing a Stateless
Session EJB as a Web Service, I execute the command "ant prepare build.split.dir".
But the medrecEar
can't be compiled correctly.
There are primarily two kinds of errors/warnings:
1)some classes, such as AdminSession can't be resolved;
2)EJB Local Reference doesn't have a JNDI name.
Who could help me. Thank you.

When you compile through J2EE it should give no apache type errors. You must of included apache xml cocoon jar files in the CLASSPATH as well later put the j2ee.jar. However j2ee.jar has XML libraries, no need to include other thrid party xml libaries.
Other words its picking your thrid party xml jar files first and using that instead of your j2ee.jar xml libaries.
Cheers
Abraham Khalil

MedRec Tutorial Step 12

When I try to do Step 12 of the MedRec tutorial, the "ant deploy.dev" command ends in a compilation failure. It fails to compile the class PhysBaseLookupDispatchAction, because of a reference to the class com.bea.medrec.controller.PhysicianSession. I cannot find this class anywhere, not even in the original zip file.
I don't think I missed a prerequisite step anywhere, except that I couldn't get the webservices tutorials (10 and 11) to work properly.

When I try to do Step 12 of the MedRec tutorial, the "ant deploy.dev" command ends in a compilation failure. It fails to compile the class PhysBaseLookupDispatchAction, because of a reference to the class com.bea.medrec.controller.PhysicianSession. I cannot find this class anywhere, not even in the original zip file.
I don't think I missed a prerequisite step anywhere, except that I couldn't get the webservices tutorials (10 and 11) to work properly.

Fix on MedRec Tutorial 10 will break tutorial 11

According to Chris Wall, tutorial 10 of MedRec needs the following fix:
1.) Add the following jars to your classpath. If these jars do not exist,
compile and create them thru the src/common build script.
C:\medrec_tutorial\build\physicianEar\APP-INF\lib\log4j-1.2.8.jar;
C:\medrec_tutorial\build\physicianEar\APP-INF\lib\value.jar;
C:\medrec_tutorial\build\physicianEar\APP-INF\lib\webServicesEjb_client.jar;
C:\medrec_tutorial\build\physicianEar\APP-INF\lib\utils.jar
2.) EJBGen 2.15 contains the -descriptorDir feature; 8.1 GA contains EJBGen
2.13beta. Please remove this flag from your cmdline. You will also need to
manually create the META-INF directory and copy the resultant descriptors to
this directory.
==============================================
Ok, I did that, and it worked. But when I did tutorial 11 Step 2, it gave me
this err msg:
C:\medrec_tutorial\src\medrecEar>ant -f my_webserv.xml
Buildfile: my_webserv.xml
build.ws:
[autotype] Autotyping for javaComponents com.bea.medrec.webservices.MedRecWebServices
[autotype] java.lang.NoSuchMethodException: weblogic.webservice.context.WebServiceContext.<init>()
[autotype] at java.lang.Class.getConstructor0(Class.java:1769)
[autotype] at java.lang.Class.getConstructor(Class.java:1002)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ensureValidClass(JavaInspector.java:1049)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.fillDescriptor(JavaInspector.java:174)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.getDescriptor(JavaInspector.java:139)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.createDescriptorForClass(JavaInspector.java:106)
[autotype] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compiler.java:106)
[autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:89)
[autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:102)
[autotype] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.addMapping(TypeMappingBuilderBase.java:180)
[autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.doTypeMapping(Java2SchemaImpl.java:267)
[autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.run(Java2SchemaImpl.java:167)
[autotype] at weblogic.webservice.tools.build.internal.Component2SchemaImpl.run(Component2SchemaImpl.java:151)
[autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.doComponent2Schema(JavaSchema.java:365)
[autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.execute(JavaSchema.java:172)
[autotype] at org.apache.tools.ant.Task.perform(Task.java:317)
[autotype] at org.apache.tools.ant.Target.execute(Target.java:309)
[autotype] at org.apache.tools.ant.Target.performTasks(Target.java:334)
[autotype] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[autotype] at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
[autotype] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[autotype] at org.apache.tools.ant.Main.start(Main.java:196)
[autotype] at org.apache.tools.ant.Main.main(Main.java:235)
[autotype] --------------- nested within: ------------------
[autotype] weblogic.xml.schema.binding.BindingException: No default constructor
was found for class weblogic.webservice.context.WebServiceContext loa
ded from file:/C:/bea/weblogic81/server/lib/webservices.jar!/weblogic/webservice/context/WebServiceContext.class.
All classes that will be serialized
or deserialized must be non-interface, non-abstract classes that provide a public
default constructor - with nested exception:
[autotype] [java.lang.NoSuchMethodException: weblogic.webservice.context.WebServiceContext.<init>()]
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ensureValidClass(JavaInspector.java:1051)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.fillDescriptor(JavaInspector.java:174)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.getDescriptor(JavaInspector.java:139)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.createDescriptorForClass(JavaInspector.java:106)
[autotype] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compiler.java:106)
[autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:89)
[autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:102)
[autotype] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.addMapping(TypeMappingBuilderBase.java:180)
[autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.doTypeMapping(Java2SchemaImpl.java:267)
[autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.run(Java2SchemaImpl.java:167)
[autotype] at weblogic.webservice.tools.build.internal.Component2SchemaImpl.run(Component2SchemaImpl.java:151)
[autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.doComponent2Schema(JavaSchema.java:365)
[autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.execute(JavaSchema.java:172)
[autotype] at org.apache.tools.ant.Task.perform(Task.java:317)
[autotype] at org.apache.tools.ant.Target.execute(Target.java:309)
[autotype] at org.apache.tools.ant.Target.performTasks(Target.java:334)
[autotype] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[autotype] at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
[autotype] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[autotype] at org.apache.tools.ant.Main.start(Main.java:196)
[autotype] at org.apache.tools.ant.Main.main(Main.java:235)
BUILD FAILED
file:C:/medrec_tutorial/src/medrecEar/my_webserv.xml:12: weblogic.webservice.tools.build.WSBuildException:
Failed to do type mapping - with nested exc
eption:
[weblogic.xml.schema.binding.BindingException: No default constructor was found
for class weblogic.webservice.context.WebServiceContext loaded from fi
le:/C:/bea/weblogic81/server/lib/webservices.jar!/weblogic/webservice/context/WebServiceContext.class.
All classes that will be serialized or deseria
lized must be non-interface, non-abstract classes that provide a public default
constructor - with nested exception:
[java.lang.NoSuchMethodException: weblogic.webservice.context.WebServiceContext.<init>()]]
Total time: 4 seconds
====================================
The classpath used in Tutorial 11 was the updated one from Tutorial 10. But it
doesn't work. But when I changed the classpath back to the old one, it worked.
Can you explain what is happening? Thank you.
Kelvin Hung

Hey Kelvin. Can you pass along your classpath? Thanks.
"Kelvin Hung" <[email protected]> wrote:
>
According to Chris Wall, tutorial 10 of MedRec needs the following fix:
1.) Add the following jars to your classpath. If these jars do not exist,
compile and create them thru the src/common build script.
C:\medrec_tutorial\build\physicianEar\APP-INF\lib\log4j-1.2.8.jar;
C:\medrec_tutorial\build\physicianEar\APP-INF\lib\value.jar;
C:\medrec_tutorial\build\physicianEar\APP-INF\lib\webServicesEjb_client.jar;
C:\medrec_tutorial\build\physicianEar\APP-INF\lib\utils.jar
2.) EJBGen 2.15 contains the -descriptorDir feature; 8.1 GA contains
EJBGen
2.13beta. Please remove this flag from your cmdline. You will also
need to
manually create the META-INF directory and copy the resultant descriptors
to
this directory.
==============================================
Ok, I did that, and it worked. But when I did tutorial 11 Step 2, it
gave me
this err msg:
C:\medrec_tutorial\src\medrecEar>ant -f my_webserv.xml
Buildfile: my_webserv.xml
build.ws:
[autotype] Autotyping for javaComponents com.bea.medrec.webservices.MedRecWebServices
[autotype] java.lang.NoSuchMethodException: weblogic.webservice.context.WebServiceContext.<init>()
[autotype] at java.lang.Class.getConstructor0(Class.java:1769)
[autotype] at java.lang.Class.getConstructor(Class.java:1002)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ensureValidClass(JavaInspector.java:1049)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.fillDescriptor(JavaInspector.java:174)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.getDescriptor(JavaInspector.java:139)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.createDescriptorForClass(JavaInspector.java:106)
[autotype] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compiler.java:106)
[autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:89)
[autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:102)
[autotype] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.addMapping(TypeMappingBuilderBase.java:180)
[autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.doTypeMapping(Java2SchemaImpl.java:267)
[autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.run(Java2SchemaImpl.java:167)
[autotype] at weblogic.webservice.tools.build.internal.Component2SchemaImpl.run(Component2SchemaImpl.java:151)
[autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.doComponent2Schema(JavaSchema.java:365)
[autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.execute(JavaSchema.java:172)
[autotype] at org.apache.tools.ant.Task.perform(Task.java:317)
[autotype] at org.apache.tools.ant.Target.execute(Target.java:309)
[autotype] at org.apache.tools.ant.Target.performTasks(Target.java:334)
[autotype] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[autotype] at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
[autotype] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[autotype] at org.apache.tools.ant.Main.start(Main.java:196)
[autotype] at org.apache.tools.ant.Main.main(Main.java:235)
[autotype] --------------- nested within: ------------------
[autotype] weblogic.xml.schema.binding.BindingException: No default
constructor
was found for class weblogic.webservice.context.WebServiceContext loa
ded from file:/C:/bea/weblogic81/server/lib/webservices.jar!/weblogic/webservice/context/WebServiceContext.class.
All classes that will be serialized
or deserialized must be non-interface, non-abstract classes that provide
a public
default constructor - with nested exception:
[autotype] [java.lang.NoSuchMethodException: weblogic.webservice.context.WebServiceContext.<init>()]
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.ensureValidClass(JavaInspector.java:1051)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.fillDescriptor(JavaInspector.java:174)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.getDescriptor(JavaInspector.java:139)
[autotype] at weblogic.xml.schema.binding.internal.codegen.JavaInspector.createDescriptorForClass(JavaInspector.java:106)
[autotype] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compiler.java:106)
[autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:89)
[autotype] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.mapClass(XSDTypeMappingBuilder.java:102)
[autotype] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.addMapping(TypeMappingBuilderBase.java:180)
[autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.doTypeMapping(Java2SchemaImpl.java:267)
[autotype] at weblogic.webservice.tools.build.internal.Java2SchemaImpl.run(Java2SchemaImpl.java:167)
[autotype] at weblogic.webservice.tools.build.internal.Component2SchemaImpl.run(Component2SchemaImpl.java:151)
[autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.doComponent2Schema(JavaSchema.java:365)
[autotype] at weblogic.ant.taskdefs.webservices.javaschema.JavaSchema.execute(JavaSchema.java:172)
[autotype] at org.apache.tools.ant.Task.perform(Task.java:317)
[autotype] at org.apache.tools.ant.Target.execute(Target.java:309)
[autotype] at org.apache.tools.ant.Target.performTasks(Target.java:334)
[autotype] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[autotype] at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
[autotype] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[autotype] at org.apache.tools.ant.Main.start(Main.java:196)
[autotype] at org.apache.tools.ant.Main.main(Main.java:235)
BUILD FAILED
file:C:/medrec_tutorial/src/medrecEar/my_webserv.xml:12: weblogic.webservice.tools.build.WSBuildException:
Failed to do type mapping - with nested exc
eption:
[weblogic.xml.schema.binding.BindingException: No default constructor
was found
for class weblogic.webservice.context.WebServiceContext loaded from fi
le:/C:/bea/weblogic81/server/lib/webservices.jar!/weblogic/webservice/context/WebServiceContext.class.
All classes that will be serialized or deseria
lized must be non-interface, non-abstract classes that provide a public
default
constructor - with nested exception:
[java.lang.NoSuchMethodException: weblogic.webservice.context.WebServiceContext.<init>()]]
Total time: 4 seconds
====================================
The classpath used in Tutorial 11 was the updated one from Tutorial 10.
But it
doesn't work. But when I changed the classpath back to the old one,
it worked.
Can you explain what is happening? Thank you.
Kelvin Hung

Why is there no EJB modules generated in chapter 10 of Medrec Tutorial?

Hi,
I am going through the sample Medical Records Development Tutorial.
In Chapter 10,after going through the Procedure 3..I couldn't see any EJB Module being deployed at http://localhost:7101/console/Deployments/EJB Modules
.Any clue what is going wrong??
Thanks in Advance
Natasha

Natasha: Are the EJBs being deployed within an EAR? If so, check under
deployed Applications in the console.
"Natasha" <[email protected]> wrote in message
news:40a908dd$[email protected]..
Hi,
I am going through the sample Medical Records Development Tutorial.
In Chapter 10,after going through the Procedure 3..I couldn't see any EJBModule being deployed at http://localhost:7101/console/Deployments/EJB
Modules
.Any clue what is going wrong??
Thanks in Advance
Natasha

Without adminWebApp.zip,I can't practice the MedRec tutorial 19.

Help me, experts.
Thank you in advance.
Answer me,quickly,ok?

I can't reach the link you gave, which seems not
to exist in the edocs website.
By the way, could you please take a look at the
the message 405. I can't finish that tutorial either,
"Securing Enterprise JavaBean (EJB) Resources Using the Administration Console".
Thanks a lot.
"Jen Hocko" <[email protected]> wrote:
>
"Paul Green" <[email protected]> wrote:
I can't find the "AdminWebApp Web Application" (adminWebApp.zip )
on the dev2dev Web site. Is there any alternative way to do that
or where can I find the file adminWebApp.zip ? Thank you.Hi Paul,
I'm sorry you are having problems with tutorial 18. I have researched
the issue
with the missing adminWebApp.zip file with the dev2dev folks and my records.
I
have discovered that the latest version of tutorial 18 on edocs (http://edocs.bea.com/wls/docs81/medrec_tutorials/ejb_security.html)
no longer makes use of that file. Perhaps your browser is caching an
old version
of this tutorial? Please let me know if a browser refresh does not solve
the problem.
Thanks,
Jen
Sr. Technical Writer
BEA Systems, Inc.

Medrec tutorial, lesson7 compile failed

Hi.
I'm running the medrec turorial and had a couple of issues I managed to solve looking at these pages but I still have one left.
latest compile error is
C:\medrec_tutorial\build\physicianEar\physSessionEjbs\com\bea\medrec\controller\PhysicianSession.java:24: package org.apache.log4j does not exist
[wlcompile] import org.apache.log4j.Logger;
and I can't find any trace of this package though I have weblogic 8.1 and the medrec downloaded from BEA.
Any idea where it should be?

org.apache.log4j.Logger is part of the log4j package.
wlcompile adds jars and classes located in <destination build ear root>/APP-INF/lib and <destination build EAR's root>/APP-INF/classes, respectivity, to the compiler's classpath. Make sure log4j.jar (or similar) is located in the EAR's lib directory.

Medrec tutorial 11 problem

I forgot to mention that I'm using WebLogic Server 8.1 SP1 version.
Thanks

Hey Alex S. Can you post your classpath? Thanks.

Problem with MedRec development tutorial

Hi,
I am facing a problem trying to run the "Tutorial 11: Exposing a Stateless Session
EJB as a Web Service" which is part of the MedRec Development Tutorial for WLS
8.1.
On running the my_webserv.xml (copy of webservices_tutorial.xml) ant script, I
get the following error:
file:D:/medrec_tutorial/src/medrecEar/my_webserv.xml:12: weblogic.webservice.tools.build.WSBuildException:
Failed to do type mapping - with nested exception:
[weblogic.xml.schema.binding.BindingException: Invalid class received: interface
javax.xml.rpc.handler.HandlerRegistry loaded from file:/D:/BEA/weblogic81/server/lib/webservices.jar!/javax/xml/rpc/handler/HandlerRegistry.class.
All classes that will be serialized or deserialized must be non-interface, non-abstract
classes that provide a public default constructor]
Having followed all the previous tutorials exactly as documented, I am not sure
why this is happening.
Looking to get some help for this problem.
thanks.

yes. looks like my CLASSPATH was a problem. some extraneous entries from a previous
medrec tutorial.
thanks.
"Chris Wall" <[email protected]> wrote:
Hey Atul.
What is your classpath?
"atul" <[email protected]> wrote in message
news:403ddd0b$[email protected]..
Hi,
I am facing a problem trying to run the "Tutorial 11: Exposing a StatelessSession
EJB as a Web Service" which is part of the MedRec Development Tutorialfor
WLS
8.1.
On running the my_webserv.xml (copy of webservices_tutorial.xml) antscript, I
get the following error:
file:D:/medrec_tutorial/src/medrecEar/my_webserv.xml:12:weblogic.webservice.tools.build.WSBuildException:
Failed to do type mapping - with nested exception:
[weblogic.xml.schema.binding.BindingException: Invalid class received:
interface>> javax.xml.rpc.handler.HandlerRegistry loaded from>file:/D:/BEA/weblogic81/server/lib/webservices.jar!/javax/xml/rpc/handler/HandlerRegistry.class.>> All classes that will be serialized or deserialized must be>non-interface, non-abstract>> classes that provide a public default constructor
Having followed all the previous tutorials exactly as documented, Iam not
sure
why this is happening.
Looking to get some help for this problem.
thanks.

Problem with JSTL 1.0.6 in WLS 8.1.4 - Please Help

I am trying to use JSTL 1.0.6 in WLS 8.1.4. Here are the steps I followed:
 
 Step 1:
 Copied the following jar files to WEB-INF/lib directory: 
 - jaxen-full.jar 
 - jdbc2_0-stdext.jar 
 - jstl.jar 
 - saxpath.jar 
 - standard.jar 
 - xalan.jar 
 - xercesImpl.jar 
 - xml-apis.jar 
 
 Step 2:
 Imported JSTL into my one-and-only JSP page as follows: 
 <%@ page contentType="text/html;charset=UTF-8" language="java" %>
 <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
 <%@ taglib prefix="c_rt" uri="http://java.sun.com/jstl/core_rt" %>
 <%@ taglib prefix="x" uri="http://java.sun.com/jstl/xml"%>
 <%@ taglib prefix="x_rt" uri="http://java.sun.com/jstl/xml_rt" %>
 <%@ taglib prefix="fmt" uri="http://java.sun.com/jstl/fmt" %>
 <%@ taglib prefix="fmt_rt" uri="http://java.sun.com/jstl/fmt_rt" %>
 <%@ taglib prefix="sql" uri="http://java.sun.com/jstl/sql" %>
 <%@ taglib prefix="sql_rt" uri="http://java.sun.com/jstl/sql_rt" %>
 <%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
 <%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
 
 
 (I am also using struts, hence the last two page directives)
 
 
 Step 3:
 Finally I tried to build an EAR (which used to build OK before I added JSTL) using a slightly modified version of the build.xml that comes with the Medrec tutorial. wlcompile went OK, but wlappc failed with the following message:
 
 java.lang.NoClassDefFoundError: javax/servlet/jsp/el/VariableResolver
 
 
 What am I doing wrong? I followed the instructions given in the JSTL 1.0.6 package. Is wlappc not the right tool for translating/compiling the JSP?
 
 Please help!
 
 
 Regards,
 Nadeem

I can't be sure about exactly what's happening here, but I can point out several things.
 The class "javax.servlet.jsp.el.VariableResolver" is associated with JSTL 1.1.x, and JSP 2.0. It's not part of JSTL 1.0.x. Make sure you really have version 1.0.6, and don't have 1.1 somewhere.
 If you're just trying to use the JSTL, you shouldn't need several of those jars that you're presently including. You only need jstl.jar and standard.jar.
 Why are you using the "rt" versions of these taglibs? Those don't even use the expression language. I would remove "_rt" from all of those references.
 Note that if you're using Struts and the JSTL, you probably want to use Struts-EL, which is a version of the Struts jar that uses the EL to evaluate attribute values. Check the struts-user archive for some information about this. You'll find the struts-el distribution in the "contrib" directory of the Struts distribution.

Calling a webservices method, paramaters are not pass correctly

Hi, I would like a Eclipse's MedRec tutorial...All project build, compil, deploy correctly.
When I invoke the "public PatientWS findPatientBySsn(String pId): ---> parameter "888888888" " Webservice's method from the WBL8.1 amin console, all is working correctly: it response me Patient[Id: 105 |...
But the same thing, call from the PhysicianWebApp, the webservices paramter invocation is NULL? I don't understan why!
standalone trace fromm admin console:
**********************************************************15:17:57,102 MedRecWebServicesEJB INFO executeThread:
'14' for queue
: 'weblogic.kernel.Default' - Finding patient by ssn.
03/01/2006 15:17:57,112 MedRecWebServicesEJB DEBUG ExecuteThread: '14' for queue
: 'weblogic.kernel.Default' - SSN: 888888888
paramater invocation trace from PhysicianWebApp
03/01/2006 15:23:02,040 MedRecWebServicesEJB DEBUG ExecuteThread: '14' for queue
: 'weblogic.kernel.Default' - SSN: null
03/01/2006 15:23:02,040 PatientSessionEJB DEBUG ExecuteThread: '14' for queue: '
weblogic.kernel.Default' - SSN: null
Thank

I find the solution, it was webServicesEjb_client.jar file problem. I use in the physicianEar.ear the jar providing from the tutorial!
When I generate my own webServicesEjb_client.jar and place it in the ear, it's all right!
For generate this librairie look at:
-->Tutorial 12-Procedure 1-step3
Personnal I add to my ant build.xml script:
<target name="build.ws.client">
 <clientgen
 wsdl="http://localhost:7101/ws_medrec/MedRecWebServices?WSDL"
 packageName="com.bea.medrec.webservices"
 keepGenerated="true"
 clientjar="./deploy/webServicesEjb_client.jar" />
 </target>
Thank a lot Stef-Ã¢ne

Wldeploy dosent work as expected in 11.1.2 as it works in 11.1.1.1.5

I have the exactly same problem as described in this thread Error running Weblogic.Deployer in medrec tutorial (wl9.1)
But my old jdev version (11.1.1.1.5) where things works fine and I am migrating to new jdev version (11.1.2) during wldeploy
C:\Oracle\Middleware1112\jdeveloper\jdev\bin>
C:\Oracle\Middleware1112\jdk160_24\bin\javaw.exe -client -Dosgi.clean=true -XX:MaxPermSize=256M -Xbootclasspath/p:../lib/lwawt.jar -Xbootclasspath/p:../lib/apt-expose.jar -Dsun.awt.keepWorkingSetOnMinimize=true -XX:+HeapDumpOnOutOfMemoryError -Doracle.jdeveloper.webservice.showAllOwsmPolicyTypes=false -Doracle.jdeveloper.webservice.hidePropertyOverride=false -Dsun.awt.disablegrab=true -Xbootclasspath/p:../../rdbms/jlib/ojdi.jar -Dide.patches.dir=jdev/lib/patches -Dnetbeans.home=../../netbeans/platform/ -Dnetbeans.logger.console=true -Dexcluded.modules=org.eclipse.osgi -Dide.cluster.dirs=../../netbeans/netbinox/:../../netbeans/bridge/:../../ -Xmx800M -Xms128M -Xverify:none -Doracle.ide.extension.HooksProcessingMode=LAZY -Dorg.eclipse.equinox.simpleconfigurator.configUrl=file:bundles.info -Dosgi.bundles=file:../ide/lib/oracle.ide.osgi.jar@3:start -Dosgi.bundles.defaultStartLevel=1 -Dosgi.configuration.cascaded=false -Dosgi.noShutdown=true -Dorg.osgi.framework.bootdelegation=* -Dosgi.parentClassloader=app -Xbootclasspath/p:../../rdbms/jlib/ojdi.jar -Dosgi.classloader.singleThreadLoads=true -Dosgi.bundlefile.limit=2000 -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n-collation.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n-mapping.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n-servlet.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n-utility.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.xdk_11.1.0/xmlparserv2.jar -Djavax.xml.parsers.DocumentBuilderFactory=oracle.xml.jaxp.JXDocumentBuilderFactory -Djavax.xml.parsers.SAXParserFactory=oracle.xml.jaxp.JXSAXParserFactory -Dorg.xml.sax.driver=oracle.xml.parser.v2.SAXParser -Dide.feedback-server=ide.us.oracle.com -Xbootclasspath/a:../../ide/lib/xml-factory.jar -Djavax.xml.transform.TransformerFactory=oracle.ide.xml.SwitchableTransformerFactory -Dsun.java2d.noddraw=true -Dide.conf=C:\Oracle\Middleware1112\jdeveloper\jdev\bin\jdev.conf -Dide.startingcwd=C:\Oracle\Middleware1112\jdeveloper\jdev\bin "-Dide.user.dir=C:\Documents and Settings\pakrish.APPLICATIONS\Application Data\JDeveloper\system11.1.2.0.38.60.17\o.jdeveloper.extensiondt.core\EDTplatform-dt_jdev-UserAndPrefDir" -Dedt.hot.classes=D:\tmp\jdev1112\SAIExtn_1App\TestAntInvoke\classes -Dedt.hot.manifest=D:\tmp\jdev1112\SAIExtn_1App\TestAntInvoke\src\META-INF\extension.xml -Dedt.hot.deploydir=jdev/extensions/ -Dedt.extension.id=yourcompany.testantinvoke -agentlib:jdwp=transport=dt_socket,server=y,address=1589 -Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true -classpath C:\Oracle\Middleware1112\jdeveloper\ide\lib\ide-boot.jar;C:\Oracle\Middleware1112\jdeveloper\netbeans\platform\lib\boot.jar;C:\Oracle\Middleware1112\jdeveloper\netbeans\platform\lib\org-openide-util.jar;C:\Oracle\Middleware1112\jdeveloper\netbeans\platform\lib\org-openide-util-lookup.jar;C:\Oracle\Middleware1112\jdeveloper\netbeans\platform\lib\org-openide-modules.jar;C:\Oracle\Middleware1112\jdeveloper\ide\lib\fcpboot.jar -Djavax.net.ssl.trustStore=C:\DOCUME~1\PAKRIS~1.APP\LOCALS~1\Temp\trustStore5123141337500065063.jks -Dhttp.proxyHost=www-proxy.us.oracle.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|localhost.localdomain|127.0.0.1|::1|10.177.10.174| -Dhttps.proxyHost=www-proxy.us.oracle.com -Dhttps.proxyPort=80 -Xbootclasspath/a:C:\Oracle\Middleware1112\jdk160_24\lib\tools.jar;C:\Oracle\Middleware1112\jdk160_24\lib\dt.jar oracle.ide.osgi.boot.JDeveloper
Listening for transport dt_socket at address: 1589
Debugger connected to local process.
Source breakpoint: InvokeAnt.java:35
Source breakpoint: InvokeAnt.java:63
Warning: Reference lib.path has not been set at runtime, but was found during
build file parsing, attempting to resolve. Future versions of Ant may support
referencing ids defined in non-executed targets.
deploy:
weblogic.Deployer -debug -nostage -verbose -upload -noexit -name globalweather -source C:\JDeveloper\mywork\SFE\outbound\globalweather\1.0.0.0.0\deploy\globalweather.ear -targets DefaultServer -adminurl t3://localhost:7101 -user weblogic -password ******** -deploy
weblogic.Deployer invoked with options: -debug -nostage -verbose -upload -noexit -name globalweather -source C:\JDeveloper\mywork\SFE\outbound\globalweather\1.0.0.0.0\deploy\globalweather.ear -targets DefaultServer -adminurl t3://localhost:7101 -user weblogic -deploy
[WebLogicDeploymentManagerImpl.<init>():115] : Constructing DeploymentManager for J2EE version V1_4 deployments
[WebLogicDeploymentManagerImpl.getNewConnection():158] : Connecting to admin server at localhost:7101, as user weblogic
[ServerConnectionImpl.getEnvironment():286] : setting environment
[ServerConnectionImpl.getEnvironment():289] : getting context using t3://localhost:7101
[ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7101/jndi/weblogic.management.mbeanservers.domainruntime
java.io.IOException
 at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
 at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
 at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
 at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
 at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:238)
weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://localhost:7101': Bootstrap to localhost/127.0.0.1:7101 failed. It is likely that the remote side declared peer gone on this JVM. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.

Retrieving Information about WebLogic Server:
Run
1. <WLHOME>/server/bin/setWLSEnv
2. java weblogic.Admin -adminurl t3://127.0.0.1:7001 -username weblogic -password weblogic1 PING 3 100
In case of exception smth like "Caused By: java.net.UnknownHostException: localhost"
add mappings of IP address to host name
127.0.0.1 localhost
For windows:
C:\Windows\System32\drivers\etc\hosts
Edited by: user6372268 on Dec 20, 2012 1:53 AM

EJB application configuration

Hi all,
would like to get your opinion about following problem:
Let's assume we have some EJB based application. This application has some external configuration file. In your opinion what's the best way to access to that file? What technologies should be used in that case?
Thank you!

If your using 7.0, I would suggest putting this "startup functionality" into
a webapp.
1. create an EAR
2. put ejb in ear
3. create webapp put in ear make this load first by ordering it in the EAR's
applicaiton.xml prior to the EJB
4. the webapp has one servlet that loads on startup and in its init method
does the "setup/configuration needs".
See 8.1 Medrec Tutorial's startupEAR
http://e-docs.bea.com/wls/docs81/medrec_tutorials/projectdir.html
Attaching src and .ear file for perusal.
Cheers
mbg
"MS" <[email protected]> wrote in message news:3e7101a2$[email protected]..
>
Hello,
Our EJB application requires some setup/configuration to be done at WLSstartup.
Right now, we have used the WLS Startup class for achieving thisfunctionality.
Is there a better way using MBean or using a custom application that canalso
be deployed/undeployed so that changes can be immediately reflected ratherthan
only after server restart.
Pl send in your comments/suggestions.
rgds
MS
[startupEar.ear]
[startupEar_src.zip]

Admin console extension sample

I've been trying to create a simple admin extension against WLS 10.0. I believe I've followed the proper procedure by creating a myextension.jar file and placing it into the console-ext of the domain root directory. In this jar file, I have a WEB-INF/netuix_extension.xml file that tries to place a portlet on the "page" parent. The portlet is nothing special and just has a "hello world" jsp page. I have placed the files in the directories as recommended by WLS documentation and created the jar file. However, the extension has no effect. There are no console errors to be found in either output or logs and am hoping to find some help.
Are there some extra debug flags I can turn on to see if it's being loaded, i.e. is there any config setting I can enable to provide more insight into finding the problem?
I've looked, but have been unable to find a working bare bones example like this. Does anyone know where I can find one for WLS 10.0
Here are the contents of the files I used to generate the extension:
The netuix_extension.xml look like:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-portal-extension
xmlns="http://www.bea.com/servers/portal/weblogic-portal/8.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/servers/portal/weblogic-portal/8.0 netuix-extension-1_0_0.xsd">
<provider-info>
<title>My Console Extension</title>
<version>1.0</version>
<description>My Console Extension</description>
<author>Oracle Inc.</author>
<last-modified>08/18/2008</last-modified>
<support-url>http://www.bea.com</support-url>
</provider-info>
<portal-file>/console.portal</portal-file>

<page-extension>
<page-location>
<parent-label-location label="page"/>
<page-insertion-point
layout-location="1"
placeholder-position="0"/>
</page-location>
<portlet-content
content-uri="/portlets/myext.portlet"
title="My Console Extension"
orientation="top"
instance-label="MyExtLabel"/>
</page-extension>
</weblogic-portal-extension>
The /portlets/myext.portlet page is:
<?xml version="1.0" encoding="UTF-8"?>
<portal:root xmlns:html="http://www.w3.org/1999/xhtml-netuix-modified/1.0.0"
xmlns:portal="http://www.bea.com/servers/netuix/xsd/portal/support/1.0.0"
xmlns:netuix="http://www.bea.com/servers/netuix/xsd/controls/netuix/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/servers/netuix/xsd/portal/
support/1.0.0 portal-support-1_0_0.xsd">
<netuix:portlet definitionLabel="MyAdminPortlet" title="wwMyAdminPortlet">
<netuix:content>
<netuix:jspContent contentUri="/ext_jsp/myext.jsp"/>
</netuix:content>
</netuix:portlet>
</portal:root>
the jsp page is:
<html>
<head>
<title>Sample Application JSP Page</title>
</head>
<body>
Sample Application JSP Page
<%= new String("Hello!") %>
</body>
</html>
Thanks

I have successfully installed this sample on a domain configured with the MedRec tutorial, but failed on a newly created domain. Again there were no errors reported in the console or log. How does one get more debug information?

Medrec tutorial 10

Similar Messages

Maybe you are looking for