Overwritting ejb classes

Hi all,
I am using xerces1.4 with j2ee, but in j2ee there is inbuild xerces2.5 so that i can't use the my old code for validation of xml with xsd.
So plz tell me how to overwrite javax.DocumentBuilder class other wise how to change the sequence of loading jar file in j2ee

If you are using an application server, put the newer version of xerces.jar file in front of its classpath. In WebLogic, there is a pre-classpath variable. If the newer version of the jar file is put here, then your problem should go away.

Similar Messages

Fundamental question: Integrating non-EJB classes

Hi there,
sorry to ask that, but how can i integrate classes other than EJBs
into my assembled application ? i use sun's deploytool and their ri
application server.
my task is to call a class called J2EEManager at the app server
startup, which has to initialize some server-wide data. but how do
i call and integrate this class at deployment level ? in the deploytool
there isn't such a support. i do also use this class during runtime.
also i do not see how to integrate my helper classes that are needed
by the EJBs i developed. again, in deploytool i just can add my EJB's
but not all the other classes i implemented.
how does this work ? any hints, links, tutorials ? the examples i've
seen in books and articles mostly do not cover these things...
thank you very much. best regards
rivella50

When you call the "packager" tool, you can specify any classes you want to include in the package archives. They don't all have to be EJB classes or interfaces. I don't use the deploytool UI, but there should be a way to include extra files into the packages from within the UI mode.
As for performing extra functionality at server startup, I don't know of any way to do this. However you can create a separate (stand-alone) application that is run on the server machine, just after server startup:
j2ee &... wait until server is up and running ...
java J2EEManager <params>Ben

MBean calling ejb class loading issue

Hi,
I would like to have an mbean call an ejb. I have come against a (predictable!!)
class loading problem. The EJB Home cant be bundled with the mbean because the
mbean class loader would load the interface, preventing ejb reload( Thats what
the error msg indicates) and the ejb doesnt get deployed.
I have moved to an mlet based scheme (beacuse an mlet is a class loader) to
load the mbeans, but now I have the problem that when the mbean looks up the
home in jndi the cast fails ie the jndi object has an interface class loaded by
the ejb class loader but the mlet has its own loaded home interface. These class
loaders appear to be sibblings - but I havnt printed out the trees.
This is WLS 702 which seems to be JMX 1.1. Has anyone got a way around this?
Have I invented a problem that doesnt exist? I cant go to WLS8.
My current way forward is to have the mbean find the class loader that loaded
the interface class (jndi object) and then have the mbean use that class loader
to load its copy of the interface class. Seems a bit complex. Im sure I missed
something obvious.
Thanks
Pete Marshall

Pete,
could you explain better your thoughts...
I'm interested to hear them.
regards,
Pedro Salazar.
Pete Marshall wrote:
Must think before typing..
If I have the ejb register a listener on the mbean and have the mbean emit an
event the detyped notification from the mbean will break the link between the
mbean class loader and the ejb loader. I think ;-) Ill try it.
Pete
"Pete Marshall" <[email protected]> wrote:
Hi,
I would like to have an mbean call an ejb. I have come against a (predictable!!)
class loading problem. The EJB Home cant be bundled with the mbean because
the
mbean class loader would load the interface, preventing ejb reload( Thats
what
the error msg indicates) and the ejb doesnt get deployed.
I have moved to an mlet based scheme (beacuse an mlet is a class loader)
to
load the mbeans, but now I have the problem that when the mbean looks
up the
home in jndi the cast fails ie the jndi object has an interface class
loaded by
the ejb class loader but the mlet has its own loaded home interface.
These class
loaders appear to be sibblings - but I havnt printed out the trees.
This is WLS 702 which seems to be JMX 1.1. Has anyone got a way around
this?
Have I invented a problem that doesnt exist? I cant go to WLS8.
My current way forward is to have the mbean find the class loader that
loaded
the interface class (jndi object) and then have the mbean use that class
loader
to load its copy of the interface class. Seems a bit complex. Im sure
I missed
something obvious.
Thanks
Pete Marshall

JDeveloper EJB Class Editor lock

I created an EJB using JDev and used the EJB class editor to build the fields/methods in the bean.
After working on the EJB for quite a while I reopened the EJB Class editor and found a blue error at the bottom of the window stating :
Editor locked : file is read only.
I have tried almost everything to unlock the editor but I have had no success.None of the files in project is read-only.
If you have experinced this problem please respond!
Regards
LeRoux

Hi,
Go to se38.
In the menubar..
Goto-->attributes.
In that u can see on the bottom of the popup, a check box with editor lock.
U check that box.
Then the program cannot be edited by any other user other than the one who has created.
In this case the username has to be unique.
If one user is used by many number of people, then all the people who are using that user can edit the program.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Can't access non ejb classes from JSP - NoClassDefFound error

          Hi,
          I have one session ejb which has a method returning a collection of non ejb class objects (say of Class 'Foo').
          The method signature is like :
          "Collection getFinacialData() throws RemoteException"
          It is working fine with normal java clients. Now when I run this from a JSP it gives a "NoClassDefFoundError". I kept class 'Foo' and the remote interface of the session bean in the same package and also in the same ejb jar file. Also I am running JSP and ejb in same WL server(ver 5.1, SP8 on solaris). What I have done is only deployed the bean jar file. Do I need to do anything more?
          thanks in advance.


I ran into a similar problem. I solved it by putting the client classes for
          accessing my EJB in the WebLogic POST_CLASSPATH in the startWebLogic script
          file:
          set POST_CLASSPATH=d:\weblogic\myserver\myClient.jar
          For more information on class visibility between the JSP and EJB class
          loaders, check out
          http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_deployover.html#1056256
          Rick
          "niroja" <[email protected]> wrote in message
          news:3a6ed903$[email protected]..
          >
          > Hi,
          >
          > I have one session ejb which has a method returning a collection of non
          ejb class objects (say of Class 'Foo').
          > The method signature is like :
          > "Collection getFinacialData() throws RemoteException"
          > It is working fine with normal java clients. Now when I run this from a
          JSP it gives a "NoClassDefFoundError". I kept class 'Foo' and the remote
          interface of the session bean in the same package and also in the same ejb
          jar file. Also I am running JSP and ejb in same WL server(ver 5.1, SP8 on
          solaris). What I have done is only deployed the bean jar file. Do I need to
          do anything more?
          >
          > thanks in advance.
          >

Locating EJB classes from JSP

Hi all,
I have some JSP that invoke Session Beans. My question is:
what is the right place to put EJB classes in order to be found by JSP ?
I have found the following solutions but they both slow down during development
phase:
1) Build an EAR and let the JSP reference EJB classes via the Class-Path attribute.
This is nice but a bit complex: I'd like to use EAR only for shipment phase and
not for every small change to the Bean.
2) Let WLS see the classes including them in the classpath at startup. But this
has the disadvantage that I have to restart WLS every time because - I suppose-
WLS isn't able to unload classes if I include them in the CLASSPATH
So what do you suggest me for development phase? is there a faster solution?
Thanks a lot
F.Marchioni

Hi Arjuna,
put it on the weblogic startup classpath.mmmmm well I think the JSP will not reload the EJB classes when I make a change
if they are on the classpath...unless I restart the server....I'll try again...I
hope I'm wrong...
thanks
Francesco
"Arjuna Chala" <[email protected]> wrote:
for testing
- put it on the weblogic startup classpath.
- use the console's hot deploy facility to re-deploy the ejb after changes.
This works well for me (WLS6.1).
Reagrds
Arjuna Chala
"Marchioni F." <[email protected]> wrote in message
news:3c5eae94$[email protected]..
Hi all,
I have some JSP that invoke Session Beans. My question is:
what is the right place to put EJB classes in order to be found byJSP ?
I have found the following solutions but they both slow down duringdevelopment
phase:
1) Build an EAR and let the JSP reference EJB classes via the Class-Pathattribute.
This is nice but a bit complex: I'd like to use EAR only for shipmentphase and
not for every small change to the Bean.
2) Let WLS see the classes including them in the classpath at startup.But
this
has the disadvantage that I have to restart WLS every time because- I
suppose-
WLS isn't able to unload classes if I include them in the CLASSPATH
So what do you suggest me for development phase? is there a fastersolution?
Thanks a lot
F.Marchioni

Re: MBean calling ejb class loading issue

Must think before typing..
If I have the ejb register a listener on the mbean and have the mbean emit an
event the detyped notification from the mbean will break the link between the
mbean class loader and the ejb loader. I think ;-) Ill try it.
Pete
"Pete Marshall" <[email protected]> wrote:
>
Hi,
I would like to have an mbean call an ejb. I have come against a (predictable!!)
class loading problem. The EJB Home cant be bundled with the mbean because
the
mbean class loader would load the interface, preventing ejb reload( Thats
what
the error msg indicates) and the ejb doesnt get deployed.
I have moved to an mlet based scheme (beacuse an mlet is a class loader)
to
load the mbeans, but now I have the problem that when the mbean looks
up the
home in jndi the cast fails ie the jndi object has an interface class
loaded by
the ejb class loader but the mlet has its own loaded home interface.
These class
loaders appear to be sibblings - but I havnt printed out the trees.
This is WLS 702 which seems to be JMX 1.1. Has anyone got a way around
this?
Have I invented a problem that doesnt exist? I cant go to WLS8.
My current way forward is to have the mbean find the class loader that
loaded
the interface class (jndi object) and then have the mbean use that class
loader
to load its copy of the interface class. Seems a bit complex. Im sure
I missed
something obvious.
Thanks
Pete Marshall

Pete,
could you explain better your thoughts...
I'm interested to hear them.
regards,
Pedro Salazar.
Pete Marshall wrote:
Must think before typing..
If I have the ejb register a listener on the mbean and have the mbean emit an
event the detyped notification from the mbean will break the link between the
mbean class loader and the ejb loader. I think ;-) Ill try it.
Pete
"Pete Marshall" <[email protected]> wrote:
Hi,
I would like to have an mbean call an ejb. I have come against a (predictable!!)
class loading problem. The EJB Home cant be bundled with the mbean because
the
mbean class loader would load the interface, preventing ejb reload( Thats
what
the error msg indicates) and the ejb doesnt get deployed.
I have moved to an mlet based scheme (beacuse an mlet is a class loader)
to
load the mbeans, but now I have the problem that when the mbean looks
up the
home in jndi the cast fails ie the jndi object has an interface class
loaded by
the ejb class loader but the mlet has its own loaded home interface.
These class
loaders appear to be sibblings - but I havnt printed out the trees.
This is WLS 702 which seems to be JMX 1.1. Has anyone got a way around
this?
Have I invented a problem that doesnt exist? I cant go to WLS8.
My current way forward is to have the mbean find the class loader that
loaded
the interface class (jndi object) and then have the mbean use that class
loader
to load its copy of the interface class. Seems a bit complex. Im sure
I missed
something obvious.
Thanks
Pete Marshall

Problem with Embedded OC4J - Can find EJB class???

I am getting the following error when starting my application within JDeveloper.
05/06/22 16:11:35 Error instantiating application 'current-workspace-app' at file:/C:/developc/developc-oc4j-app.xml: Error initializing ejb-module; Exception Error loading class 'com.syncra.ct.server.AggregatesManagerBean': java.lang.ExceptionInInitializerError: java.lang.NullPointerException
It never reaches breakpoints in the class. So, I assume that it can't find the class in the classpath. But, when I look at the developc-oc4j-app.xml file see the following:
<ejb-module path="file:/C:/developc/Model/classes/"/>
<web-module id="developc-ViewController-webapp" path="C:\developc\ViewController\public_html"/>
and the ejb class is in the correct spot. Any help would be greatly appreciated. I am on JDeveloper 10.1.2.
Thanks.

I put a static method in the class to print out when it is loaded. And the class exists in the classpath. It is never making it to the class.
Also, I do have both the JAVA_HOME and ORACLE_HOME environment variables set.
The ejb definitions are:
ejb-jar.xml
<session>
<ejb-name>ct.AggregatesManagerHome</ejb-name>
<home>com.syncra.ct.server.api.AggregatesManagerHome</home>
<remote>com.syncra.ct.server.api.AggregatesManager</remote>
<ejb-class>com.syncra.ct.server.AggregatesManagerBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
orion-ejb-jar.xml
<session-deployment name="ct.AggregatesManagerHome" location="ct.AggregatesManagerHome"/>
Because JDeveloper forces me to split the code into Model and ViewController I am wondering if there is something special that needs to be done for OC4J to see everything. Any ideas?
Nick

Deployement of ejb class in xi server

hi all
i have to deploy my ejb class on xi server.can anybody tell me what will be the procedure

try this
/people/alessandro.guarneri/blog/2006/10/13/get-rid-of-recordset-node
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bc7f08e1-0901-0010-b1bd-80966009d8f0
http://help.sap.com/saphelp_nw2004s/helpdata/en/40/00be09879f114aa1ec46c2afa4445b/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9221b490-0201-0010-0e90-8cc75cde876c
http://help.sap.com/saphelp_webas630/helpdata/en/cb/f4bc3d42f46c33e10000000a11405a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/eaeb475d-0c01-0010-f5a4-d7a8eb185793
Thanks

Problem with Dynamically accessing EJB Class objects in WL 7.0 SP1

I am trying to build a component which has the ability to instantiate and execute
an known EJB method on the fly.
I have managed to build the component but when I try and execute it I get a ClassNotFoundException.
I know that the EJB I am trying to invoke is deployed and available on the server,
as I can see it in the console, I also seen to have been able to get the remote
interface of the object, my problem occurs when I try and access the class object
so I can perform a create on the object and then execute my method
The code I have written is below:
private Object getRemoteObject(Context pCtx, String pJNDIName, String pHomeBean)
throws Exception {
     String homeCreate = "create";
     Class []homeCreateParam = { };
     Object []homeCreateParamValues = {};
try {
//This call seems to work and doesn't throw an exception
Object home = pCtx.lookup(pJNDIName);
//However this call throws a java.lang.ClassNotFoundException
Class homeBean = Class.forName(pHomeBean);
Method homeCreateMethod = homeBean.getMethod(homeCreate,homeCreateParam);
return homeCreateMethod.invoke(home, homeCreateParamValues);
} catch (NamingException ne) {
logStandardErrorMessage("The client was unable to lookup the EJBHome.
Please make sure ");
logStandardErrorMessage("that you have deployed the ejb with the JNDI
name "+pJNDIName+" on the WebLogic server ");
throw ne;
} catch (Exception e) {
logStandardErrorMessage(e.toString());
throw e;
Any advice would be really appreciated, I'm fast running out of ideas, I suspect
it has something to do with the class loader but I'm not sure how to resolve it
Regards
Jo Corless

Hello Joanne,
Congratulations! I'm very happy that you've managed to fix your problem. It's
always essential to understand how to package applications when deploying on BEA
WebLogic. Usually, by throwing everything into an EAR file solves just about all
the class loader problems. :-) Let us know if you have any further problems that
we can assist you with.
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
"Joanne Corless" <[email protected]> wrote:
>
>
I've fixed it!!!!!!!!
Thanks to everyone who gave me help!!!!
The class loader was the culprit which is what I suspected all along.
As soon
as I put the 2 jar files I was using into an EAR file the problem went
away!!!!!
Thanks again
Jo Corless
"Ryan LeCompte" <[email protected]> wrote:
Hello Joanne,
As Mr. Woollen mentioned, I also believe it's a problem with the class
loader.
You need to be careful how you arrange your EJBs, because WebLogic has
a specific
method in which it loads classes in an EAR, JAR, and WAR file(s). Please
refer
to http://dev2dev.bea.com/articles/musser.jsp for more information about
BEA WebLogic
class loading mechanisms and caveats. Also, try printing out the various
methods
that are available on the object that was returned to you via reflection.
For
example, use the getMethods() method, which returns an array of Method
objects
that you can subsequently cycle through and print out the various method
names.
This way you can discover if the class found/returned to you is indeed
the one
you intend to locate.
Hope this helps,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
Rob Woollen <[email protected]> wrote:
I believe the issue is the home interface class for this EJB is not
available in the class loader which is doing the reflection.
If you do:
getClass().getClassLoader().loadClass(homeInterfaceClassName)
I suspect it will fail. Reflection still requires that the class be
loadable.
-- Rob
Joanne Corless wrote:
Hi Slava,
If I make my code look like you describe below I get a compliationerror telling
me that
home.getMethod() is not recognised (no such method)
If I change it slightly and use
Method homeCreateMethod =
home.getClass().getMethod(homeCreate,homeCreateParam);
The code will compile OK but when executed it still throws a NoSuchMethodException
Any ideas ?
Thanks for your help so far
Regards
Jo Corless
Your code should look like
Object home = pCtx.lookup(pJNDIName);
Method homeCreateMethod =
home.getMethod(homeCreate,homeCreateParam);
return homeCreateMethod.invoke(home, homeCreateParamValues);
Regards,
Slava Imeshev
"Joanne Corless" <[email protected]> wrote in message
news:[email protected]...
Hi Ryan,
I also wanted to mention that if you do a "header search" in this
particular
newsgroup
with the search query as "reflection", you will see many previousmessages
regarding
reflection and EJBs. I believe you could learn a lot from thedifficulties
that
others have faced and solved.I tried that and although there was a number of similar cases noneof them
actually
seem to fix my issue. Thanks for the suggestion though
Are the EJBs that you are trying to access accessible via your
system
classpath?
Try to avoid having them accessible via the main system classpath,and
only bundle
them in your appropriate EJB jar files (contained in an EAR file,for
example).Maybe I should have laid the problem out a little clearer.
I have a number of EJB's bundled up in a JAR file which is hot deployedto
the
server. Within this first JAR file is an EJB (SSB) component that
needs
to
be
able to invoke a known method on another EJB. This second EJB may
or
may
not be
within the first JAR file but it also will be hot deployed.
The component trying to invoke the method on the 2nd EJB has to
be
able to
create
an instance of the 2nd EJB without actually knowing anything bar
a
JNDI
Name which
is passed in at runtime.
I can get as far as doing the
Object home = pCtx.lookup(pJNDIName);
This returned a class with the name
"com.csc.edc.projects.allders.httppostoffice.postman.PostmanBean_mp8qy2_Home
Impl_WLStub"
My problem seems to occur when I try and invoke the create method
Method homeCreate = home.getClass().getMethod("create", new Class[0]);
My code throws a java.lang.NoSuchMethodException at this point so
I
am
unable
to progress to the next step of :
Object bean = homeCreate.invoke(home, null);
So I can return the instantiated bean back to the calling client.
Why am I getting the NoSuchMethodException, is is because I am gettinga
stub
back rather than the home interface and if so how do I get the truehome
interface
from the bean
Thanks in advance
Jo Corless

Apparent EJB Class Loader Issue

I am having a problem loading narrowing an EJB. It appears to be a class loader
problem. I am getting a ClassCastException with the following message: Cannot
narrow remote object to com.dte.ejb.facade.AccessoryServiceHome.
Here is my code that looks up the EJB (I've ommitted the 'catch' clauses):
EJBHome ejbHome = (EJBHome) cache.get(homeClass);
try {
Object temp = ctx.lookup("ejb/" + homeClass.getName());
if (ejbHome == null) {
ejbHome = (EJBHome) PortableRemoteObject.narrow(temp, homeClass);
cache.put(homeClass, ejbHome);
Here is the output of some debugging information from the above method. Here I've
displayed the class.getName and the class.getClassLoader for the Class object
passed to this method and the remote object being cast by the narrow method:
homeClass : com.dte.ejb.facade.AccessoryServiceHome
homeClass : weblogic.utils.classloaders.ChangeAwareClassLoader@29164c finder:
weblogic.utils.classloaders.MultiClassFinder@300ec4
From Lookup: com.dte.ejb.facade.AccessoryServiceBean_krx5el_HomeImpl
From Lookup: weblogic.utils.classloaders.GenericClassLoader@1ea02f finder: weblogic.utils.classloaders.MultiClassFinder@6fca08
As you can see, the Class passed into this method has been loaded with the ChangeAwareClassLoader
but the HomeImpl class was loaded with the GenericClassLoader. I think that is
the problem (please correct me if I am wrong).
The application in question is an .ear with 2 .war modules and a ejb.jar file.
It was my understanding that all classes needed by any module in a .ear were all
loaded with the same class loader. Is this true? If so, then why am I having this
problem?
Thank you in advance for your help.

I just want to add few comments hoping the iPlanet engineer will be able to help me.
I mange to get one deployment of a war file with the client weblogic EJB to work; only if I add the Installation Directory path of the war file plus “web-inf/classes” to the classpath of the JVM configuration.
This tells me that the class loader looks for the JVM classpath to load the EJB home class at run time. I think; if I can make iPlanet class loader to look for the application classpath instead of the JVM my problem will go away.
Thank you in advance,
Nad

Why wlappc ANT task forces aways the generation of the EJB classes ?

I've got a problem with the ANT task "wlappc" witch interfaces Weblogic compilator.
In fact, I would like to execute the ebj compilation only when needed (if the deployment descriptor or a class changed for example).
It seems that this is the default behavior and the 'forcegeneration' option of the wlappc Ant task can change it (the doc is below).
forceGeneration :
Forces generation of EJB and JSP classes. Without this flag, the classes will not be regenerated unless a checksum indicates that it is necessary.
So I wrote :
<wlappc source="${descriptors}/CommandeEntities" output="${build}/CommandsEntities.jar" keepgenerated="true" verbose="true" forcegeneration="false">
<classpath refid="ejb.classpath"/>
</wlappc>
but I got the folowing result :
ejbjar:
[wlappc] Warning, output location exists H:\devWv2\wv2\build\CommandesEntities.jar
[wlappc] Created working directory: C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [VersionHelper] Recompiling because no previous hashes found
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Compliance Checker said bean was compliant
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Bean Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating source for ejb WCritereListeMulticritere
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generated the following sources for this EJB: [C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\WCritereListeMulticritere_u6449c_LocalHomeImpl.java, C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\WCritereListeMulticritere_u6449c_ELOImpl.java]
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Persistence Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Bean Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating source for ejb Document
[wlappc] 18 sept. 2008 11:23:00 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generated the following sources for this EJB: [C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\Document_6vm6yi_LocalHomeImpl.java, C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\Document_6vm6yi_ELOImpl.java]
[wlappc] 18 sept. 2008 11:23:02 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Persistence Sources
[wlappc] 18 sept. 2008 11:23:02 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Compiling EJB sources
[wlappc] Note: Some input files use unchecked or unsafe operations.
[wlappc] Note: Recompile with -Xlint:unchecked for details.
[wlappc] 18 sept. 2008 11:23:10 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Recompilation completed
[wlappc] 18 sept. 2008 11:23:10 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Rmic completed
[wlappc] Compilation completed successfully.
[jar] Updating jar: H:\devWv2\wv2\build\CommandesEntities.jar
BUILD SUCCESSFUL
All the classes witch hasn't changed has been checked and regenerated. The compliler says "Recompiling because no previous hashes found".
But why ? It could be besause it creates a different working directory each time I execute this ant task ? Is this working directory configurable ?
Would you have any idea of what's happening ?
Thanks.

You can find this in the 'org\apache\tools\ant\taskdefs\defaults.properties'
file of %wl-home%\server\lib\ant\ant.jar
--Sathish
<Michael Lee> wrote in message news:[email protected]..
I mean the definition of "wlappc" not the help for wlappc???thx.
i.e.
where can i find the sentence list below:
<taskdef name="wlappc" classname="weblogic.ant.taskdefs.j2ee.Appc"/>
I mean which files this "taskdef" is being in .

Basic question concernign EJB class

Hi,
I can not understand why a EJB bean class implements methods defined in the remote interface but not 'implements' that interface itself.
who 'implements' that remote interface.
thanks a lot for your time.
Benjamin

Hi !
The remote inteface inturn has the signatures of all the methods present in the Bean class and not the vice versa and hence u see all the complete bussiness methods in the Bean interface.
Hope i am clear
Regards,
Vin

Bug: weblogic.jar doesn't include the javax.ejb classes

In the
Oracle WebLogic Server 11gR1 (10.3.6) + Coherence -
Package Installer
the C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar doesn't include the javax.ejb package classes. The javax.ejb package is empty.

This is the correct behavior, stub and skeleton classes are generated at deployment time by WebLogic server and stored in a server internal location.
In case you are interested, it is something like: ...\samples\domains\medrec\servers\MedRecServer\cache\EJBCompilerCache\ with file named like HelloSession_gjfaqw_Intf.java., etc.
-danny

Compliant J2EE/EJB class file packaging...

Hi,
I've just come across some commerical components which are packaged slightly strangely and I'd like to find out if their approach is J2EE compliant.
The components are EJBs which are packed into several EJB module archives (.jars) inside a main application archive (.ear). The interesting thing is, inside each EJB module .jar, they have packaged the .class files into several ordinary .jar files and added those .jars into the EJB .jar, rather than simply adding the classes to the EJB .jar itself. My question is, is this compliant?
Are application server classloaders suppsed to automatically open such embedded .jars and make the classes available to the container at runtime? I don't think so but I have been assured by the vendor in question that this is compliant (and runs in the J2EE 1.2 RI which I havn't tested).
There are no directives, either in the J2EE deployment descriptors or .jar Manifests which can be used to indicate that the 'inner' .jar files should be unpacked. The Class-Path Manifest attribute can be used to point to other jars using a relative URI but I don't believe it can be used to point to .jars inside the referencing .jar. (In any case, this vendor isn't using a Class-Path attribute)
Any thoughts appreciated!
Regards,
John.

>
Nesting .jar's has always been perfectly proper, It has? I've certainly never seen anything like this in my past java programming experience. Can you give me some examples or references to the J2SE or J2EE specifications that back up this assertion?
I believe J2SE doesn't allow you to simply place different classes in different jars, then nest those jars inside each other and expect a standard ClassLoader to be able to load the classes from the correct location at runtime. Try it, you'll see that doesn't work. I can see nothing in the J2EE spec that says that a J2EE appserver has to go looking into these nested jars.
why
do you believe that ejb-jar do not support this ?Quite simply because there are no references to "nesting" jars in the specification, beyond
a) nesting J2EE modules (.jar, .war and .rar files) inside J2EE application .ear files
and
b) nesting required libraries in "WEB-INF/lib" location of a .war file.
Both of these cases are explicitly defined in the specification but I don't believe there is any support for "general" nesting or Jars.

Overwritting ejb classes

Similar Messages

Maybe you are looking for