[JBoss Portal] - Re: Localizing Tab that has spaces in its name
by thomas.heute＠jboss.com
"syllant" wrote : anonymous wrote :
| | The issue is that resource bundles (as file) cannot be changed at runtime, so when you add a page you cannot change it.
| |
| ? But this is the same for -object.xml descriptor, both provide default values ?!
|
-object.xml is just there to populate the database. It's very convenient in that sense. But then you can also change your portal objects using the admin portlet.
"syllant" wrote :
| anonymous wrote :
| | I was also thinking of resource bundles as default values that could be overridden with whatever is in database. Would that fit your use case ?
| This is what I would expect :-)
|
The reason why i didn't do it is that it can be very confusing. This would update the database, if you redeploy the app with new localized display-name they wouldn't be taken in account unless you use <if-exists>overwrite</if-exists> which is already an issue today for other topics.
"syllant" wrote :
| Where would you put bundles ? Could we use hierarchical page keys (e.g. : default.page1.subpage1) ?
|
The initial idea was to define the resource bundle in the -object.xml descriptor but it means that it would be stored in database (the location of the resource bundle) which sucks.
"syllant" wrote :
| anonymous wrote :
| | portlet.xml is different... It's a deployment feature, not a way to populate data (opposite from -object.xml) so please there is no need for exclamation marks.
| |
| There was a hidden smile under the exclamation mark, that was not supposed to be rude :-)
|
I didn't see the hidden smile, i'm glad if we can have constructive discussion. So far i'm satisified with no solution with the current -object.xm descriptors
"syllant" wrote :
| Even though I think both are descriptors which should not store localization. But this is just my humble opinion...
|
Again the descriptors serves totally different goals. JSR-168 spec lets you define localized string either directly in the portlet.xml or in a resource bundle, this is cool. But we cannot do it for a descriptor which is used to populate data that can be modified at runtime and must be persistent.
If you have a solution that perfectly fits the use cases i mentioned, i would be glad to hear it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106974#4106974
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106974
18 years, 8 months
[JBoss Portal] - Re: Problem with Refresh of IFrame using IFramePortlet.
by Soon5
Hy,
I have to say, that I haven't tested this idea because I had no time, but if you want, you can try.
The idea is, that you put a filter before the applikation that you want to display in the IFrame. That filter does nothing but writing the actual called URL, identified by the session ID into the Database.
Your IFrame Portlet uses the session ID, to get the last URL from the database, and uses that URL as Source. So the IFrame always displays the last visited URL. It should work for all GET operations. POSTs won't work, but I think thats not a problem.
There is some more logik needed, like dropping old entrys in the database, when session is invalidatet or User logs out.
Greetings
Soon5
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106972#4106972
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106972
18 years, 8 months
[JBoss Portal] - Re: Localizing Tab that has spaces in its name
by syllant
anonymous wrote :
| The issue is that resource bundles (as file) cannot be changed at runtime, so when you add a page you cannot change it.
|
? But this is the same for -object.xml descriptor, both provide default values ?!
anonymous wrote :
| I was also thinking of resource bundles as default values that could be overridden with whatever is in database. Would that fit your use case ?
This is what I would expect :-)
Where would you put bundles ? Could we use hierarchical page keys (e.g. : default.page1.subpage1) ?
anonymous wrote :
| portlet.xml is different... It's a deployment feature, not a way to populate data (opposite from -object.xml) so please there is no need for exclamation marks.
|
There was a hidden smile under the exclamation mark, that was not supposed to be rude :-) Even though I think both are descriptors which should not store localization. But this is just my humble opinion...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106971#4106971
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106971
18 years, 8 months
[JCA/JBoss] - Re: Opening connection from a marked rollback tx
by vickyk
"oglueck" wrote :
| Anyway, yes we are drifting away from the problem. I still think it is perfectly legal to open as many connections as I like even if the current tx is set rollback-only. I guess the rollback-only flag is only set in the transaction manager and the connection is completely unaware of this fact until the transaction manager performs the rollback at the end.
When the getConnection() is called on the ConnectionFactory for the xa-tx-datasource the AS should make sure that the associated XA Resource is enlisted in the associated Transaction .
Now if you have the following sequence
1) Start TX T1
2) CF.getConnection(); The associated XAResource with the connection will get enlisted in the T1.
3) SET ROLLBACK on T1 . This step basically sets
case Status.STATUS_PREPARED:
| status = Status.STATUS_MARKED_ROLLBACK;
Look at
http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_0/transaction/sr...
4) Again calling the CF.getConnection() will be able to get the same ManagedConnection from the TransactionLocal but when the associated XAResource is getting enlisted in associated TX this code will get called
| // Inactive transaction
| Transaction threadTx = tm.getTransaction();
| if (threadTx == null || status != Status.STATUS_ACTIVE)
| {
| String error = "Transaction " + threadTx + " is not active " + TxUtils.getStatusAsString(status);
| if (trace)
| log.trace(error + " cl=" + this);
| throw new IllegalStateException(error);
| }
http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_0/connector/src/...
So Connection would not be taken and you would get IllegalStateException .....
Enable to TRACE logging on the org.jboss.resource(JBoss JCA) and org.jboss.tm(Transaction Manager) and figure out what is going on ....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106969#4106969
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106969
18 years, 8 months
[JBoss Messaging] - jboss messging in DMZ zone
by terapong
Hi
im run two jboss as 4.2.1 GA & jboss-messaging-1.4.0.CR2
one in dmz zone private IP 192.168.157.8 and NAT to public IP 210.246.145.170 and add name server jms.dor.go.th start with option -b jms.dor.go.th.
the second front of firwall have ip 210.246.145.173 start with option -b 0.0.0.0
210.246.145.170 config bridge to 210.246.145.173
210.246.145.173 config bridge to 210.246.145.170
when i start server in dmz send private to server front of firwall and server frint of firwall don no private IP and have error
2550-11-23 11:33:52,918 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] getting secondary locator
2550-11-23 11:33:52,938 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] secondary locator: InvokerLocator [null://192.168.157.8:2683/null]
2550-11-23 11:33:52,938 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] creating control connection: InvokerLocator [null://192.168.157.8:2683/null]
2550-11-23 11:34:13,808 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] Error creating a control socket
java.net.ConnectException: Connection timed out: connect
plese help me
sorry for english im not strong im from thailand
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106968#4106968
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106968
18 years, 8 months