[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2008-02-29 Thread alllle
I think you will have better chance to get some help if you open a new thread 
as it seems like a different issue.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4133366#4133366

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4133366
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2008-02-27 Thread yugantshah
ae wrote : aborland wrote : Is there currently any other 
solution/workaround for this? I'd prefer not to hack in such a change. I'm 
using 4.2.0.GA_CP01 and having this exact problem.
  | 
  | This fix is pretty safe and should not have any impact to the rest of the 
system.
  | 
  | As for other workaround, I guess it would be your turn to find it and 
publish it out :)

Hello,
This  solution solves the persistence context loading issue.
But now I have one more issue.The @PersistenceContext is not supported in MDB. 
Also I tried with the 
persistence-context-ref

persistence-context-ref-namehopsLM3/messaging/entity_manager/persistence-context-ref-name
persistence-unit-namehopsMessaging$LM/persistence-unit-name
/persistence-context-ref
in ejb-jar.xml but still same issue.
The error that I get is 

14:50:01,042 ERROR [STDERR] javax.naming.NameNotFoundException: hopsLM3 not boun
d
14:50:01,042 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(Naming
Server.java:529)
14:50:01,042 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(Naming
Server.java:537)
14:50:01,057 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingS
erver.java:543)
14:50:01,057 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServ
er.java:267)
14:50:01,057 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServ
er.java:270)

I am not able to resolve it.
Any help on it would be appreciated.

Thanks and Regards,
Yugant Shah.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4132525#4132525

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4132525
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2008-02-12 Thread alllle
degerhar wrote : Thank you very much! Had the same problem and your patch 
solved the issue!!
  | 
  | Thanx for supplying the zip file, made things much easier

You are welcome. Glad it helped you. It is a pain to setup project just to 
compile a small class change :)

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4128930#4128930

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4128930
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2008-02-12 Thread degerhar
Thank you very much! Had the same problem and your patch solved the issue!!

Thanx for supplying the zip file, made things much easier

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4128721#4128721

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4128721
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-06 Thread alllle
justkeys wrote : Works great!

Good, that confirms that your problem is caused by the same bug.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110758#4110758

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110758
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-06 Thread aborland
Is there currently any other solution/workaround for this? I'd prefer not to 
hack in such a change. I'm using 4.2.0.GA_CP01 and having this exact problem.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110940#4110940

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110940
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-06 Thread alllle
aborland wrote : Is there currently any other solution/workaround for this? 
I'd prefer not to hack in such a change. I'm using 4.2.0.GA_CP01 and having 
this exact problem.

This fix is pretty safe and should not have any impact to the rest of the 
system.

As for other workaround, I guess it would be your turn to find it and publish 
it out :)

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4111001#4111001

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4111001
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-05 Thread justkeys
Ah its a zip! 

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110601#4110601

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110601
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-05 Thread justkeys
Works great!

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110606#4110606

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110606
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-05 Thread justkeys
Thanks. I decoded your base64, but my decompiler says its not a class file. 
Perhaps you could make your patched class file online available some other way, 
or mail it to mynickname / yahoo / com?

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110600#4110600

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110600
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-04 Thread alllle
After tracing into the deployment code, I believe I found the bug that caused 
this problem, at least for my case.

My EAR contains a MDB and the persistence.xml file for configuring the 
EntityManager.

Two classes are involved in this deployment problem: 
org.jboss.ejb3.EJBContainer and org.jboss.ejb3.mdb.MessagingContainer.

The MessagingContainer is a subclass of the EJBContainer, it has a method with 
the signature:
protected JMSProviderAdapter getJMSProviderAdapter(){...}
It invokes the public InitialContext getInitialContext(){...} in the 
EJBContainer class to obtain a InitialContext object in order to lookup the JMS 
provider adapter object from the JNDI. At the end of the method, 
MessagingContainer closes the InitialContext object.

In the previous implemention, the EJBContainer.getinitialContext() method 
returns a new InitialContext object everytime it is called. In version 
4.2.2.GA, it returns the shared instance of InitialContext object defined in 
the class InitialContextFactory, whch is defined as static in the 
InitialContextFactory class.

As you might already figure out at this point, the problem rises when a MDB is 
deployed. Because the MessagingContainer.getJMSProviderAdapter() method closes 
the InitialContext object, it nullify all internal properties of the shared 
instance of the InitialContext object. This shared InitialContext object is 
later used to deploy the persistence.xml file, which throws the 
NoInitialContextException exception.

To overcome this problem before the official fix is out, I had to recompile the 
EJB3 deployment jar  with the modified source. the patched class is attached in 
the next reply below.


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110302#4110302

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110302
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-04 Thread alllle
If you are having the same problem, you may need the patched class file (I 
haven't find any workaround). To compile it from the source is a very tedious 
work so I'll post it here, hope this will save you some time. 

Since the forum does not allow attachment, I encoded the patch in Base64. You 
can copy the text below and go to this site to decode it. It's a zip file that 
contains the patched MessagingContainer class.

UEsDBAoAAIp6gzcKb3JnL2pib3NzL1BLAwQKAACPeoM3
DwAAAG9yZy9qYm9zcy9lamIzL1BLAwQKAACQeoM3EwAA
AG9yZy9qYm9zcy9lamIzL21kYi9QSwMEFAgAPHqDN/TwhXFuGQAAjzoAACsAAABvcmcvamJv
c3MvZWpiMy9tZGIvTWVzc2FnaW5nQ29udGFpbmVyLmNsYXNzxFoLeFTlmf6+YZIZJgeQYCBBkAER
Qm4joogJIoEESUzCJREFqngyc5KcMJkzziUkaq2X2qu1e6ndSl1d11W61bWiMgFRUbtqL1vX1bWu
2+u23Wq73UvrturWat/vP2fuM0B9nj6rDznn/Jfvfv3/+cZ7jz1JRCtdWzzkYjrTig0HRgeteDxg
jA6uCoyFBgO9RjyuD5uR4Y1WJKGbESPmITfTaQVLO7s35CyoZGopWJAwx4xY3IiNm0EjMICP0JbB
USOY6IqMW3uNGNO0sDXMNL8nuw8DgjjQg6cRa2PSFJB+GwhTbc+oPq5PCHwFMT2DlTP1YMIc1xOm
FemPGkGmM3pK8Naetwjb5o4pbo3OSChqmZHEJoCxYpNM55XabkaGwta+QPcGjPaW3AiQtR2dm9ov
6RnY09HZP9DV1z7QtaVvz8DOrZ1M1Yr+QFgHj/2JGFjF+hkQYzyhRxI79HDS8NIcplmKzZbRsXjL
gBU1wU1Vd2//nvaO9q0DW7Z7aS6TD5PNMb0lpkOSVTmovFSHgZART5gRxSnTKYWUeGkBkOSsGZiM
Qrw1W7dv2dHV0bndxoRnd19Hl5cWMc2JxqxxM2TE2kN6NGHEZAJoetsv29Pf2d+v8C4BVWP6RD8E
o9DOWarHoX+BH+8w4/pg2Agx8S4m79pg2IyYiXUwgvoVO5jcG62Q4aMV1OihBod/W0wbwwCiURM1
Q1mg2IwZofY02P6EnkjGFZBd04kpoNEZtNRHK2mVh86GKsqZlkbn0LlM04eNhD3A1FzfU4C1bUV5
0xRs52nkIS+o7YEP9CXHBo3YgDAperaCeniHHjPl2xmsXOuw/Gx9sRnkYNKtaKA9DvNM9OoRXZAV
EtZj6aH84TQUNZJMmOHAZj0+khDEbYWGDGM1YkEjCnMNdGXfuyJD1nYjasVNZceFuzrxp8OIhq3J
MSOSaFuxw0MXMM0rJGFD0gyDNi9dyLRQbW8ZPdswWp04cAGixqqmiD5mXOCjtdSuUSttgOGVkMiK
HbKiQ6NO2gTh6dGoEQkVqCm9tGjIIaNNQGzWqIu6YXQJy55kOrW+eAvWTqMeIaiX6dU/sor+/5S2
hWnxCQOjj/pom4himdh5v0ZVpHnoEqi0VL7oUInAmEjI4ks1uox2IuYMGnrEGVcSYZpd5GAe2s10
7gcKtD7aRdsE4RUazaCZ8nmlRjoNImnEjUQmNYHm+kKxZCbbVOxJjJigbnmpgF+cCxGwPZjugwnj
bcxWP5Ac1zqYXMEwvKWMlSAHKGnJkA14RjAxsTVmRSXMGSCupqSRYDzHLrJ2wLT6g9kPAngoYy5M
i05gT9AyAmhGRnYSmZPnW7aeIR8szNoYpDlkDucyODu9S7HYq0clN0etaDKsJ4z2gtQ+Q2FNjFgh
oR/c5nprzBgKQ/QBe0FeDBfFZPcBQ108TX5xAdBaZDYnWQGITc0FhduNuJWEnFXGtGKiWA9dy1Sf
Q1AkYiUUY6qkydthxHyw7us0+ghdD/nEMBceN9ozO1C8lcpY2RG72mqromvoRo1ukhBYMS4lBrSs
54Bp6DlZgkRieiiUrw5Hi5NZNWRUmFOtldG9SKuKPkmf9tCnmJaceL1GtwgjWtT5Fql66VbYxFiu
GfroT+jPPPSnsNDCeKvRn9PnkFCMq5J6OF6QexyZrdjloc8zrcoKZsxI6CE9oZclDHald2CBj26j
bV66HXFF0pzUNF/U6A76S9tZOoxgWEcJs8k0wieRzdLGrJYjQ91Fd3vor/Lybt4Sjf6a7oEw4uJt
QSnEVOnhrt8l6fQuulej++gACiYsQMgrwXoJYezw0k2ipC9rdL8If0Za+Kpg9dDfoYjP7tqejEjR
3jkhEQZi8tED9BXJJQ+hHstFODASs/apOCY28DA96qFHADzPhDQ6RCmQG02C3DUnR27xkIcOIy5l
hzO0wQzgV8lwQoq4wvDjjWYse+nJWDJ2jDlGgKTW8wFsByCmi9E4xlFX1hDgwcqTnYVsZDJEPn9Y
WIHWIgb+fJnBuBQ6z2v097RMIszXNUrab9/U6B9oGZaaESS6ftnnoxfoRQ/9I0rrE3V36V7MCYMa
/RO9hA4BNt+l2hvp31bVrygMqieC0yYk/LNGr9C3UVcHYwbywUBeUxg6Tn4/Ibb8ntQxnhINplQa
/6LRdPKJpP5Vo++IpDQlXKhxAklMCP2eRt+nH8DYYFagvoDS0+rLgRcf+zfA60KHYOph82oEAmlj
fqzRT+jfocWQMZgcLhOsdghJr2t0NXXL2880+rkQNx0d4kYlL6gUaugem7CLi0X1aTbt8kVyuQNM
FkDi/0X/46H/Lq4UhdNJRzGbjXBUGqlf0q/s0KZ6nu5IyLSxtByv7CqOel76XyZ/6Y6hadSBiqbh
N/S2h97KO7kYm7DdNssCMI3DsYS8d+j/UKcF7QGmlWUDbnlpvEvveeh3CNZFy3r18JAVy1iRrM+4
mUbvixZmRYEjAWcK7h2I6UHDywy5btJNNMP+hOW3LdqfBdDkH4sPg9F3eZrGbom3vkyRZUgwbQc/
o2ldLjwu7QhJoxmFBIqXHo/+NimpnxcGdHiM6LU/OTRkThTE4bJtTSkd80wmdMynIGQFkKK5WuM5
fCr4MSMhY2LLUJlOsEvWztV4HtfCrOPJwbjTx9XUd5VA43AdUVxrIWNITybStPtGcxjRHLT9qJ1G
QJOcaITFiu1wwNR+nMJy98mlHl6cl3oySQ+eymdoNE77vHwm0zkbrWQ45Ef15XcqPX+mJfCPKYz+
oZg15o+KC/pBY7jV7+PltNnD9Uis5cgUNA0an86NipuytfDJcYN8adMix3ZlJYN6Q48No7SaUwIq
Jk1VtM8vT4yPV/G5Hj4nr3qD5Aw9pPFqPk/6o2QsBgu2BwsbentUgTlf41aWRmnY7gnT3ajdeSHH
FncrTlMmkrtA43XixJ5oMj7SGQl6eH3xmWnuQagYTlBleB9fyBtQ9vDGgg60gFdEb6zs1HgTXwTz
lMItNG7GLdA2v3CbM+Ps6dK4my+229322HBSPBpCn1tfSpdqR6/GfbxFJXix7z4Io1B0znoR3TaN
t3M/RBcvLbr5Re2HIzmVkPgSjXeI7CrRxUF0cFwrHErvnRkBtKywSnTfpaUKTc6CJvPT6vxMPivK
q0xNpTJmueUeviLPlzIHjZ2xmBXz8pUI3WqD39mhHHbSSPjNdOI2Qj6+nAel4EXedkcvNibzz30z
flAlTizQrKRSQyFRkCOqDh7R2ORR8C3LB5FGNuuRUFiEuOZ4TX6POWQEJ4NhI6fbd3ZCu2GOeHgM
LdsHg6CxxVGw5agCDGx0iGNakGdPBaHBw6B7bpZRaDmTcLwMMTT0WelwN6LHEQONiN9pSpEv95mJ
Ef96B6WPr6J2H+/jSQ8jmC/LshI3EB7MxGSg33mBHq2gqSxI46v5Gpt0odmIbUXOCJpRPSz1mUN6
BkBmEpR/GMZUslMuQtdhjcFuq/ha/ojG10sKr01GkIRG4KFmUDjJwJXMdqPGN/FH4SlhIzKcGFHH
2V0e/hga4lI8mWPRsJEFwDfbUvikxp/iT9vhIIenBfVlWVqxw8OfyYuxtm2K935WcsYiFJ6qYk6f
3eVaJ6JiIm28Glw7B2ddWZTw/HiekFAnlj5+KCNUaZES6Rya3/Vk+0n4HarvKApy/qLGd0hBXh0z
xqzxvHpc2LxT47skSFXJ+kwdP43v1vh2aYp28d0gOevcWy0rLPP3anyP7JNznq3FNyMC+ksaxSmB
xpa/rPH9/ADUOixN97KyASk/AtNt/KDGX1En19hoXw7xQSc+tQY6pK4JJ7p7+9MEOAdjOTcwM9WJ
Q85NUHX+gH1UwpzSeIoP21kyB6DDEdOKvL4NfUVAyqhA8VKUeI8BS3rUr9vDKFVoLT+uUSc/UXDo
UUIC+Uf4VXyMn/bwU3mJ9zgkaPwMfxUGqxpPpTcnecnxQzryozaUyxxnBlQ/C7sK2l+tfi+j7j09
W6MDlB/O649ZiPbOKhHb1zV+lLq9/E2m81XcUjV6cyhmjhuR5pzrNf+wjLT5k3GpT/3DSVFQZNif
UPJfyd/S+AWVLvbpsYhAflHjR1Q3xy8BB7/MtLa+NOklyuXiIQH0isbf5lfh7qq7txtD53Kxrgxs
dKX8Wt5t5LakkVQW8x2Nv1sITU16+Pt5R5zZ8+RA9uQ4J+b/EOgvieyNWPsi/hyJNYtoUOB+j9q9

[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-04 Thread alllle
forgot to mention that you should merge this above patched MessagingContainer 
class into the SERVER_CONFIG/deploy/ejb3.deployer/jboss-ejb3.jar file.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110307#4110307

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110307
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-04 Thread alllle
Create JIRA ticket:
http://jira.jboss.com/jira/browse/JBAS-5049

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110308#4110308

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110308
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-12-04 Thread alllle
ae wrote : ... You can copy the text below and go to this site to decode 
it. It's a zip file that contains the patched MessagingContainer class
  | 

And since I can't edit the original post, here is the link I forgot to post to 
the site that does the base64 encode/decode online for free:
http://www.motobit.com/util/base64-decoder-encoder.asp

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110312#4110312

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110312
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-11-30 Thread alllle
Forgot to mention that I was using SEAM. And I compared all the configuration 
files with one of the SEAM examples, didn't see any differences other than name 
references.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109481#4109481

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109481
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-11-30 Thread alllle
I wonder if anyone has encountered the same problem described here? 

I am having the same problem. My EAR contains a module app.jar, which contains 
the persistence.xml file:

  | persistence
  | persistence-unit name=myDB
  | providerorg.hibernate.ejb.HibernatePersistence/provider
  | jta-data-sourcejava:appDS/jta-data-source
  | /persistence-unit
  | /persistence
  | 
Where the appDS is deployed with a xxx-ds.xml file with no problem. However, I 
am getting the same NoInitialContextException. 

I tried to deploy the app.jar under module/java as well as module/ejb but same 
problem. I also tried to add:
properties
  | property name=java.naming.factory.initial 
value=org.jnp.interfaces.NamingContextFactory /
  | property name=java.naming.factory.url.pkgs 
value=org.jboss.naming:org.jnp.interfaces /
  | /properties
  | 
to the persistence.xml file and same error.

I have no clue what is wrong. It's deployed to the server so no jndi.properties 
file should be needed. If so, why this error occurs?

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109449#4109449

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109449
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-11-21 Thread jaikiran
I still have no clue why your packaging should result in that error. Why not 
try this package structure:

- q.ear/lib/utils.jar
  | - q.ear/META-INF/application.xml (module/ejb=beans.jar)
  | - q.ear/beans.jar
  | - q.ear/beans.jar/META-INF/persistence.xml 

And dont specify the jar-file element in the persistence.xml. 

See if this works.



View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4106797#4106797

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4106797
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-11-20 Thread jaikiran
Can you post the logs from the server.log file, from the point where it logs 
the following message:

anonymous wrote :  15:20:27,725 INFO [PersistenceUnitDeployment] Starting 
persistence unit persistence.units:ear=q.ear,unitName=manager1 



View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4106337#4106337

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4106337
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-11-20 Thread justkeys
javax.naming.NoInitialContextException: Need to specify class name in 
environment or system property, or as an applet parameter, or in an application 
resource file:  java.naming.factory.initial
at 
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
at 
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at 
javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at 
org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:216)
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:585)
at 
org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at 
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy82.start(Unknown Source)
at 
org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120)
at 
org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:627)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:351)
at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at 
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy35.start(Unknown Source)
at 

[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-11-20 Thread jaikiran
Strange. Since this piece of code is running in the server itself, you shouldnt 
have seen this error. JBoss comes with 3 servers (named 'default', 'minimal' 
and 'all'). Which one are you using? Or have you created your own server? If 
you have created the server yourself, are you sure you did it right? And 
depending on the server you are using, do you see a file named jndi.properties 
in the %JBOSS_HOME%\server\ serverName\conf folder? What does it contain? 
Also, does your ear/jar file contain any jndi.properties file in it?



View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4106362#4106362

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4106362
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-11-20 Thread jaikiran
anonymous wrote : The ear deploys on 4.2.1

I just compared the source code of 4.2.1 and 4.2.2. Incidentally, there's a 
change in the org.jboss.ejb3.Ejb3Deployment. The change relates to the way the 
InitialContext is being constructed. 

I can't reproduce this error on 4.2.2 system, with my sample persistence 
application. However, i have seen a similar post in one of the forums here 
which too pointed to the same error while deploying an application on 4.2.2 
(and the application deployed fine on 4.2.1). Looks like something specific to 
the way the application is packaged or maybe the contents in your application.




View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4106409#4106409

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4106409
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [Installation, Configuration DEPLOYMENT] - Re: 4.2.2 wont deploy my persistency unit

2007-11-20 Thread justkeys
Yes something changed in the packaging interpretation.
In 4.2.1, we had to package the jars containing the ejbs (beans.jar) twice:

- q.ear/lib/utils.jar
- q.ear/META-INF/application.xml (module/ejb=app.jar)
- q.ear/beans.jar - duplicate
- q.ear/app.jar/ejb3/beans.jar
- q.ear/app.jar/META-INF/persistence.xml (jar-file=../ejb3/beans.jar)

In 4.2.2 the packaging above results in deployment errors, so i changed the 
packaging into what i believe is the correct ejb3-packaging 

- q.ear/lib/utils.jar
- q.ear/META-INF/application.xml (module/ejb=app.jar)
- q.ear/app.jar/ejb3/beans.jar
- q.ear/app.jar/META-INF/persistence.xml (jar-file=ejb3/beans.jar)

and then i got the jndi-factory-naming error. 

So perhaps, the difference is that my persistence.xml is in a .jar inside an 
.ear (that also contains lib/.jars).

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4106443#4106443

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4106443
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user